ubl-ndrsc — archive

[Tim McGrath]

 MHonArc v2.5.0b2 -->

















ubl-ndrsc message






[Date Prev]
 | [Thread Prev]
 | [Thread Next]
 | [Date Next]

--

[Date Index]
 | [Thread Index]
 | [List Home]








Subject: Re: [ubl-lcsc] CCT, RT, DT Files with fixed Major:Minor numbering




From: Tim McGrath <tmcgrath@portcomm.com.au>
To: "Stuhec, Gunther" <gunther.stuhec@sap.com>
Date: Fri, 10 Oct 2003 15:51:30 +0800










Gunther,


before you get too excited, can you confirm:


a. Does this code set implementation conform to that used for other code
sets in the Library?  for example, these should be 'standard' code sets using
the mechanisms of our code catalogue.  

b. Where we re-use these codes in the Library BIEs, do they/can they share
a common source?  for example, will your 'currencyID' reference our 'UBL-CodeList-CurrencyCode-Use-1.0-???????.xsd'?


Of course, none of this is an NDR issue - although we did spend time talking
about this on the Joint NDR/LC call 3 weeks ago and no-one at NDR mentioned
you were planning to do this.  


Bear in mind, the code working group and LC have spent several weeks working
on a code set implementation mechanism and don't want to inherit any orphans
at this late stage.


Also, we shall be building the final 1.0 schemas following the Friday teleconference.
 We need to receive the final CCT, RT and DT schemas before then if we are
to use them for UBL 1.0


Some other things for you to consider about the three schema files ....


* in Representationterm.xsd: the word "Representation" is mis-spelt in these
two statements (you have "Repesentation")

<xsd:schema targetNamespace="urn:oasis:names:tc:ubl:DataTypes:1:0-alpha" 
xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:rt="urn:oasis:names:tc:ubl:RepesentationTerms:1:0-alpha" 
xmlns="urn:oasis:names:tc:ubl:DataTypes:1:0-alpha" elementFormDefault="qualified" 
attributeFormDefault="unqualified">

     <xsd:import namespace="urn:oasis:names:tc:ubl:RepesentationTerms:1:0-alpha" 
schemaLocation="RepresentationTerms_1p0-alpha.xsd"/>


* in Representationterm.xsd: it still references the OAGI WG not UBL, as
in...
    <!--OAGI Core Component WG Datatypes based
on ebXML Core Component Specification V1.90-->


* in Representationterm.xsd: what is CodeContent  used for?


* in Representationterm.xsd: there is no definition for the secondary representation
term 'Picture' (the primary is Binary Object).


* in Representationterm.xsd: why aren't Date and Time restrictions of DateTime?
 without this, there is nothing to tell us they are secondary RTs to DateTime.


* in Representationterm.xsd: Indicator is explicitly given only the possible
values 'true' or 'false' - is that what we want to do?  even the CCTS uses
'on/off' as its example.


* in Representationterm.xsd: if 'Rate' is defined as a 'Numeric'  and "Rate
is a value expresses the ratio per specified unit and a rate basis unit."
 what numeric value is used, the ratio per unit or the basis unit?


* in DataTypes.xsd: what are 'QualifiedIdentifier' and 'QualifiedCode'?


* in DataTypes.xsd: you define an DT such as DayType, MonthType, etc...  I
understood from the CCTS that these should be named using the ISO11179 concepts
of Representation Term plus Qualifier.  So shouldn't they be called DayDateTimeType
and MonthDateTimeType ?


* in DataTypes.xsd: how can you define DataTypes that have no Representation
Term (e.g. Duration and Temperature) as it is Representation Term that links
the BIEs to Data Types, when would these ever get used?


Finally, the more i look at these three I cannot understand why we need a
Data Types.xsd - as we only reference Representation terms how will it ever
be used?


Stuhec, Gunther wrote:


  
Hello Tim,

I'm fixing this problems now. 
I made with LanguageCode a suggestion for using the code lists within the representation schema. I have seen that was a positive reaction in the NDRSC, therefore I'm adding the other code lists into the representation term schema, today.

Kind regards,

	Gunther