Re: SV: [ubl-psc] UBL 2.1 Instance files for CPFR

["G. Ken Holman" <gkholman@CraneSoftwrights.com>]

At 2010-04-14 20:20 +0200, Oriol Bausą Peris wrote:
>Maybe the codelists should be done only in English.

I think providing more information is better than providing less information.

>Arianna, I can generate the codelists in 
>Genericode, but I need to know the metadata as you state in the first point.

Here is what I see in Arianna's prototype:

     <Identification>
         <ShortName>ActivityCode</ShortName>
         <LongName xml:lang="en">Activity code 
for the contracting authority</LongName>
         <Version>2.1</Version>

The version should be the version of the code 
list, not the version of UBL.  The version should 
probably reflect the version of the list from 
where you obtained the values.  For example, for 
Payment Means the version is "D03A".

         <CanonicalUri/>
         <CanonicalVersionUri/>
         <LocationUri/>

Following the Payment Means code list as a model, I recommend the following:

<CanonicalUri>urn:oasis:names:specification:ubl:codelist:gc:ActivityCode</CanonicalUri>
<CanonicalVersionUri>urn:oasis:names:specification:ubl:codelist:gc:ActivityCode-2.1</CanonicalVersionUri>
<LocationUri>http://docs.oasis-open.org/ubl/os-UBL-2.1/cl/gc/default/ActivityCode-2.1.gc</LocationUri>

If there is a URI from where you obtained these 
values, you can add the following:

<AlternateLocationUri>...uri...</AlternateLocationUri>

         <Agency>
             <LongName>OASIS Universal Business Language</LongName>
         </Agency>

<Agency>
  <LongName xml:lang="en">OASIS Universal Business Language</LongName>
  <Identifier>UBL</Identifier>
</Agency>

     </Identification>
     <ColumnSet>
         <Column Id="Code" Use="required">
             <ShortName>Code</ShortName>
             <Data Type="string"/>
         </Column>
         <Column Id="Name" Use="optional">
             <ShortName xml:lang="en">Name</ShortName>
             <Data Type="string"/>
         </Column>
         <Column Id="Nombre" Use="optional">
             <ShortName xml:lang="es">Nombre</ShortName>
             <Data Type="string"/>
         </Column>
         <Key Id="CodeKey">
             <ShortName>CodeKey</ShortName>
             <ColumnRef Ref="Code"/>
         </Key>
     </ColumnSet>

I recommend the following, preserving the Spanish 
column, identifying the language of the data (in 
addition to defining the language of the short 
name which was already done) and changing the 
case of the identifiers to be consistent with the 2.0 code lists:

     <ColumnSet>
         <Column Id="code" Use="required">
             <ShortName>Code</ShortName>
             <Data Type="string"/>
         </Column>
         <Column Id="name" Use="optional">
             <ShortName xml:lang="en">Name</ShortName>
             <Data Type="string" Lang="en"/>
         </Column>
         <Column Id="nombre" Use="optional">
             <ShortName xml:lang="es">Nombre</ShortName>
             <Data Type="string" Lang="es"/>
         </Column>
         <Key Id="codekey">
             <ShortName>CodeKey</ShortName>
             <ColumnRef Ref="Code"/>
         </Key>
     </ColumnSet>

>There is another point that we need to take into 
>account when creating the codelists: Most of 
>these data sets follow Spanish and EU rules. 
>It's not only a matter of translation but of 
>alignment of codes in different countries, for 
>instance, when talking about types of evidence, 
>This work is still on progress and should be 
>agreed in a forum like BII or CEFACT before creating the list.
>
>About the XML examples, I have plenty of samples 
>for the etendering documents, but all them are 
>using CODICE namespaces and are in Spanish 
>language. Please, tell me how do you want me to 
>proceed, use the UBL 2,1 schemas to validate the 
>instances, translate the contents of textual elements?

Personally I have no problems with Spanish 
language instances, validating against the UBL 
2.1 schemas, without translating the text.

>what about codelists that point to CODICE published codelists?

Sorry, Oriol, I do not understand this 
abbreviated question.  Are the CODICE published 
code lists already in genericode?

I hope this helps.

. . . . . . . . . . . . . . Ken

--
XSLT/XQuery training:         San Carlos, California 2010-04-26/30
Principles of XSLT for XQuery Writers: San Francisco,CA 2010-05-03
XSLT/XQuery training:                 Ottawa, Canada 2010-05-10/14
XSLT/XQuery/UBL/Code List training: Trondheim,Norway 2010-06-02/11
Vote for your XML training:   http://www.CraneSoftwrights.com/o/i/
Crane Softwrights Ltd.          http://www.CraneSoftwrights.com/o/
G. Ken Holman                 mailto:gkholman@CraneSoftwrights.com
Male Cancer Awareness Nov'07  http://www.CraneSoftwrights.com/o/bc
Legal business disclaimers:  http://www.CraneSoftwrights.com/legal