codelist — archive

[Ken Holman]

Hi folks, I'm struggling with how much to put (or not to put) into a conformance clause for genericode. We certainly do not want to restrict *how* or *where* genericode is being used. For example, I've posted in the UBL group a distillation of the International Data Dictionary spreadsheets as a number of genericode files. This makes the information in these spreadsheets available as an XML resource for application developers to read and load up their application structures with language-based definitions suitable for pop-ups or help information. The main post is here: http://lists.oasis-open.org/archives/ubl/200707/msg00027.html And there has been some discussion on UBL-Dev about things like column names: http://lists.oasis-open.org/archives/ubl-dev/200707/msg00006.html I chose genericode because it can be used as a general-purpose keyed-table (used for data representation), unlike other table structures such as CALS tables (used for data presentation) that differ. Interestingly, my current thoughts on this are to use