Feedback from OASIS UBL TC to Draft Core Components Specification 1.8
|
|
- Phillip James
- 5 years ago
- Views:
Transcription
1 Feedback from OASIS UBL TC to Draft Core Components Specification.8 document id Version 0.2 editor Bill Burcham April 8, 2002 Sterling Commerce Much of the contention over element naming in UBL stems from the imprecise treatment of properties in the UN Core Components Technical Specification [CC-UN]. While that specification does talk extensively about property terms which are part of a dictionary entry name for a data element (a la [NAMING-ISO]), we are left to infer the existence and makeup of a first class property concept. The term property is used often in that specification, but it is never formally defined. Additionally, the term child field is used in some of the examples in that specification. That term is used synonymously to property, and is also left undefined. Further, it never appears in any of the conceptual diagrams. We are trying to give property terms to things. What things are we trying to give them to? Well [CC-UN] doesn t tell us. We propose: Proposal The CC model must include the concept of property. Property is the model element named by a property term in the same way as a BIE or a CC is the model element named by an object class (name). Proposal 2 A Property relates an Aggregate Core Component to a Basic Core Components it contains. What is property s relationship to the other elements of the CC meta-model? This simply formalizes the prose in already in the specification. A Property allows us to identify (name) the use of a Basic Core Component by an Aggregate Core Component. This concept (Property) corresponds to field in database models, attribute in ER modeling, member in Java, local element in XML. Proposal 3 The is derived from relationship of Core Component Type to Representation Term is eliminated. A Representation Term describes the role of a Core Component Type as it is used in an Aggregate Core Component, through a Basic Core Component. The new relationship is : Representation Term:Property. Section 5.6 lines ; section lines
2 UBL needs to clearly define the role of CCTs and RTs, since the Core Components spec fails to do this. I want to go over the history of the development of thes concepts, so that we can make sure that we produce a set of definitions that are sufficient to the needs of UBL. Originally, there were *NO* CCTs. All we had in the CC work was a set of semantic "primitives" that were called RTs. The list in the spec has not changed much since then. At one of the ebxml meetings it was realized that although some of the RTs were single bits of data, others were actually data composites. For each RT, one (and exactly one, in theory) CCT was indicated, to suggest the semantics of the properties needed to fully express the use of the RT. As we start trying to use the spec set up in this way (UBL and others), we have been realizing that there are some significant failings in this system. One great example of this is a Location Code, a common bit of data that cannot be described as a set of enumerated values - what we traditionally and typically think of as a 'code list' - even though it's business function is that of a code. Core Components did not account for this phenomenon. Because it functions as a "code", it has a semantic primitive RT of "Code" - this means that it has a "Code" CCT, which allows you to point to a code-list and supporting properties. Unfortunately, this doesn't work. For this type of a "code" you need a different set of properties in your physical expression of the business data. (In the case of location code, this is a pattern, not an enumeration - a different type of simple datatype in XSD, for example.) This is true not only of codes, but also of other kinds of data. We need to specify *both* the semantic primitive of the model (the Representation Term, traditionally) *and* the set of properties by which it is made manifest (the CCT), and there is neither a one-to-one relationship between RTs and CCTs, nor a many-to-one relationship between RTs and CCTs. It is, by the practical dictates of business information, a many-to-many, unless we substantially increase the range of our RTs and CCTs. We must either extend these lists significantly, or we must allow them to be combinatorial. We canot know how to clearly define CCts and RTs until we understand whether they are combinatorial or not. There is another requirement that highlights this need, and it is something that has not been addressed so far in UBL, other than as a comment against the draft order from the LCSC. This is the absolute need for a solid description of the physical representation of data, at a finer level of detail than is currently possible. Take, for example, the degree of precision of a price. This is a fundamental kind of datatype issue, since the degree of precision in prices defines the tolerances used in the calculations for essential business processes such as Order/ASN/Invoice reconciliation (aka "book-keeping"). If we are to describe a "price" using the current system, here is what we would know about it: RT = "Amount" (which is always a monetary amount according to the CC definitions)
3 CCT = "AmountType" (which gives us a number and a currency code) The degree of precision of the price cannot be specified in the semantic model, given these capabilities. All monetary amounts are the same. But in reality, prices have a very different specificity than some other monetary amounts. This means we cannot simply assume a single precision for all monetary amounts, and make that part of our syntaxbinding. In other words, there is a need to capture in the model some distinction between a price and another kind of monetary amount, since they have different requirements in terms of how they are represented. Please note that, in this example, precision is *not* syntaxspecific. It is a critical property of the business data itself, and can be described equally well in many different syntaxes. SUGGESTED APPROACH AND DEFINITIONS: I would suggest the following approach to solving these difficulties: () Have a set of Representation terms, which function as "semantic primitives," as originally intended by the CC group in ebxml. (The list may need to be altered slightly to include some missing types, but will not undergo wholesale expansion). This indicates what the business purpose of the data is, in an abstract sense, wholly separate from how it will be represented when syntax bound. (2) The list of CCTs should be expanded to reflect the actual needs of expressing business data in a syntax, to cover those cases where the syntax itself is not the determining factor, but rather the representation of the business data (as is the case for numeric precision of prices). Alternately, the CCTs could have properties added to them so that the range of possible representation formats is one of the properties. This would work very neatly for something like datetimes, for ecxample, but might become very confusing and clunky in referring to numeric formats. In either case, the range of expressive possibilities for CCTs should be expanded. (3) Each representation term could be combined with some specified subset of the available CCTs, as determined by the requirements of reality. An "Identifier" RT could be a CodeType, or it could be a TextType, biut we would no longer have ambiguous types like "IdentifierType". The CCT would now define an exact set of properties that would describe the actual representation of the data, rather than describing its semantic or business function. (This is essentially abstracting the idea of simpletypes in XSD up a level, but still referring to the actual physical representation of the data, rather than its semantic.) This would result in a significant increase in the number of CCTs (or their expressive range) and would result in the removal of some of the existing ones. The current list assumed a many-to-one relationship between RTs and CCTs that is not useable in reality. We need to re-work the list to reflect this finding. NOTE: The names "Representation Term" and "CCT" are not particularly good, so if you want to reverse them, you could. I wanted to avoid confusion within CC, however, by not redefining them as their exact opposites. Traditionally, the RT was the semantic
4 primitive, and the CCT was a construct that encapsulated the property set for representing that primitive. Proposal 4 A CCTProperty relates a Core Component Type to the (Content and Supplimentary) Components it contains. For the same reasons a property is needed to relate an ACC to the BCC s it contains, a property is needed to relate a CCT to the components it contains. As a result of P0-P3, Figure 6. Core Components Metamodel should now be as shown in the Core Components Metamodel box in this diagram: XML Schema CC For the same reasons ACC needs a Property to relate it to its constituents, CCT needs a property to relate it to its constituents. CCTProperty..* Content Component TypeName -identifies -describes Type CCT -represents Supplementary Component There is a derived association (..*,..*) between RT and CCT through Property and BCC. TypeDefinition -contains BCC Property..* Representation Term ElementDeclaration -describes ACC Core Components Metamodel This concept is not explicitly present in the CC technical specification. It is mentioned extensively, but never really defined. -implements TagName -describes Element..* -child -parent XML Instance XML Implementation
5 The preceding diagram shows how the proposed Core Components metamodel (with properties modeled) is syntax bound to XSD by UBL. The syntax binding process to XSD involves creating XSD complex types for ACC s and CCT s. These complex types consist of (local) element declarations one for each property of the source ACC/CCT. The element s tag name is identical to the name of the source property (Property/CCTProperty). Representation Terms may be modeled in XSD via various mechanisms. For example an attribute called RepresentationTerm could be defined on elements of complex types representing ACC s and CCT s. The attribute could be given a default value selected from a distinguished list of terms one for each Representation Term. Once we identify and describe properties, what shall we call them? Could a set of rules around role definition satisfy our need to capture recurring component usage patterns (and name them)? Perhaps the central tenet would be: P4: Role-based property naming: a Property s name ( property term in the dictionary entry name) should reflect the role played by that property s content relative to the ACC in which that property is declared. Similarly a CCTProperty s name should reflect the role played by that property s content relative to the CCT in which that property is declared. References CC-UN NAMING-ISO UN/CEFACT Draft Core Components Specification, Part, 8 February, 2002, version.8 ISO/IEC 79, Final committee draft, Parts -6.
UN/CEFACT Core Components Data Type Catalogue Version December 2007
1 2 3 4 5 6 7 8 9 UN/CEFACT Core s Data Type Catalogue Version 2.01 7 December 2007 UN/CEFACT Core s Data Type Catalogue Version 2.01 of 7 December 2007 Page 1 of 137 10 11 12 13 14 15 16 Abstract This
More informationUBL Library Content Methodology
UBL Library Content Methodology The purpose of this document is two-fold: 1. To explain how we got to where we are with the UBL vocabulary, we felt it necessary to provide a background to the rationale
More informationUN/CEFACT Core Components Data Type Catalogue Version September 2009
UN/CEFACT Core Components Data Type Catalogue Version 3.0 29 September 2009 UN/CEFACT Core Components Data Type Catalogue Version 3.0 Page 1 of 88 Abstract CCTS 3.0 defines the rules for developing Core
More informationConformance Requirements Guideline Version 0.1
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 Editors: Conformance Requirements Guideline Version 0.1 Aug 22, 2001 Lynne Rosenthal (lynne.rosenthal@nist.gov)
More informationUBL Naming and Design Rules Checklist
UBL Naming And Design Rules Checklist Page 1 2004-09-03 UBL Naming and Design Rules Checklist This document is a subset of the UBL Naming and Design Rules Master Document. It reflects the rules used to
More informationSchema Rules for UBL and Maybe for You. Eve Maler XML 2002 Conference 12 December 2002
Schema Rules for UBL and Maybe for You Eve Maler XML 2002 Conference 12 December 2002 1 Lots to cover in this session Goals Introduce the Universal Business Language and its unique schema requirements
More informationTeiid Designer User Guide 7.5.0
Teiid Designer User Guide 1 7.5.0 1. Introduction... 1 1.1. What is Teiid Designer?... 1 1.2. Why Use Teiid Designer?... 2 1.3. Metadata Overview... 2 1.3.1. What is Metadata... 2 1.3.2. Editing Metadata
More informationFor example, under Presentation Node Type, one would not say:
Published on OASIS (https://www.oasis-open.org) Keyword Guidelines for OASIS Specifications and Standards Description: Describing best practices in using RFC2119 or ISO keywords when writing specifications
More informationThe Future of XML Vocabularies. Creating UBL Conformant Schema Tutorial
www.oasis-open.org/events/symposium_2005 The Future of XML Vocabularies SYMPOSIUM 24 April: Tutorials 8:30 AM 12:00 PM New Orleans Marriott Creating UBL Conformant Schema Tutorial Mark Crawford Senior
More informationThe Object Model Overview. Contents. Section Title
The Object Model 1 This chapter describes the concrete object model that underlies the CORBA architecture. The model is derived from the abstract Core Object Model defined by the Object Management Group
More informationDirection And Concepts March Scott R. Hinkelman Techniques and Methodologies (TMG) [acting] Vice Chair
UN/CEFACT Unified Context Methodology (UCM) Direction And Concepts March 2009 Scott R. Hinkelman Techniques and Methodologies (TMG) [acting] Vice Chair Unified Context t Methodology (UCM) Project Chair
More informationProposed Revisions to ebxml Technical Architecture Specification v ebxml Business Process Project Team
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 Proposed Revisions to ebxml Technical Architecture Specification v1.0.4 ebxml Business Process Project Team 11
More informationUBL NDR 2.0 Checklist
UBL NDR 2.0 Checklist Editors Michael Grimley Mavis Cournane The following checklist contains all UBL XML naming and design rules as defined in UBL Naming and Design Rules version 2.0, 30 August 2006.
More informationProposed Revisions to ebxml Technical. Architecture Specification v1.04
Proposed Revisions to ebxml Technical Architecture Specification v1.04 Business Process Team 11 May 2001 (This document is the non-normative version formatted for printing, July 2001) Copyright UN/CEFACT
More informationIntroduction to Global Data Types in SAP NetWeaver PI 7.1 (preview)
Introduction to Global Data Types in SAP NetWeaver PI 7.1 (preview) Applies to: SAP NetWeaver Process Integration IT Scenarios in Version 7.1 Summary This article introduces the core components technical
More informationElectronic Business Extensible Markup Language (ebxml) Part 5: Core Components Specification (CCS)
INTERNATIONAL STANDARD ISO 15000-5 First edition 2014-04-15 Electronic Business Extensible Markup Language (ebxml) Part 5: Core Components Specification (CCS) Commerce électronique en langage de balisage
More informationInformation Model Architecture. Version 1.0
Information Model Architecture Version 1.0 1 introduction...2 2 objective...2 3 definition of terms...3 4 conformance...4 4.1 UBL conformance...4 4.2 NES conformance...4 4.3 NES profile conformance...4
More informationA - 1. CS 494 Object-Oriented Analysis & Design. UML Class Models. Overview. Class Model Perspectives (cont d) Developing Class Models
CS 494 Object-Oriented Analysis & Design UML Class Models Overview How class models are used? Perspectives Classes: attributes and operations Associations Multiplicity Generalization and Inheritance Aggregation
More informationCSE 12 Abstract Syntax Trees
CSE 12 Abstract Syntax Trees Compilers and Interpreters Parse Trees and Abstract Syntax Trees (AST's) Creating and Evaluating AST's The Table ADT and Symbol Tables 16 Using Algorithms and Data Structures
More informationUN/CEFACT/UBL XML Naming and Design Rules Analysis Page 1
UN/CEFACT/UBL XML Naming and Design Rules Analysis 03 August 2007 [Source: http://www.oasis-open.org/committees/download.php/25133/ubl_vs_cefact_xml_ndr_analysis_2007-08-03.doc] Legend Same as UBL No corresponding
More informationBusiness Document Naming and Design Rules Version 1.0
Business Document Naming and Design Rules Version 1.0 Committee Specification Draft 01 / Public Review Draft 01 Specification URIs This version: http://docs.oasis-open.org/ubl/business-document-ndr/v1.0/csprd01/business-document-ndrv1.0-csprd01.xml
More informationDepartment of the Navy XML Naming and Design Rules (NDR) Overview. 22 September 2004 Federal CIO Council XML WG Mark Crawford LMI
Department of the Navy XML Naming and Design Rules (NDR) Overview 22 September 2004 Federal CIO Council XML WG Mark Crawford LMI Why do you need XML rules? To achieve interoperability! Department (e.g.
More informationUNIT II. Syllabus. a. An Overview of the UML: Visualizing, Specifying, Constructing, Documenting
UNIT II Syllabus Introduction to UML (08 Hrs, 16 Marks) a. An Overview of the UML: Visualizing, Specifying, Constructing, Documenting b. Background, UML Basics c. Introducing UML 2.0 A Conceptual Model
More informationSchema Binding Proposal
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 Schema Binding Proposal Sandy Gao Valentina Popescu 1 Terminology...1 2 Problem definition...2 3
More informationWhat are the characteristics of Object Oriented programming language?
What are the various elements of OOP? Following are the various elements of OOP:- Class:- A class is a collection of data and the various operations that can be performed on that data. Object- This is
More informationTeiid Designer User Guide 7.7.0
Teiid Designer User Guide 1 7.7.0 1. Introduction... 1 1.1. What is Teiid Designer?... 1 1.2. Why Use Teiid Designer?... 2 1.3. Metadata Overview... 2 1.3.1. What is Metadata... 2 1.3.2. Editing Metadata
More informationGuide to the Core Components Dictionary. ebxml Core Components
1 2 3 4 5 6 7 8 9 10 11 12 13 14 Guide to the Core Components Dictionary ebxml Core Components 10 May 2001 Version 1.04 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 1 Status of this Document This
More information/633 Introduction to Algorithms Lecturer: Michael Dinitz Topic: Sorting lower bound and Linear-time sorting Date: 9/19/17
601.433/633 Introduction to Algorithms Lecturer: Michael Dinitz Topic: Sorting lower bound and Linear-time sorting Date: 9/19/17 5.1 Introduction You should all know a few ways of sorting in O(n log n)
More informationSAP Intern. Elements versus Attributes. 1 Introduction. 2 Characteristics
SAP Intern Elements versus Attributes 20. March 2002 Gunther Stuhec Verteiler: UBL-Group 1 Introduction A common cause of confusion, or at least uncertainty, in the design of a schemas is the choice between
More informationConceptual Modeling and Specification Generation for B2B Business Processes based on ebxml
Conceptual Modeling and Specification Generation for B2B Business Processes based on ebxml HyoungDo Kim Professional Graduate School of Information and Communication, Ajou University 526, 5Ga, NamDaeMoonRo,
More informationBusiness Document Naming and Design Rules Version 1.1
Business Document Naming and Design Rules Version 1.1 Committee Specification Draft 01 / Public Review Draft 01 Specification URIs This version: http://docs.oasis-open.org/ubl/business-document-ndr/v1.1/csprd01/business-document-ndrv1.1-csprd01.xml
More informationSUMMARY: MODEL DRIVEN SECURITY
SUMMARY: MODEL DRIVEN SECURITY JAN-FILIP ZAGALAK, JZAGALAK@STUDENT.ETHZ.CH Model Driven Security: From UML Models to Access Control Infrastructres David Basin, Juergen Doser, ETH Zuerich Torsten lodderstedt,
More informationCEN/ISSS WS/eCAT. Terminology for ecatalogues and Product Description and Classification
CEN/ISSS WS/eCAT Terminology for ecatalogues and Product Description and Classification Report Final Version This report has been written for WS/eCAT by Mrs. Bodil Nistrup Madsen (bnm.danterm@cbs.dk) and
More informationWhich Of The Following Is Not One Of The Built-in Data Types Of Xml Schema Definition
Which Of The Following Is Not One Of The Built-in Data Types Of Xml Schema Definition 2.5 DTD (Document Type Definition) Validation - Simple Example To develop an XML document and schema, start with a
More informationB2B Integration - Aligning ebxml and Ontology Approaches
B2B Integration - Aligning ebxml and Ontology Approaches Birgit Hofreiter & Christian Huemer Institute for Computer Science and Business Informatics University of Vienna, Liebiggasse 4, 1010 Vienna, Austria
More informationCore Component Primer
Joint Core Components Core Component Primer Interim Basic Information Entity Discovery Method DRAFT Version 0.3 11 September 2001 Core Component Primer Page 2 Table of Contents 1. STATUS OF THIS DOCUMENT...
More informationA Data Modeling Process. Determining System Requirements. Planning the Project. Specifying Relationships. Specifying Entities
Chapter 3 Entity-Relationship Data Modeling: Process and Examples Fundamentals, Design, and Implementation, 9/e A Data Modeling Process Steps in the data modeling process Plan project Determine requirements
More information21. Business Process Analysis (3)
21. Business Process Analysis (3) DE + IA (INFO 243) - 2 April 2008 Bob Glushko 1 of 43 4/1/2008 3:34 PM Plan for Today's Class Business Transaction Patterns Business Signals Collaborations and Choreography
More informationB oth element and attribute declarations can use simple types
Simple types 154 Chapter 9 B oth element and attribute declarations can use simple types to describe the data content of the components. This chapter introduces simple types, and explains how to define
More informationSpecification for Information Exchange (SIX) Language
Specification for Information Exchange (SIX) Language Mr. Thomas Lee Center for E-Commerce E Infrastructure Development The University of Hong Kong http://www.cecid.hku.hk Web Wide Web Consortium One-day
More informationDCMI Abstract Model - DRAFT Update
1 of 7 9/19/2006 7:02 PM Architecture Working Group > AMDraftUpdate User UserPreferences Site Page Actions Search Title: Text: AttachFile DeletePage LikePages LocalSiteMap SpellCheck DCMI Abstract Model
More informationInformation Technology Document Schema Definition Languages (DSDL) Part 1: Overview
ISO/IEC JTC 1/SC 34 Date: 2008-09-17 ISO/IEC FCD 19757-1 ISO/IEC JTC 1/SC 34/WG 1 Secretariat: Japanese Industrial Standards Committee Information Technology Document Schema Definition Languages (DSDL)
More informationIntegrating Concepts: Open items for consideration
Integrating Concepts: Open items for consideration John H. Spicer, Hubert S.K. Tong, Daveed Vandevoorde Project: ISO/IEC JTC 1/SC 22/WG 21/C++ Document #: Date: 2017-06-17 Revises: None Working Group:
More informationUBL 2 Guidelines for Customization, First Edition
UBL 2 Guidelines for Customization, First Edition Public Review Draft 03 16 October 2009 Specification URIs: This Version: http://docs.oasis-open.org/ubl/guidelines/ubl2-customization1prd03.pdf (Authoritative)
More informationXML technology is very powerful, but also very limited. The more you are aware of the power, the keener your interest in reducing the limitations.
XML technology is very powerful, but also very limited. The more you are aware of the power, the keener your interest in reducing the limitations. A key problem is rooted in the very paradigm of XML, which
More informationDraft SDMX Technical Standards (Version 2.0) - Disposition Log Project Team
Draft SDMX Technical s (Version 2.0) - Disposition Log Project 1 Project 2 Project general general (see below for exampl es) In the document Framework for SDMX technical standards, version 2) it is stated
More informationNote that in this definition, n + m denotes the syntactic expression with three symbols n, +, and m, not to the number that is the sum of n and m.
CS 6110 S18 Lecture 8 Structural Operational Semantics and IMP Today we introduce a very simple imperative language, IMP, along with two systems of rules for evaluation called small-step and big-step semantics.
More informationGoals: Define the syntax of a simple imperative language Define a semantics using natural deduction 1
Natural Semantics Goals: Define the syntax of a simple imperative language Define a semantics using natural deduction 1 1 Natural deduction is an instance of first-order logic; that is, it is the formal
More informationA registry model for UN/CEFACT s Core Components
A registry model for UN/CEFACT s Core Components Christian Huemer, Philipp Liegl Institute of Software Technology and Interactive Systems Vienna University of Technology Vienna, Austria {huemer, liegl}@big.tuwien.ac.at
More informationSDMX self-learning package No. 5 Student book. Metadata Structure Definition
No. 5 Student book Metadata Structure Definition Produced by Eurostat, Directorate B: Statistical Methodologies and Tools Unit B-5: Statistical Information Technologies Last update of content December
More informationType Checking and Type Equality
Type Checking and Type Equality Type systems are the biggest point of variation across programming languages. Even languages that look similar are often greatly different when it comes to their type systems.
More informationThe Extensible Markup Language (XML) and Java technology are natural partners in helping developers exchange data and programs across the Internet.
1 2 3 The Extensible Markup Language (XML) and Java technology are natural partners in helping developers exchange data and programs across the Internet. That's because XML has emerged as the standard
More informationTMQL issues. October 14, slide 1
TMQL issues October 14, 2007 http://www.isotopicmaps.org slide 1 Support for transitive closures We think TMQL needs to support transitive closures on query expressions Something like root-node (
More informationCHAPTER4 CONSTRAINTS
CHAPTER4 CONSTRAINTS LEARNING OBJECTIVES After completing this chapter, you should be able to do the following: Explain the purpose of constraints in a table Distinguish among PRIMARY KEY, FOREIGN KEY,
More informationGML Clarifications. IHO S-100WG April 2018 Raphael Malyankar; Eivind Mong. Work sponsored by NOAA
GML Clarifications IHO S-100WG3 10-13 April 2018 Raphael Malyankar; Eivind Mong Work sponsored by NOAA Overview of proposal/presentation The proposal for Part 10b contains: Modifications arising from splines
More informationSOME TYPES AND USES OF DATA MODELS
3 SOME TYPES AND USES OF DATA MODELS CHAPTER OUTLINE 3.1 Different Types of Data Models 23 3.1.1 Physical Data Model 24 3.1.2 Logical Data Model 24 3.1.3 Conceptual Data Model 25 3.1.4 Canonical Data Model
More informationPosition Paper on the Definition of SOA-RM
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 Position Paper on the Definition of SOA-RM Authors: C. Matthew MacKenzie (mattm@adobe.com), Duane A.
More informationAn Architecture for Semantic Enterprise Application Integration Standards
An Architecture for Semantic Enterprise Application Integration Standards Nenad Anicic 1, 2, Nenad Ivezic 1, Albert Jones 1 1 National Institute of Standards and Technology, 100 Bureau Drive Gaithersburg,
More informationWeb Services Resource Metadata 1.0 (WS-ResourceMetadataDescriptor)
1 2 3 4 Web Services Resource Metadata 1.0 (WS-ResourceMetadataDescriptor) Committee Specification 01, November 9, 2006 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 Document identifier:
More informationCimConteXtor User Guide
CimConteXtor User Guide V3 1/86 CimConteXtor User Guide User Guide V3 CimConteXtor is an Enterprise Architect Add-In. The main purpose of CimConteXtor is to create a UML profile in EA, profile that is
More informationCS-202 Introduction to Object Oriented Programming
CS-202 Introduction to Object Oriented Programming California State University, Los Angeles Computer Science Department Lecture III Inheritance and Polymorphism Introduction to Inheritance Introduction
More informationUniversal Business Language (UBL) Naming and Design Rules
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 Universal Business Language (UBL) Naming and Design Rules Publication Date 5 November 2004 Document
More informationCIMERGY PROJECT FIRST RESULTS ON IEC STANDARDS EDF IMPLEMENTATION
CIMERGY PROJECT FIRST RESULTS ON IEC 61970-61968 STANDARDS EDF IMPLEMENTATION E. Lambert*, A. Maizener*, F. Wu*, J.L Sanson*, C. Bahloul*, P. Veyret* *EDF R&D Division 1, Abenur du Général de Gaulle 92141
More informationDATA MODELS FOR SEMISTRUCTURED DATA
Chapter 2 DATA MODELS FOR SEMISTRUCTURED DATA Traditionally, real world semantics are captured in a data model, and mapped to the database schema. The real world semantics are modeled as constraints and
More information- What we actually mean by documents (the FRBR hierarchy) - What are the components of documents
Purpose of these slides Introduction to XML for parliamentary documents (and all other kinds of documents, actually) Prof. Fabio Vitali University of Bologna Part 1 Introduce the principal aspects of electronic
More informationOMG Modeling Glossary B
OMG Modeling Glossary B This glossary defines the terms that are used to describe the Unified Modeling Language (UML) and the Meta Object Facility (MOF). In addition to UML and MOF specific terminology,
More informationUBL Guidelines for Customization Version 1.0
UBL Guidelines for Customization Version 1.0 Public Review Draft 02 13 April 2009 Specification URIs: This Version: http://docs.oasis-open.org/ubl/guidelines/ubl-customization1.0prd02.pdf (Authoritative)
More informationUniversal Business Language (UBL) Naming and Design Rules
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 Universal Business Language (UBL) Naming and Design Rules Publication Date 15 November 2004 Document
More informationM301: Software Systems & their Development. Unit 4: Inheritance, Composition and Polymorphism
Block 1: Introduction to Java Unit 4: Inheritance, Composition and Polymorphism Aims of the unit: Study and use the Java mechanisms that support reuse, in particular, inheritance and composition; Analyze
More informationStylus Studio Case Study: FIXML Working with Complex Message Sets Defined Using XML Schema
Stylus Studio Case Study: FIXML Working with Complex Message Sets Defined Using XML Schema Introduction The advanced XML Schema handling and presentation capabilities of Stylus Studio have valuable implications
More informationBeginning To Define ebxml Initial Draft
Beginning To Define ebxml Initial Draft File Name Version BeginningToDefineebXML 1 Abstract This document provides a visual representation of how the ebxml Architecture could work. As ebxml evolves, this
More informationThe DPM metamodel detail
The DPM metamodel detail The EBA process for developing the DPM is supported by interacting tools that are used by policy experts to manage the database data dictionary. The DPM database is designed as
More informationAn UML-XML-RDB Model Mapping Solution for Facilitating Information Standardization and Sharing in Construction Industry
An UML-XML-RDB Model Mapping Solution for Facilitating Information Standardization and Sharing in Construction Industry I-Chen Wu 1 and Shang-Hsien Hsieh 2 Department of Civil Engineering, National Taiwan
More informationIEEE LANGUAGE REFERENCE MANUAL Std P1076a /D3
LANGUAGE REFERENCE MANUAL Std P1076a-1999 2000/D3 Clause 10 Scope and visibility The rules defining the scope of declarations and the rules defining which identifiers are visible at various points in the
More informationB.H.GARDI COLLEGE OF MASTER OF COMPUTER APPLICATION. Ch. 1 :- Introduction Database Management System - 1
Basic Concepts :- 1. What is Data? Data is a collection of facts from which conclusion may be drawn. In computer science, data is anything in a form suitable for use with a computer. Data is often distinguished
More informationNIEM Update. Mike Hulme, NIEM Technical Architecture Committee Co-chair and Unisys Solution Architect. Nlets Implementers Workshop
NIEM Update Mike Hulme, NIEM Technical Architecture Committee Co-chair and Unisys Solution Architect Nlets Implementers Workshop 8/31/2016 Topics NIEM 3.2 NIEM 4.0 niem.github.io Enhanced code list capabilities
More informationUN/CEFACT Core Components Technical Specification Version 3.0
United Nations Centre for Trade Facilitation and Electronic Business 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 UN/CEFACT Core Components Technical Specification Version 3.0 2 nd Public Review 16 April 2007
More information6.001 Notes: Section 1.1
6.001 Notes: Section 1.1 Slide 1.1.1 This first thing we need to do is discuss the focus of 6.001. What is this course all about? This seems quite obvious -- this is a course about computer science. But
More informationAdministrative Guideline. SMPTE Metadata Registers Maintenance and Publication SMPTE AG 18:2017. Table of Contents
SMPTE AG 18:2017 Administrative Guideline SMPTE Metadata Registers Maintenance and Publication Page 1 of 20 pages Table of Contents 1 Scope 3 2 Conformance Notation 3 3 Normative References 3 4 Definitions
More informationUBL v2 Data Model Architecture Discussion Paper
UBL v2 Data Model Architecture Discussion Paper Thomas Lee (ytlee@cecid.hku.hk) 18 May 2005 1 Introduction This paper describes the architecture design of the UBL v2 data model that was discussed and proposed
More informationA Conceptual Model of the UML
CONTENT A Conceptual Model of the UML Building Blocks of the UML 1. Things [1.1] Structural Things (1.1.1) Class (1.1.2) Interface (1.1.3) Collaboration: (1.1.4) Use case (1.1.5) Components: (1.1.6) Node:
More informationXML Naming and Design Rules. Draft 1.1, 14 January 2005
XML Naming and Design Rules Draft 1.1, 14 January 2005 NamingAndDesignRules_1.1.doc Page 1 14 January 2005 1 Status of this Documents This version: This UN/CEFACT Technical Specification has been developed
More information1 Scope. 2 Normative References. WORKING DRAFT ISO/IEC ISO/IEC 11404:xxxx WD3
WORKING DRAFT ISO/IEC ISO/IEC 11404:xxxx WD3 Information technology Programming languages, their environments and system software interfaces Language-independent General purpose datatypes (GPD) [Working
More information7. Relational Calculus (Part I) 7.1 Introduction
7. Relational Calculus (Part I) 7.1 Introduction We established earlier the fundamental role of relational algebra and calculus in relational databases (see 5.1). More specifically, relational calculus
More informationISO/IEC TR TECHNICAL REPORT
TECHNICAL REPORT ISO/IEC TR 22250-1 First edition 2002-02-15 Information technology Document description and processing languages Regular Language Description for XML (RELAX) Part 1: RELAX Core Technologies
More informationDictionary Driven Exchange Content Assembly Blueprints
Dictionary Driven Exchange Content Assembly Blueprints Concepts, Procedures and Techniques (CAM Content Assembly Mechanism Specification) Author: David RR Webber Chair OASIS CAM TC January, 2010 http://www.oasis-open.org/committees/cam
More information- MXV (Model-driven XML Vocabulary) Design and Productivity Tools
A practical Example: Model-driven Semantic Interoperability using - Open Standards and - MXV (Model-driven XML Vocabulary) Design and Productivity Tools VERSION 2.2 (NDR 2.1) Data Management Solutions,
More informationChapter 2 Overview of the Design Methodology
Chapter 2 Overview of the Design Methodology This chapter presents an overview of the design methodology which is developed in this thesis, by identifying global abstraction levels at which a distributed
More informationGlobal Justice XML Data Model.
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 Global Justice XML Data Model Naming and Design Rules Draft Version 0.4, 23 August 2005 Editor: Webb Roberts, Georgia Institute of Technology Contributors: Abstract:
More informationOne of the main selling points of a database engine is the ability to make declarative queries---like SQL---that specify what should be done while
1 One of the main selling points of a database engine is the ability to make declarative queries---like SQL---that specify what should be done while leaving the engine to choose the best way of fulfilling
More informationSemantic Information Modeling for Federation (SIMF)
Purpose Semantic Information Modeling for Federation (SIMF) Overview V0.2-04/21/2011 The Architecture Ecosystem SIG of the Object Management Group (OMG) is in the process of drafting an RFP focused on
More informationOCL Support in MOF Repositories
OCL Support in MOF Repositories Joachim Hoessler, Michael Soden Department of Computer Science Technical University Berlin hoessler@cs.tu-berlin.de, soden@cs.tu-berlin.de Abstract From metamodels that
More information6.001 Notes: Section 15.1
6.001 Notes: Section 15.1 Slide 15.1.1 Our goal over the next few lectures is to build an interpreter, which in a very basic sense is the ultimate in programming, since doing so will allow us to define
More informationD2.5 Data mediation. Project: ROADIDEA
D2.5 Data mediation Project: ROADIDEA 215455 Document Number and Title: D2.5 Data mediation How to convert data with different formats Work-Package: WP2 Deliverable Type: Report Contractual Date of Delivery:
More informationCS112 Lecture: Variables, Expressions, Computation, Constants, Numeric Input-Output
CS112 Lecture: Variables, Expressions, Computation, Constants, Numeric Input-Output Last revised January 12, 2006 Objectives: 1. To introduce arithmetic operators and expressions 2. To introduce variables
More informationSemantics for and from Information Models Mapping EXPRESS and use of OWL with a UML profile for EXPRESS
Semantics for and from Information Models Mapping EXPRESS and use of OWL with a UML profile for EXPRESS OMG Semantic Information Day March 2009 David Price Eurostep and Allison Feeney NIST Agenda» OASIS
More informationUsing UML To Define XML Document Types
Using UML To Define XML Document Types W. Eliot Kimber ISOGEN International, A DataChannel Company Created On: 10 Dec 1999 Last Revised: 14 Jan 2000 Defines a convention for the use of UML to define XML
More informationInternational Standards Organisation. Parameterized Derived Types. Fortran
International Standards Organisation Parameterized Derived Types in Fortran Technical Report defining extension to ISO/IEC 1539-1 : 1996 {Produced 4-Jul-96} THIS PAGE TO BE REPLACED BY ISO CS ISO/IEC 1
More informationQuick Guide to CAM Dictionaries
Quick Guide to CAM Dictionaries Building and using canonical XML components dictionaries for CAM Author: David RR Webber Chair OASIS CAM TC April, 2010 http://www.oasis-open.org/committees/cam 1 June,
More informationObject-Oriented Software Engineering Practical Software Development using UML and Java
Object-Oriented Software Engineering Practical Software Development using UML and Java Chapter 5: Modelling with Classes Lecture 5 5.1 What is UML? The Unified Modelling Language is a standard graphical
More information