[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: RE: [regrep-cc-review] CC Serialization and UBL-CoreComponentParameters.xsd
True, it is non-normative. Here is some of my thoughs how CoreComponentParameters are related to ccts section 7: <Component>: mapped to section 7.1 and 7.4 <CategoryCode>: [S2] Stored Core Components shall always be defined as one of the four recognized types Basic Core Component, Association Core Component, Aggregate Core Component or Core Component Type. [S46] Stored Business Information Entities shall be based on a stored Aggregate Core Component, Basic Core Component or Association Core Component. They shall never be based on a Core Component Type. <DictionaryEntryName>: [S1] Core Components are a particular category of Registry Classes. As such, all stored Core Components shall include the following Attributes: ... * Dictionary Entry Name (mandatory): The official name of a Core Component. ... [S44] Business Information Entities are a particular category of Registry Classes. As such, all stored Business Information Entities shall include the following Attributes: ... * Dictionary Entry Name (mandatory): The official name of a Business Information Entity. ... <Definition>: [S1] Core Components are a particular category of Registry Classes. As such, all stored Core Components shall include the following Attributes: ... * Definition (mandatory): The semantic meaning of a Core Component. ... [S44] Business Information Entities are a particular category of Registry Classes. As such, all stored Business Information Entities shall include the following Attributes: ... * Definition (mandatory): The semantic meaning of a Business Information Entity. ... <QualifierObjectClass>: [S52] Stored Aggregate Business Information Entities shall include the following Attribute: * Qualifier Term (mandatory): Qualifies the Object Class Term of the associated Aggregate Core Component. <ObjectClass>: [S7] Stored Aggregate Core Components shall include the following Attribute: * Object Class Term (mandatory): A semantically meaningful name for the Object Class that is represented by the Aggregate Core Component. It shall serve as basis for the Dictionary Entry Name of the Aggregate Core Component and for the Dictionary Entry Name of all Basic and Association Core Components that represent Core Component Properties of this Aggregate Core Component. <QualifierPropertyTerm>: [S56] Stored Business Information Entity Properties shall include the following Attributes: * Qualifier Term (optional): Qualifies the Property Term of the associated Core Component Property in the associated Aggregate Core Component. <PropertyTerm>: [S10] Stored Core Component Properties shall include the following Attributes: * Property Term (mandatory): A semantically meaningful name for the characteristic of the Object Class that is represented by the Core Component Property. It shall serve as basis for the Dictionary Entry Name of the Basic or Association Core Component that represents this Core Component Property. ... <QualifierRepresentationTerm>: qualifier for <RepresentationTerm>: [S22] Stored Core Component Types shall include the following Attributes: * Primary Representation Term (mandatory): A semantically meaningful name that forms the basis for the Dictionary Entry Name of the Core Component Type. It can also form the basis for the Dictionary Entry Name of Data Types that are based on the Core Component Type. <QualifierDataType>: qualifier for <DataType>: [S12] Stored Basic Core Component Properties shall be linked to the Data Type that describes the possible values of the Basic Core Component Property. [S58] Stored Basic Business Information Entity Properties shall be linked to the Data Type that describes the possible values of the Basic Business Information Entity Property. This Data Type shall either be the same as the Data Type that is linked to the corresponding Basic Core Component Property or it shall be a more restricted Data Type (i.e. additional and/or more restrictive Content Component Restrictions and/or additional and/or more restrictive Supplementary Component Restrictions). <QualifierAssociatedObjectClass>: qualifier for <AssociatedObjectClass>: [S14] Stored Association Core Component Properties shall be linked to the Aggregate Core Component that describes the structure of the Association Core Component Property. <BusinessTerm>: [S3] Stored Core Components shall include the following Attributes: * Business Term (optional, repetitive): A synonym term under which the Core Component is commonly known and used in a business. Business Terms may be expressed in any language. A Core Component may have several Business Terms or synonyms. [S48] Stored Business Information Entities shall include the following Attributes: ... * Business Term (optional, repetitive): A synonym term under which the Business Information Entity is commonly known and used in the business. Business Terms may be expressed in any language. A Business Information Entity may have several Business Terms or synonyms. ... <Context>: [S45] Stored Business Information Entities shall be based on a stored Business Context. <IndustryClassification>: <Geopolitical>: <BusinessProcess>: <OfficialConstraint>: <ProductClassification>: <BusinessProcessRole>: <SupportingRole>: <SystemCapability>: -------------------------------------------- Antti Jokipii Chief Technology Advisor Republica Corp., R & D Labs Ohjelmakaari 1, 40500 Jyväskylä, Finland E-Mail Antti.Jokipii@republica.fi GSM +358 40 96 16 998 http://www.republica.fi/ http://www.x-fetch.com/ -----Original Message----- From: MCRAWFORD@lmi.org [mailto:MCRAWFORD@lmi.org] Sent: 5. huhtikuuta 2004 13:46 To: Antti Jokipii; dnickull@adobe.com Cc: regrep-cc-review@lists.oasis-open.org; Kathryn.r.Breininger@boeing.com Subject: Re: [regrep-cc-review] CC Serialization and UBL-CoreComponentParameters.xsd UBL should not be considered normative for CCTS. The documentation requirements for ccts are those contained in ccts section 7 - no more, no less. Mark Crawford Research Fellow - LMI XML Lead W3C Advisory Committee, OASIS, RosettaNet Representative Vice Chair - OASIS UBL TC & Chair Naming and Design Rules Subcommittee Chair - UN/CEFACT XML Syntax Working Group Editor - UN/CEFACT Core Components ______ Logistics Management Institute 2000 Corporate Ridge, McLean, VA 22102-7805 (703) 917-7177 Fax (703) 917-7481 Wireless (703) 655-4810 mcrawford@lmi.org http://www.lmi.org "Opportunity is what you make of it" -----Original Message----- From: Antti Jokipii <antti.jokipii@republica.fi> To: Duane Nickull <dnickull@adobe.com> CC: regrep-cc-review@lists.oasis-open.org <regrep-cc-review@lists.oasis-open.org>; Kathryn.r.Breininger@boeing.com <Kathryn.r.Breininger@boeing.com> Sent: Mon Apr 05 06:02:12 2004 Subject: RE: [regrep-cc-review] CC Serialization and UBL-CoreComponentParameters.xsd Hi, In UBL, "documentation" of data elements is defined in CoreComponentParameters (and used as a documentation of generated XML schema elements). Example: <ccts:Component xmlns:ccts="urn:oasis:names:tc:ubl:CoreComponentParameters:1:0-beta"> <ccts:CategoryCode>BBIE</ccts:CategoryCode> <ccts:DictionaryEntryName>Contact. Telephone. Text</ccts:DictionaryEntryName> <ccts:Definition>The number or virtual address of a telephone in a telecommunication system </ccts:Definition> <ccts:ObjectClass>Contact</ccts:ObjectClass> <ccts:PropertyTerm>Telephone</ccts:PropertyTerm> <ccts:RepresentationTerm>Text</ccts:RepresentationTerm> <ccts:DataType>Text.Type</ccts:DataType> </ccts:Component> I think that Data Element Metadata(DEM) should include all information that is in UBL CoreComponentParameters... Also CC serialization format could be based on CoreComponentParameters if we add there parts that are missing (like UUID, version information, etc). -----Original Message----- From: Duane Nickull [mailto:dnickull@adobe.com] Sent: 1. huhtikuuta 2004 0:14 To: Antti Jokipii Cc: regrep-cc-review@lists.oasis-open.org; Kathryn.r.Breininger@boeing.com Subject: Re: [regrep-cc-review] CC Serialization and UBL-CoreComponentParameters.xsd Antti: Is it possible for you to make a presentation to the registry group on what aspects you suggest we review? There is a lot of information there and it would be more efficient to have this done by phone. I can ask Kathryn to put this on the agenda. Thanks Duane Antti Jokipii wrote: >Hi, > >I think that UBL CoreComponentParameters should be reviewed... > >Beta: http://www.oasis-open.org/committees/ubl/lcsc/UBLv1-beta/xsd/common/UBL-CoreComponentParameters-1.0-beta.xsd > >-------------------------------------------- >Antti Jokipii >Chief Technology Advisor >Republica Corp., R & D Labs >Ohjelmakaari 1, 40500 Jyväskylä, Finland >E-Mail Antti.Jokipii@republica.fi >GSM +358 41 57 186 99 >http://www.republica.fi/ >http://www.x-fetch.com/ > >To unsubscribe from this mailing list (and be removed from the roster of the OASIS TC), go to http://www.oasis-open.org/apps/org/workgroup/regrep-cc-review/members/leave_workgroup.php. > > > -- Senior Standards Strategist Adobe Systems, Inc. http://www.adobe.com To unsubscribe from this mailing list (and be removed from the roster of the OASIS TC), go to http://www.oasis-open.org/apps/org/workgroup/regrep-cc-review/members/leave_workgroup.php. To unsubscribe from this mailing list (and be removed from the roster of the OASIS TC), go to http://www.oasis-open.org/apps/org/workgroup/regrep-cc-review/members/leave_workgroup.php.
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]