WG: Precise minutes AW: AW: Updates to Schema generations

["Michael Dill" <dill2@gefeg.com>]

Hi,
this are the first conclusion of the Friday's 14:00 CET call
we do have very short and precise minutes,marked with #
Michael

-----Ursprüngliche Nachricht-----
Von: Tim McGrath [mailto:tmcgrath@portcomm.com.au]
Gesendet: Freitag, 19. März 2004 10:12
An: David Kruppke
Cc: Stephen Green; Michael Dill
Betreff: Re: AW: Updates to Schema generations


thank you once again for the prompt turnaround on these schemas.

I have a few comments to make.

1. Reusable: TaxSchema.Currency now refers to the appropriate
specialised datatype
does this mean you are changing the values in EDIFIX and not loading
them from the spreasheets?  These type of changes are being made as part
of the draft 9 update and you should not make them to your models
directly but await the next draft.
PS i don't think we asked you to fix this :-[
# no action required


2. Core Component Types schema
we still need the  'format' attribute for DateTime, Numeric and
Indicator.(as stephen indicated)
#add these three suppl components as of ccts to the xsd;no inbuilt-DTypes;

3.1 Unspecialised Data Types schema
#no action;it's OK
why is it we get different metadata in the documentation between CCT and
UDT?  for example...
in CCT schema we find...
                <ccts:Component>
                    <ccts:CategoryCode>CCT</ccts:CategoryCode>
                    <ccts:DictionaryEntryName>Quantity.
Type</ccts:DictionaryEntryName>
                    <ccts:Definition>A counted number of non-monetary
units possibly including fractions.</ccts:Definition>
                    <ccts:ObjectClass>Quantity</ccts:ObjectClass>
                    <ccts:PropertyTerm>Type</ccts:PropertyTerm>
                </ccts:Component>
and in UDT schema we find...
        <ccts:Component>
          <ccts:CategoryCode>DT</ccts:CategoryCode>
          <ccts:DictionaryEntryName>Amount. Type</ccts:DictionaryEntryName>
          <ccts:Definition>A number of monetary units specified in a
currency where the unit of the currency is explicit or
implied.</ccts:Definition>
          <ccts:RepresentationTerm>Amount</ccts:RepresentationTerm>
        </ccts:Component>
(one has RepresentationTerm and the other has ObjectCLass and
PropertyTerm)??

3.2 Specialised Data Type schema
I had hoped you would have made this empty.  the purpose of this run of
schemas was to test the use of only code list schemas and leave SDT
empty.  this was the first change requested.  by leaving SDT as the code
list schema - we don't proove anything.  I am afraid it will have to be
done this way (together with the related changes not yet implemented).
 But now, we may as well hold off until draft 9 models are built -
within the next 24 hours.
#we understand: 1. DK should create one empty spec DT xsd just containing a
Namespace import; rename derived code types into SDT (like CurrencyCode )
using the RepTermQualifier for naming; BBIE shall use the new
CodeListXSD(=new SDT) directly

4. Code List schemas.
Toward the end of the schema you list the supplementary component
attributes - but leave them empty, as in...

     <xsd:attribute name="name" type="xsd:string" use="optional"/>
        <xsd:attribute name="codeListID" type="xsd:normalizedString"
use="optional"/>
        <xsd:attribute name="codeListAgencyID"
type="xsd:normalizedString" use="optional"/>
        <xsd:attribute name="codeListAgencyName" type="xsd:string"
use="optional"/>
        <xsd:attribute name="codeListName" type="xsd:string"
use="optional"/>
        <xsd:attribute name="codeListVersionID"
type="xsd:normalizedString" use="optional"/>
        <xsd:attribute name="codeListURI" type="xsd:anyURI" use="optional"/>
        <xsd:attribute name="codeListSchemeURI" type="xsd:anyURI"
use="optional"/>
        <xsd:attribute name="languageID" type="xsd:language"
use="optional"/>

They should have the relevant values populated as in (using currency
code as an example)...
     <xsd:attribute name="name" type="xsd:string" use="optional"/>
        <xsd:attribute name="codeListID" type="xsd:normalizedString"
fixed="ISO 4217 Alpha"/>
        <xsd:attribute name="codeListAgencyID"
type="xsd:normalizedString" fixed="6"/>
        <xsd:attribute name="codeListAgencyName"
type="xsd:string" fixed="United Nations Economic Commission for Europe"/>
        <xsd:attribute name="codeListName"
type="xsd:string" fixed="Currency"/>
        <xsd:attribute name="codeListVersionID"
type="xsd:normalizedString" fixed="0.3"/>
        <xsd:attribute name="codeListURI"
type="xsd:anyURI"
fixed="http://www.bsi-global.com/Technical%2BInformation/Publications/_Publi
cations/tig90x.doc"/>
        <xsd:attribute name="codeListSchemeURI"
type="xsd:anyURI"
fixed="urn:oasis:names:tc:ubl:codelist:CurrencyCode:1:0-draft-8.31"/>
        <xsd:attribute name="languageID" type="xsd:language" fixed="en"/>

#1 OK
#2
CodeListNamespacePrefixID
CodeListDescription
CodeListCredits
The above mentioned Information does not directly appear in a schema.



Thats all for now, but we should be able to give you a fuller brief
after the friday call.