OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help

ubl-lcsc message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]

Subject: Re: [ubl-lcsc] Latest Models for Code Lists - draft 6 of the UBL 1.0 spreadsheets


1. In the Specialised DataTypes model, shouldn't there really be a separate
ABIE for each
Code? I realise there effectively is but how about having them one under the
other as sets of rows
rather than as extra columns - it would help any mapping such as to a
worksheet, as with the other models? We'd need just one set of the extra
columns that you have already.
I do accept though that this involves duplication but I get the feeling a)
that it would help if we
later had to add further code datatypes, b) it would help those who might
wish to add their own codleists
and c) I reckon folk could then use the same spreadsheet to create
non-codelist Specialised DataTypes.

2. In the other models, will we eventually delete columns H and J?


----- Original Message -----
From: "Tim McGrath" <tmcgrath@portcomm.com.au>
To: <ubl-lcsc@lists.oasis-open.org>
Sent: Wednesday, March 03, 2004 7:18 AM
Subject: [ubl-lcsc] Latest Models for Code Lists - draft 6 of the UBL 1.0

> Please find attached the latest spreadsheets for draft 6 of the 1.0
> 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.
> --
> regards
> tim mcgrath
> phone: +618 93352228
> postal: po box 1289   fremantle    western australia 6160


> To unsubscribe from this mailing list (and be removed from the roster of
the OASIS TC), go to

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]