[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]
Subject: Re: [ubl-comment] To define propietary business documents
Hi Todd, It happens to me that I can't get rid of code sometimes. For example, when I want to model a small enumeration like whether a ship status is "loading", "discharge", or "transit", it would be strange to use id. What CCT should I model a ShipStatus? Id (ShipStatusId), Code (ShipStatusCode), Name (ShipStatusName), or Text (ShipStatusText)? Seems code sounds more appropriate. I may be wrong since I still don't have full understanding of the specs, as I said. What do you think? Best regards, Thomas On Sun, 30 Jun 2002, Todd Boyle wrote: > Use ID. Forget about code. Codes are evil. :-) > > Some owners of list data will use the CCTS "Code" type. > When you encounter them you can > > - wrapper them as an Identifier type, or > > - if the set is small or static, in your market or community then, put the > whole set or subset, in your runtime, or XML schema. But don't > attempt to put the entire EDIFACT code lists, like > CommerceOne did with their XDR version of XCBL, "XCBL30.xdr" > which is 691Kb. > http://www.google.com/search?q=AmericanPsychiatricAssociationDiagnosticStatisticalManualOfMentalDisorders
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]
Powered by eList eXpress LLC