← Prev in month
← Prev in thread
Next in thread →
Next in month →
codelist rule RE: [ubl] Agenda for Atlantic UBL TC call 3 May 2006
MHonArc v2.5.0b2 --> ubl message [Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home] Subject: codelist rule RE: [ubl] Agenda for Atlantic UBL TC call 3 May 2006 From: To: Date: Wed, 03 May 2006 08:26:38 -0600 Oops! Should read: ... > so then at least the 'listURI' attributes need to be * default * > so that these codelists can be restricted in implementations. Quoting : > The thinking - was it on the Pacific call? - was that we > want to provide genericode files even for the ATG2 codelists > so then at least the 'listURI' attributes need to be fixed > so that these codelists can be restricted in implementations. > In short I think the NDR should allow both fixed and default > and spreadsheet/modellers should specify which is used for which > but if this had to be simplified (such as for EF) I'd say the > simplest is to make all default and either put that in the rule > or just in the spreadsheet. (By 'spreadsheet' I mean uDT.) > > Thanks > > Steve > > > Quoting Grimley Michael J NPRI <>: > >> >> I have just been informed that I have to support a meeting @ 1300 >> that requires travel; therefore, I will be unable to attend today's >> call. >> >> >>> SG: We need an agreement in this week's Atlantic call >>> regarding the rule about code list attributes, default >>> vs. fixed -- we only want default, and at the moment they >>> are all fixed; see emails over the last week from TM and SG. >>> We need to finalize this. >> >> >> I have no objection to making them 'default'. >> >> Do we want to create two rules, one for the Code Lists we adopt from >> ATG 2 (these can remain fixed) and one for all others (where we >> allow default)? >> >> >> >>
← Prev in month
← Prev in thread
Next in thread →
Next in month →