Re: [ubl-lcsc] Latest Models for Code Lists - draft 6 of the UBL1.0 spreadsheets

[Tim McGrath <tmcgrath@portcomm.com.au>]

One of the others tasks to arise from updating our code list mechanism is
that we now the the opportunity to add 'names' to code 'content'.  In other
words we can have "1" = "Original", etc.. (adding descriptive labels to code
values).  

But his means we need to revisit the text files of list values prepared (but
not published) for 1.0-Beta.

Do I hear a volunteer to take a first pass at this? i.e. design a way of
describing this and then populating it?

Tim McGrath wrote:

Please find attached the latest spreadsheets for draft 6 of the 1.0 release.

These incorporate the 'Data Type' for all BBIEs, but only the code lists we consider 'standard' have a specialised data type name.  The placebo codes are user-defined and must remain unspecialised in out package.  It will be up to implementors to create and apply their own specialised data types (based on this model), if they want schema validation of their code values.

The accompanying spreadsheet (UBL-SpecialisedDataTypes-draft6.xls) defines the values for each of the required specialised data type's supplementary components.

This should bring us into line with the CCTS structures and hopefully we can reflect this into the new schemas.

I think it also sets the template for how we could apply other types of specialised data types in the future.

Can I ask Michael to check this has all he needs to create the schemas. I would also appreciate anyone's comments on the values proposed and also  whether we now need to maintain the old Code List Catalog model.

PS i have also updated and included the change log for this delta.

To unsubscribe from this mailing list (and be removed from the roster of the OASIS TC), go to http://www.oasis-open.org/apps/org/workgroup/ubl-lcsc/members/leave_workgroup.php.

-- 
regards
tim mcgrath
phone: +618 93352228  
postal: po box 1289   fremantle    western australia 6160