Thanks Tim & Garret. Good work! (01)
FYI ... (esp. those on the CCT-Rep team) (02)
-------- Original Message --------
Subject: [ubl] UBL and OAG Common Core Component schemas
Date: Thu, 01 Apr 2004 15:54:55 +0800
From: Tim McGrath <tmcgrath@xxxxxxxxxxxxxxx>
To: ubl@xxxxxxxxxxxxxxxxxxxx
CC: Garret.Minakawa@xxxxxxxxxx (03)
It has been a long standing principle that UBL and OAG would try to
align their implementations of schemas for Core Component Types and
Data Types. The intention is that this will provide input into the
work of a mutually agreed upon standards organization such as
UN/CEFACT ATG2 or ISO. (04)
In August 2003 both groups started with a common initial set of
schemas. Since that time these have evolved separately to accommodate
design and implementation issues both within OAGIS 9.0 and UBL 1.0. (05)
As UBL is about to finalize its 1.0 package it is useful to review
these differences and attempt to synchronise our developments. (06)
To this end, Garrett Minakawa (representing OAG) and Tim McGrath
(representing UBL) have reviewed the current OAGIS 9.0 and proposed
UBL 1.0 schemas. (07)
We have identified five areas of misalignment: (08)
1. Naming of Supplementary Components as attributes. (09)
2. Use of XSD normalizedString for code, identifier and text components. (010)
3. Use of XSD built-in dataypes requiring format Supplementary
Component (Date Time, Indicator and Numeric). (011)
4. Restrictions on Binary Object for Graphic, Picture, Sound and Video
data type. (012)
5. Patterns for Indicator data type. (013)
We would like to propose the following immediate course of action to
align these schemas. (014)
Proposed Action Items
------------------------ (015)
1. Naming of Supplementary Components as attributes. (016)
* Analysis: (017)
UBL have adopted a naming convention for Supplementary Components
based on the ObjectClass + PropertyTerm + RepresentationTerm rule that
applies to BIEs. (018)
OAG have informal naming rules inherited from the initial schemas. (019)
* Proposal: (020)
OAG consider adopting the same naming rules as UBL. (021)
2. Use of XSD normalizedString for code, identifier and text components. (022)
* Analysis: (023)
OAG use the built-in XSD type,"token", for all code, identifier and
text components (where there is no specific built-in type, such as
"language"). (024)
UBL uses the built-in XSD type,"normalizedString", for all code and
identifier components and the built-in XSD type,"string", for all text
components (where there is no specific built-in type, such as "language"). (025)
* Proposal: (026)
OAG consider the built-in XSD type,"normalizedString", for all code,
identifier and text components (where there is no specific built-in
type, such as "language"). (027)
UBL consider the built-in XSD type,"normalizedString", for all text
components (where there is no specific built-in type, such as "language"). (028)
3. Use of XSD built-in dataypes requiring format Supplementary
Component(Date Time, Indicator and Numeric). (029)
* Analysis: (030)
OAG explictly define an attribute for "format" in the Core Component
Type schema. This is then restricted(prohibited) in the data type schema. (031)
UBL do not define an attribute for "format" in the Core Component Type
schema. This follows UBL Naming and Design rule [STD1]:
"For every ccts:CCT whose supplementary components map directly onto
the properties of a built-in xsd:datatype, the ccts:CCT MUST be
defined as a named xsd:simpleType in the ccts:CCT schema module." (032)
* Proposal: (033)
UBL consider relaxing NDR rule STD1 to allow adoption of the OAG approach. (034)
4. Restrictions on Binary Object for Graphic, Picture, Sound and Video
data type. (035)
* Analysis: (036)
OAG define different attributes for use in data types derived from
Binary Object (Graphic, Picture, Sound and Video). For example, in OAG
a Graphic type has characterSetCode,encodingCode,URI and filename (037)
whereas in UBL, a Graphic type has only mimeCode. (NB this is actually
a UBL modeling error, it was supposed to have all Supplementary
Components except the mimeCode). (038)
* Proposal: (039)
UBL consider adopting OAG restrictions for Graphic, Picture, Sound and
Video data type. (040)
5. Patterns for Indicator data type. (041)
* Analysis: (042)
OAG define a pattern of "true" or "false" for their Indicator data type. (043)
UBL has no pattern. (044)
* Proposal: (045)
UBL consider adopting OAG pattern of "true" and "false" for the
Indicator data type. (046)
Open Work Items
---------------
We also identified some work areas that both OAG and UBL could jointly
pursue. These are: (047)
6. Namespace. OAGIS and UBL use different notation and naming in their
namespace declarations. This should not be a major issue since it is
expected that OAGIS and UBL will eventually use the same set of common
core component schema files once they are officially approved and
hosted by a mutually agreed upon international standards organization
such as UN/CEFACT ATG2 or ISO. Once this occurs, OAGIS and UBL will
simply reference the namespace names adopted by the mutually agreed
upon standards organization. As long as the content of the common core
component schema files remain unchanged, there should be no visible
impact to end users. (048)
7. Annotation. OAGIS and UBL have different documentation/annotation
standards but again, this is not expected to be an issue once the
common core component schema files are implemented by a mutually
agreed upon international standards organization. (049)
8.XML Schema Namespace Prefix. OAGIS uses xs: as the namespace prefix
for http://www.w3.org/2001/XMLSchema. UBL uses the prefix xsd:. As
with namespaces and annotations, this is not expected to be an issue
once the common core component schema files are implemented by a
mutually agreed upon international standards organization. (050)
9. complexType Naming Convention of Representation Terms. UBL has
appended the term “Type” to the name of all representation terms in
“UnspecialisedDataTypes.xsd” (e.g. “AmountType” vs. “Amount”). (051)
10. Name of RepresentationTerms schema (vs. UnspecialisedDataTypes) (052)
11. Abbreviation for Identifier (ID vs. Id) (053)
12. Develop a consistent method for representing prohibited attributes
(and attributes with no changes from the base type) when using
derivation by restriction. (054)
--
regards
tim mcgrath
phone: +618 93352228
postal: po box 1289 fremantle western australia 6160 (055)
_________________________________________________________________
Message Archives: http://ontolog.cim3.net/forum/ontolog-forum/
Subscribe/Unsubscribe/Config:
http://ontolog.cim3.net/mailman/listinfo/ontolog-forum/
Shared Files: http://ontolog.cim3.net/file/
Community Wiki: http://ontolog.cim3.net/wiki/
To Post: mailto:ontolog-forum@xxxxxxxxxxxxxxxx (056)
|