DOCSLIB.ORG

Session 3: XML Information Modeling (Part I)

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Session 3: XML Information Modeling (Part I) XML for Java Developers G22.3033-002 Session 3 - Main Theme XML Information Modeling (Part I) Dr. Jean-Claude Franchitti New York University Computer Science Department Courant Institute of Mathematical Sciences 1 Agenda Q Summary of Previous Session Q XML Physical Entities Q Logical Structure of XML Documents Q XML Document Navigation Q Java APIs Q Custom Markup Languages Q Readings Q Assignment #1b (1 week) Q Assignment #2a+2b (2 weeks) 2 1 Summary of Previous Session Q History and Current State of XML Standards Q Advanced Applications of XML Q XML’s eXtensible Style Language (XSL) Q Character Encodings and Text Processing Q XML and DBMSs Q Course Approach ... Q XML Application Development Q XML References and Class Project Q Readings Q Assignment #1a (reminder?) / Assignment #1b (1 week) 3 XML Physical and Logical Structure Q Physical Structure Q Governs the content in a document in form of storage units Q Storage units are referred to as entities Q See http://www.w3.org/TR/REC-xml#sec-physical-struct Q Logical Structure Q What elements are to be included in a document Q In what order should elements be included Q See http://www.w3.org/TR/REC-xml#sec-logical-struct 4 2 XML Physical Entities Q Allow to assign a name to some content, and use that name to refer to it Q Eight Possible Combinations: Q Parsed vs. Unparsed Q General vs. Parameter Q Internal vs. External Q Five Actual Categories: Q Internal parsed general Q Internal parsed parameter Q External parsed general Q External parsed parameter Q External unparsed general 5 Logical Structure: Namespaces Q See Namespaces 1.0 Q Sample Element: <z:a z:b="x" c="y" xmlns:z="http://www.foo.com/"/> Q Corresponding DTD Declaration <!ELEMENT z:a EMPTY> <!ATTLIST z:a z:b CDATA #IMPLIED c CDATA #IMPLIED xmlns:z CDATA #FIXED "http://www.foo.com"> 6 3 Logical Structure: DTDs Q Shortcomings Q Separate Syntax <!ELEMENT Para (#PCDATA)*> <Para>Some paragraph</Para> vs. <ElementType name="Para"> <ContentModel><PCData/></ContentModel> </ElementType> Q Lack of Support for Data-typing Q DTD Treats an XML Structure as a String of Characters <Price currency="USD">1450</Price> <Price currency="USD">too high</Price> 7 Logical Structure: XML Schemas Q Structures Q How elements and attributes are setup in an XML document Q Datatypes Q Built-in datatypes (e.g., String, Boolean, numbers) Q Generated datatypes (e.g., dates, times, real values) Q Support for user generated datatypes Q Backward compatibility with functional subset (DTD) Q ID, IDREF, NMTOKEN, and SGML-based types Q Grouping of Elements/Attributes Q Archetypes and Attribute Groups Q Inheritance Q Via Basetypes, and Archetypes/Attribute Groups 8 4 Logical Structure: XML Schemas (continued) <datatype name='AgeInYears'> <basetype name='integer' URI="http://www.w3.org/xmlschemas/datatypes"/> <minInclusive>0</minInclusive> <maxInclusive>140</maxInclusive> </datatype> <attribute name="employeesAge" type="AgeInYears"/> 9 Logical Structure: Navigation Q URIs/URLs Q Syntax for encapsulating a name in any registered namespace, and label it with the namespace Q Produce a member of the universal set of reachable objects Q See http://www.w3.org/Addressing/ Q XPath Q Used to locate certain parts of an XML document Q See Session 3 handout on “Processing XML documents in Java using XPath and XSLT” 10 5 JAXP and Associated XML APIs Q JAXP: Java API for XML Parsing Q Common interface to SAX, DOM, and XSLT APIs in Java, regardless of which vendor's implementation is actually being used. Q JAXB: Java Architecture for XML Binding Q Mechanism for writing out Java objects as XML (marshalling) and for creating Java objects from such structures (unmarshalling). Q JDOM: Java DOM Q Provides an object tree which is easier to use than a DOM tree, and it can be created from an XML structure without a compilation step. Q JAXM: Java API for XML Messaging Q Mechanism for exchanging XML messages between applications. Q JAXR: Java API for XML Registries Q Mechanism for publishing available services in an external registry, 11 and for consulting the registry to find those services. Simple API for XML (SAX) Parsing APIs 12 6 DOM Parsing APIs 13 XSLT APIs 14 7 Java API Packages Q java.xml.parsers Q The JAXP APIs, which provide a common interface for different vendors' SAX and DOM parsers. Q Two vendor-neutral factory classes: SAXParserFactory and DocumentBuilderFactory that give you a SAXParser and a DocumentBuilder, respectively. The DocumentBuilder, in turn, creates DOM-compliant Document object. Q org.w3c.dom Q Defines the Document class (a DOM), as well as classes for all of the components of a DOM. Q org.xml.sax Q Defines the basic SAX APIs. Q jaxax.xml.transform 15 Q Defines the XSLT APIs that let you transform XML into other forms. SAX API Packages Q org.xml.sax Q Defines the SAX interfaces. Q org.xml.sax.ext Q Defines SAX extensions that are used when doing more sophisticated SAX processing, for example, to process a document type definitions (DTD) or to see the detailed syntax for a file. Q org.xml.sax.helpers Q Contains helper classes that make it easier to use SAX -- for example, by defining a default handler that has null-methods for all of the interfaces, so you only need to override the ones you actually want to implement. Q javax.xml.parsers Q Defines the SAXParserFactory class which returns the SAXParser. Also defines exception classes for reporting errors. 16 8 DOM API Packages Q org.w3c.dom Q Defines the DOM programming interfaces for XML (and, optionally, HTML) documents, as specified by the W3C. Q javax.xml.parsers Q Defines the DocumentBuilderFactory class and the DocumentBuilder class, which returns an object that implements the W3C Document interface. The factory that is used to create the builder is determined by the javax.xml.parsers system property, which can be set from the command line or overridden when invoking the newInstance method. This package also defines the ParserConfigurationException class for reporting errors. 17 XSLT API Packages Q javax.xml.transform Q Defines the TransformerFactory and Transformer classes, which you use to get a object capable of doing transformations. After creating a transformer object, you invoke its transform() method, providing it with an input (source) and output (result). Q javax.xml.transform.dom Q Classes to create input (source) and output (result) objects from a DOM. Q javax.xml.transform.sax Q Classes to create input (source) from a SAX parser and output (result) objects from a SAX event handler. Q javax.xml.transform.stream Q Classes to create input (source) and output (result) objects from an I/O stream. 18 9 Content of Jar Files Q jaxp.jar (interfaces) Q javax.xml.parsers Q javax.xml.transform Q javax.xml.transform.dom Q javax.xml.transform.sax Q javax.xml.transform.stream Q crimson.jar (interfaces and helper classes) Q org.xml.sax Q org.xml.sax.helpers Q org.xml.sax.ext Q org.w3c.dom Q xalan.jar (contains all of the above implementation classes) 19 XML Information Modeling Q Steps Q Documenting the Information Structure Q Representing the Information Structure in XML Form Q Defining XML DTDs and/or Schemas Q Modeling Techniques Q UML: object modeling Q XML: content modeling Q ORM: data modeling Q See Session 3 handout on “XML Information Modeling” Q UML, MOF and XMI Q See Session 3 handouts on “UML, MOF, and XMI” and “OMG’s XML Metadata Interchange Format (XMI)” 20 10 Open Information Model Q Analysis and Design Model Q Unified Modeling Language (UML) - uml.dtd Q UML Extensions - umlx.dtd Q Common Data Types - dtm.dtd Q Generic Elements - gen.dtd Q Components and Object Model Q Component Description Model - cde.dtd Q Database and Warehousing Model Q Database Schema Elements - dbm.dtd Q Data Transformation Elements - tfm.dtd Q OLAP Schema Elements - olp.dtd Q Record Oriented Legacy Databases - rec.dtd Q Knowledge Management Model 21 Q Semantic Definition Elements - sim.dtd Custom Markup Languages Q Mathematical Markup Language (MathML) Q OpenMath Q Chemical Markup Language (CML) Q Geography Markup Language (GML) Q Wireless Markup Language (WML) Q Synchronized Multimedia Integration Language (SMIL) Q Synchronized Vector Graphics (SVG) Q Extensible 3D (X3D) Q XML-Based User Interface Language (XUL) Q Extensible Log Format (XLF) 22 11 Readings Q Readings Q XML Development with Java 2: Chapters 4 Q Professional Java XML: Chapters 5 Q XML and Java: Chapter 2 Q Handouts posted on the course web site Q Review XML 1.0, XPath 1.0, XML Schema W3C Recs Q Project Frameworks Setup (ongoing) Q Apache’s Web Server, TomCat/JRun, and Cocoon Q Apache’s Xerces, Xalan, Saxon Q Antenna House XML Formatter, Apache’s FOP, X-smiles Q Visibroker 4.5 (or AppServer), WebLogic 6.1 23 Q POSE & KVM (MIDP/PADP) Assignment Q Assignment #2a: Q This part of the project focuses on the application business model discovery using XML information modeling technology. The discovery process should adhere to the following steps: (a) Documenting the information structure, (b) Representing the information structure in XML form, (c) Defining XML DTDs and/or Schemas Q More specific project related information, and extra credit assignments will be provided during the session 24 12 Assignment (continued) Q Assignment #2b: Q This part of the project relies on the business model discovery process suggested in assignment #2a, and should demonstrate the use of UML use cases to support the development of XML DTDs and/or Schemas 25 Next Session: XML Information Modeling (Part II) Q Advanced Logical Structuring and XML Schemas Q XML Metadata Management Q XML Linking/Pointer Language, XML Base, and XML Inclusions Q XML Data Binding Q Industry Specific Markup Languages 26 13.
Load more

