[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Re: Customisation Document
On 04/21/2004 03:06 PM, Stephen Green wrote: > Thanks Eduardo. It now makes sense that context values would in fact > be coded enumerations. I just couldn't see the link between the two. > I guess it probably did no harm to draw attention to this rather clever > use of codes for context drivers as it helps clarify the section asking > that there be controlled vocabulary of the context values. This shows > how that can be done. I wonder if it is apparent enough (though it might > be too late now) or whether something could be added to the paragraph > about control of vocabulary for contexts to underline the use of coded > values in achieving such controlled vocabulary. This is if I've got the > right grasp of the association with codes of course. Yes and no ;) In section 3.3 the guidelines say: "There is no pre-set list of values for each driver. Users are free at this point to use whatever codification they choose, but they should be consistent; therefore while not obliged to do so, communities of users are strongly encouraged to always use the same values for the same context (that is, those who use "U.S.A" to indicate a country in the North American Continent, should not intermix it with "US" or "U.S." or "USA"). And *if a particular standardized codification is used, it should also be identified in the documentation.* (Some standard sets of values are provided in the CCTS specification.)" Emphasis mine. The end of this section refers specifically to how to identify that 'standardized codification'. I always assumed that the proximity of the two paragraphs was enough to make things clear, but apparently not. Perhaps the sentence "For each of the context drivers (Geopolitical, IndustryClassification, etc.) the following characteristics should also be specified" should be changed to read: "For each of the context drivers (Geopolitical, IndustryClassification, etc.) the following characteristics should also be specified with reference to its value" Would that make things clearer? Jon, is it too late to make this change? If not, let me know so I can also change the original. Thanks. > > Steve > > ----- Original Message ----- > From: "Eduardo Gutentag" <Eduardo.Gutentag@Sun.COM> > To: "Stephen Green" <stephen_green@seventhproject.co.uk> > Cc: <ubl@lists.oasis-open.org>; <Jon.Bosak@Sun.COM> > Sent: Wednesday, April 21, 2004 10:49 PM > Subject: Re: Customisation Document > > > >>Stephen, >> >>the values used for context drivers for a given customization are supposed >>to be taken from codelists, indeed, but when this was written, and until >>a few days ago, the status of such was so unclear and fluid that it would >>not have made sense for this paper to address this issue in any other way >>than as it does currently. >> >> >> >>On 04/21/2004 02:09 PM, Stephen Green wrote: >> >>>Is this quite a sizable error? >>> >>>In the Customisation Document, Section 3.3 - >>> >>>"... >>> >>>For each of the context drivers (Geopolitical, IndustryClassification, >>>etc.) the following characteristics should also be specified (a later >>>version will provide the requisite attributes for doing so): >>> >>> * >>> >>> CodeListID - string: The identification of a list of codes. Can be >>> used to identify the URL of a source that defines the set of >>> currently approved permitted values. >>> >>> * >>> >>> CodeListAgencyID - string: An agency that maintains one or more >>> code lists. Defaults to the UN/EDIFACT data element 3055 code > > list. > >>> * >>> >>> CodeListAgencyName - string: The name of the agency that maintains >>> the code list. >>> >>> * >>> >>> CodeListName - string: The name of a list of codes. >>> >>> * >>> >>> CodeListVersionID - string: The Version of the code list. >>> Identifies the Version of the UN/EDIFACT data element 3055 code > > list. > >>> * >>> >>> languageID - string: The identifier of the language used in the >>> corresponding text string [ISO639] >>> > > <http://ibiblio.org/bosak/ubl/UBL-1.0/doc/cm/cs-ubl-cmsc-cmguidelines-1.0.ht > ml#ISO639> > >>> * >>> >>> CodeListUniformResourceID - string: The Uniform Resource >>> Identifier that identifies where the code list is located. >>> >>> * >>> >>> CodeListSchemeUniformResourceID - string: The Uniform Resource >>> Identifier that identifies where the code list scheme is located. >>> >>> * >>> >>> Content: A value or set of values taken from the indicated code >>> list or classification scheme. >>> >>> * >>> >>> Name: The textual equivalent of the code content. >>> >>> >>> >>>..." >>> >>> >>> >>>These appear to me to be erroneous as characteristics for context >>>drivers but rather they are attributes for codelists. >>> >>> >>> >>>Steve >>> >> >>-- >>Eduardo Gutentag | e-mail: eduardo.gutentag@Sun.COM >>Web Technologies and Standards | Phone: +1 510 550 4616 x31442 >>Sun Microsystems Inc. | W3C AC Rep / OASIS BoD >> > > -- Eduardo Gutentag | e-mail: eduardo.gutentag@Sun.COM Web Technologies and Standards | Phone: +1 510 550 4616 x31442 Sun Microsystems Inc. | W3C AC Rep / OASIS BoD
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]