[ubl-ndrsc] Representation Terms

["Stephen Green" <stephen_green@seventhproject.co.uk>]

I'm going through the CCT Datatype (Representation Term) Schema and I have a few issues still

outstanding really from the last instance sample

generation / review cycle

 

1.  In Measure and in Quantity we still have

unitCodeListID 

unitCodeListAgencyID

unitCodeListAgencyName
as supplementary components

 

but in Code we have this restricted to

*none*

 

and in Amount we have it defined in the CCT Schema as

currencyID

codeListVersionID

 

My question/issue is:

 

with Code:

the codelist mechanism might have to be very good to avoid

need for any meta data at all - can we guarantee this?

Shouldn't we still have

listID

listAgencyID

listAgencyName
?

 

with Amount a CCT issue really:

we seem to have a version ID

but is it decided and clear to all that there is

just the one codelist that can be used so that we don't even

have to specify what it is but only which version?

 

 

2.  Just a request for feedback from the last NDRSC

call (unavoidable that I couldn't make it) regarding

my issue of 

type="xsd:token"

missing from some of the elements in the Schema

 

3. Who will be editing the DT (CCT DT) and RT (UBL DT) Schemas?

Will it still be Gunther and Garrett?

Will it still be in collaboration / synchronisation with OAG and/or ATG?

How will it fit with the schedule? and tools work?

We'll presumably need any changes introduced prior to instance

generation. There may be some impact on this and on FPSC work

if the listID and listAgencyID are put back into the CCT DT Schema.

I don't see what can be done, if anything at this stage, about the

Amount supplementary components and how to specify the

codeListID

codeListAgencyID

and

codeListAgencyName

but if it were possible and agreed we'd need a suitable schedule for this

-

Otherwise perhaps something should be put into the Documentation

 

 

Sorry to keep pestering - just last minute rush

 

All the best

 

Many thanks

 

Steve