Recommended publications
  • 73 Metadata Interchange in Service Based Architecture
    UDC:681.324 Review paper METADATA INTERCHANGE IN SERVICE BASED ARCHITECTURE Alma Butkovi Tomac Nagravision Kudelski group, Cheseaux / Lausanne [email protected] Dražen Tomac Cambridge Technology Partners, Genève [email protected] Abstract: Metadata is important factor for understanding, controlling and planning in complex information systems both from technical and business perspective. However its usage is often limited due to opposing or non-existent standards. The article discusses current state of meta model standards and shows new possibilities for meta data interchange based on XML as de facto standard for data interchange and increasing acceptance of web services architecture. Keywords: metadata, web services, XMI, CWM. 1. INTRODUCTION Term “meta” comes from old Greek work representing after, next, with; Latin word denoting something transcendental or beyond nature. Applying the prefix meta denotes more comprehensive or transcendent then the base itself. Meta data transcends the data in a way that it describes or references more than individual data instance: it provides domain, format, context of the data, data source, business related rule etc. Most common short definitions on metadata say: Meta data is data about data. This definition does not describe meta data in its whole scope. To quote [4]:” Meta data is all physical data (contained in software and other media) and knowledge (contained in employees and various media) from inside and outside an organization, including information about the physical data, technical and business processes, rules and constraints of the data, and structures of the data used by a corporation.” 2. METADATA SIGNIFICANCE Although metadata significance is widely recognized and important in information systems, it gains on its importance for data warehouse projects, business intelligence and semantic web.
    [Show full text]
  • A Logic-Based Service for Verifying Use Case Models
    COMPUTATION TOOLS 2017 : The Eighth International Conference on Computational Logics, Algebras, Programming, Tools, and Benchmarking A Logic-based Service for Verifying Use Case Models Fernando Bautista, Carlos Cares Computer Science and Informatics Department, University of La Frontera (UFRO) Temuco, Chile Email: [email protected], [email protected] Abstract—Use cases are a modeling means to specify the required modular and scalable solution in order to initially implement use of software systems. As part of UML (Unified Modeling some types of verifications and then another group of them Language), it has become the de facto standard for functional under an incremental development. specifications, mainly in object-oriented design and development. In order to check these models, we propose a theoretical solution In this paper, we present a first Prolog prototype, as proof by adapting a general quality of models framework (SEQUAL), of concept, of a tool that can aid the quality assessment of and, following our approach, a rule-based solution that includes a use case diagram. Moreover, we have implemented it as a both expert-based and definition-based rules. In order to promote Web service in order to illustrate that logic-based solutions can a distributed set of quality assessment services, a Web service has also be part of key quality assessment process in cloud-based been developed. It works on XMI (XML Metadata Interchange) software development environment. files which are parsed and verified by Prolog clauses. In order to check use case models and their application, Keywords–Rule-based quality; UseCase verification; Logic- based services; XMI; Prolog.
    [Show full text]
  • Xml Schema Production Rules
    Xml Schema Production Rules Protozoan Fremont sometimes advertized his administrations offhandedly and redeploy so unthinkingly! Polymorphic Sanders cogitate very continuously while Cesar remains effete and documentary. Vick still stabilises sneeringly while apprehensive Glenn recombines that unwisdom. Tax jurisdiction in discussions of the study description for each metadata for all xml schema and rural, credit that is used to xml schema production rules A mistake between the XML Schema Definition XSD lan- guage and text-based. XML schema files version 22 Search & Match the Share. XML schema validation using parsing expression PeerJ. To be used to observe data to ESMA in the production environment MiFIR Transparency RequirementsMiFIR introduces rules with respect to. In most common configurable options are a lot of this specification defines a new resource denoted by other variables such a necessary to give a new aggregate component. Introduction to XML Metadata Interchange XMI Eclipse Wiki. Keywords Schema validation XMLDTD parsing expression. Therefore obtain an xscomplexType element that is built using the rules described in. This is no approach followed by rule based XML schema languages which. ANNEX V Implementation Rules and Guidelines WIPO. It among a third-sizes-fit-third solution put a combination of business rules. All changes to the XML schema since the production of the 2006 normative. Fully integrated schema in a production environment and reduce processing time divide each. Databases needing to produce RSS feeds producing and storing valid. Not your computer Use offset mode to vocation in privately Learn more Next savings account Afrikaans azrbaycan catal etina Dansk Deutsch eesti. In production rule, then to offer options available for frb holidays.
    [Show full text]
  • OMG Meta Object Facility (MOF) Core Specification
    Date : October 2019 OMG Meta Object Facility (MOF) Core Specification Version 2.5.1 OMG Document Number: formal/2019-10-01 Standard document URL: https://www.omg.org/spec/MOF/2.5.1 Normative Machine-Readable Files: https://www.omg.org/spec/MOF/20131001/MOF.xmi Informative Machine-Readable Files: https://www.omg.org/spec/MOF/20131001/CMOFConstraints.ocl https://www.omg.org/spec/MOF/20131001/EMOFConstraints.ocl Copyright © 2003, Adaptive Copyright © 2003, Ceira Technologies, Inc. Copyright © 2003, Compuware Corporation Copyright © 2003, Data Access Technologies, Inc. Copyright © 2003, DSTC Copyright © 2003, Gentleware Copyright © 2003, Hewlett-Packard Copyright © 2003, International Business Machines Copyright © 2003, IONA Copyright © 2003, MetaMatrix Copyright © 2015, Object Management Group Copyright © 2003, Softeam Copyright © 2003, SUN Copyright © 2003, Telelogic AB Copyright © 2003, Unisys USE OF SPECIFICATION - TERMS, CONDITIONS & NOTICES The material in this document details an Object Management Group specification in accordance with the terms, conditions and notices set forth below. This document does not represent a commitment to implement any portion of this specification in any company's products. The information contained in this document is subject to change without notice. LICENSES The companies listed above have granted to the Object Management Group, Inc. (OMG) a nonexclusive, royalty-free, paid up, worldwide license to copy and distribute this document and to modify this document and distribute copies of the modified version. Each of the copyright holders listed above has agreed that no person shall be deemed to have infringed the copyright in the included material of any such copyright holder by reason of having used the specification set forth herein or having conformed any computer software to the specification.
    [Show full text]
  • Application Schema Modeling for Interoperable Geospatial Information Using the ISO 19100 Series of Standards
    Application schema modeling for interoperable geospatial information using the ISO 19100 series of standards. Pavel Golodoniuc 1, Simon Cox 2 1 CSIRO Earth Science and Resource Engineering, Perth, Australia, [email protected] 2 CSIRO Earth Science and Resource Engineering, Perth, Australia, [email protected] INTRODUCTION Geographic information (GI) is inherent to many application domains in various disciplines and constitutes an integral part of Earth sciences, including geology, geophysics, meteorology, hydrology, oceanography, and soil science. Communication of GI may occur between different domains or within the same community. A sensible way to enable interoperability between distributed applications and systems is the use of unified standards shared across disciplines that communities have agreed upon. The primary authorities in GI standardization are ISO Technical Committee 211 (ISO/TC 211) and the Open Geospatial Consortium (OGC). While ISO/TC 211 focuses primarily on abstract standards including information models for cross- domain concerns, OGC concentrates on architectures for distribution of geospatial services and implementation of ISO standards through service interfaces, data models and encodings. Implementation of ISO 19136 [1], also known as Geography Markup Language (GML), provides a set of encoding patterns and auxiliary cross-domain XML components to serve as a framework for the implementation of specialized languages, based on the models provided in a number of ISO/TC 211 standards, such that aspects that are common across domains are implemented in a common way. GML is an implementation of abstract artefacts, which is not intended for use “out of the box”. It is an XML grammar defined in W3C XML Schema (WXS) language that is intended to be used as the basis for concrete Application Schema implementation.
    [Show full text]
  • Technical Standards Catalogue VERSION 6.2
    e-Government Technical Standards Catalogue VERSION 6.2 FINAL September 2005 Technical Standards Catalogue / version 6.2 final / September 2005 1 CONTENTS 1 INTRODUCTION ...........................................................................................................................3 2 CHANGES FROM PREVIOUS VERSION..................................................................................4 3 ISSUES UNDER CONSIDERATION............................................................................................5 4 INTERCONNECTION ...................................................................................................................7 TABLE 1 SPECIFICATIONS FOR INTERCONNECTIVITY.......................................................................7 TABLE 2 SPECIFICATIONS FOR WEB SERVICES ..............................................................................10 5 DATA INTEGRATION ................................................................................................................16 TABLE 3 SPECIFICATIONS FOR DATA INTEGRATION ...........................................................................16 6 CONTENT MANAGEMENT METADATA ...............................................................................19 TABLE 4 SPECIFICATIONS FOR CONTENT MANAGEMENT METADATA .................................................19 TABLE 5 SPECIFICATIONS FOR IDENTIFIERS .......................................................................................20 7 E-SERVICES ACCESS.................................................................................................................23
    [Show full text]
  • Understanding
    Implementing UBL Mark Crawford UBL Vice Chair XML 2003 9 December 2003 Why Are We Talking About UBL • UBL fulfils the promise of XML for business by defining a standard cross-industry vocabulary • UBL is the ebXML missing link • UBL plus ebXML enables the next generation of eBusiness exchanges – Cheaper, easier, Internet-ready – Extends benefits of EDI to small businesses – Fits existing legal and trade concepts – Allows re-use of data • UBL can provide the XML payload for a wide variety of other web-based business frameworks Overview 1 What and Why of UBL 2 The Design of UBL ebXML Core Components Naming and Design Rules Document Engineering Customizing UBL 3 The Content of UBL 1.0 What is Normative What is non-Normative Availability 4 Making UBL Happen 5 UBL Phase 2 6 Summary The promise of XML for e-business • Plug ‘n’ play electronic commerce – Spontaneous trade – No custom programming • Ubiquity on the Internet – Dirt-cheap tools – Complete platform independence – Enable true global market availability • Enable universal interoperability – Abandon existing EDI systems – Handle both "publication" document types and "transactional" documents Goals for Successful eBusiness Services • Web-enable existing fax- and paper-based business practices • Allow businesses to upgrade at their own pace • Preserve the existing investment in electronic business exchanges • Integrate small and medium-size businesses into existing electronic data exchange-based supply chains The standardization of XML business documents is the easiest way to accomplish
    [Show full text]
  • XMI and MOF: a Mini-Tutorial
    XMI and MOF: a mini-tutorial Perdita Stevens University of Edinburgh http://www.dcs.ed.ac.uk/home/pxs UML + XML = ? This tutorial is about the combination of two major buzzwords: UML and XML. My assumption is that everyone knows what UML is: - the Unified Model(l)ing Language - a diagrammatic language for recording the design of (object-oriented software) systems but that perhaps not everyone knows how it’s defined? How UML is defined Two main documents: Notation Guide : informal explanation of notation (concrete syntax) and its connection to abstract syntax. Semantics : semi-formal specification of abstract syntax, plus further explanation of semantics. Semantics takes precedence over Notation Guide in cases of conflict – theoretically. Plus: definition of the Object Constraint Language (OCL). UML semantics document: syntax The abstract syntax describes (in UML!) the relationships between kinds of UML model elements (the metamodel). For example, use cases, actors and classes are all said to be examples of classifiers: Classifier Class Actor UseCase ¡ Back in the days of the method wars... ... people wanted to be able to switch tools, which meant switching notations. But the different OOMLs recorded different information. One major reason for UML success... but still not fully realised in practice. Hmm... structured data (UML models) ... standard way to exchange it between tools.... yup. XML may be the key to getting real value from UML tools But how exactly to use XML? XMI XMI = XML Metadata Interchange an OMG standard. Most importantly, XMI is a way to save UML models in XML. In fact it’s more general. UML is a MOF-based metamodel; XMI shows how to save any MOF-based metamodel in XML ¢ MOF 1 MOF = Meta Object Facility an OMG standard MOF is a simple language for defining languages, e.g., UML.
    [Show full text]
  • Documents Currently Open for Public Review and Comment
    Documents Currently Open for Public Review and Comment The InterNational Committee for Information Technology Standards (INCITS) announces that the subject-referenced document(s) is being circulated for a 45-day public review and comment period. Comments received during this period will be considered and answered. Commenters who have objections/suggestions should so indicate and include their reasons and send them to [email protected]. When submitting comments, we encourage use of the Comments Template This public review also serves as a call for patents and any other pertinent issues (copyrights, trademarks). Correspondence regarding intellectual property rights may be emailed to the INCITS Secretariat at [email protected]. List of all public reviews this year Public Review Period: 9/26/2014 - 11/10/2014 Withdrawal of: INCITS/ISO/IEC TR 14165-372:2011[2011] Title: Information Technology - Fibre Channel Methodologies for Interconnects -2 (FC-MI-2) Call for Patents Committee: INCITS/ T11.3 Comments on this document should be submitted to: [email protected] To obtain copies, click here Public Review Period: 10/3/2014 - 11/17/2014 Withdrawal of: INCITS/ISO/TS 19138:2006[2010] Title: Geographic information - Data quality measures Call for Patents Committee: INCITS/ L1 Comments on this document should be submitted to: [email protected] To obtain copies, click here Public Review Period: 10/10/2014 - 11/24/2014 Adoption of: ISO/IEC 19508:2014[] Title: Information technology - Object Management Group Meta Object Facility (MOF) Core Call for Patents
    [Show full text]
  • Iso/Iec 19503:2005(E)
    This is a preview - click here to buy the full publication INTERNATIONAL ISO/IEC STANDARD 19503 First edition 2005-11-01 Information technology — XML Metadata Interchange (XMI) Technologies de l'information — Échange de métadonnées XML (XMI) Reference number ISO/IEC 19503:2005(E) © ISO/IEC 2005 ISO/IEC 19503:2005(E) This is a preview - click here to buy the full publication PDF disclaimer This PDF file may contain embedded typefaces. In accordance with Adobe's licensing policy, this file may be printed or viewed but shall not be edited unless the typefaces which are embedded are licensed to and installed on the computer performing the editing. In downloading this file, parties accept therein the responsibility of not infringing Adobe's licensing policy. The ISO Central Secretariat accepts no liability in this area. Adobe is a trademark of Adobe Systems Incorporated. Details of the software products used to create this PDF file can be found in the General Info relative to the file; the PDF-creation parameters were optimized for printing. Every care has been taken to ensure that the file is suitable for use by ISO member bodies. In the unlikely event that a problem relating to it is found, please inform the Central Secretariat at the address given below. © ISO/IEC 2005 All rights reserved. Unless otherwise specified, no part of this publication may be reproduced or utilized in any form or by any means, electronic or mechanical, including photocopying and microfilm, without permission in writing from either ISO at the address below or ISO's member body in the country of the requester.
    [Show full text]
  • Session 12 - Main Theme Service Oriented Architectures Web Services Platforms (Part I)
    Application Servers G22.3033-011 Session 12 - Main Theme Service Oriented Architectures Web Services Platforms (Part I) Dr. Jean-Claude Franchitti New York University Computer Science Department Courant Institute of Mathematical Sciences 1 Agenda Continued from Session 11: Middleware and Component Infrastructures EAI and B2Bi Environments MDA/BPM Technology UML-Based Component Modeling and Related Standards XML Pattern Languages and XML Model-Based Applications Web Services XML-RPC SOAP, DIME, and ROPE UDDI, DISCO WSDL Summary Readings Assignment #8 (due: 12/10) 2 1 Summary of Previous Session .Net Environment (continued) Channel Independence and Pervasive Devices Connected Devices XML in Component-Based Development Environments XML and JavaBeans/EJBs Deployment Descriptors for OMA Services More on the OMA Persistence Service EAI Environments B2Bi Environments (e.g., WebMethods Framework) BPM Environments Summary Readings Assignment #8 3 Application Servers Architectures Application Servers for Enhanced HTML (traditional) a.k.a., Page-Based Application Servers Mostly Used to Support Standalone Web Applications New Generation Page-Based Script-Oriented App. Servers First Generation Extensions (e.g., Microsoft IIS with COM+/ASP) Servlet/JSP Environments XSP Environment Can now be used as front-end to enterprise applications Hybrid development environments Distributed Object Computing Platforms Provide an infrastructure for distributed communications enabling Still need to merge traditional web-oriented
    [Show full text]
  • NIST Big Data Interoperability Framework: Volume 7, Standards Roadmap
    NIST Special Publication 1500-7 NIST Big Data Interoperability Framework: Volume 7, Standards Roadmap Final Version 1 NIST Big Data Public Working Group Technology Roadmap Subgroup This publication is available free of charge from: http://dx.doi.org/10.6028/NIST.SP.1500-7 NIST Special Publication 1500-7 NIST Big Data Interoperability Framework: Volume 7, Standards Roadmap Final Version 1 NIST Big Data Public Working Group (NBD-PWG) Technology Roadmap Subgroup Information Technology Laboratory This publication is available free of charge from: http://dx.doi.org/10.6028/NIST.SP.1500-7 September 2015 U. S. Department of Commerce Penny Pritzker, Secretary National Institute of Standards and Technology Willie May, Under Secretary of Commerce for Standards and Technology and Director NIST BIG DATA INTEROPERABILITY FRAMEWORK: VOLUME 7, STANDARDS ROADMAP National Institute of Standards and Technology (NIST) Special Publication 1500-7 46 pages (September 16, 2015) NIST Special Publication series 1500 is intended to capture external perspectives related to NIST standards, measurement, and testing-related efforts. These external perspectives can come from industry, academia, government, and others. These reports are intended to document external perspectives and do not represent official NIST positions. Certain commercial entities, equipment, or materials may be identified in this document in order to describe an experimental procedure or concept adequately. Such identification is not intended to imply recommendation or endorsement by NIST, nor is it intended to imply that the entities, materials, or equipment are necessarily the best available for the purpose. There may be references in this publication to other publications currently under development by NIST in accordance with its assigned statutory responsibilities.
    [Show full text]