the other option is to put these terms in our controlled vocabulary and allow them that way. but i like Jon's suggestion better - including the use of Un rather than Non On 26/05/12 2:31 AM, Jon Bosak wrote: Thanks very much to Ken and others who confirmed that, in fact, CCTS 2.01 does prohibit camel case in DENs. One way around this is to observe that our rules make the Oxford English Dictionary normative and that both "pre" and "post" are recognized with word entries in that dictionary, though clearly the editors disapproved of such usages. Of "post" as "the Latin preposition meaning 'after'" used "with English words and phrases" the editors say "Usu. found in contexts where _after_ would be equally appropriate and more agreeable", but they nevertheless give four recent citations beginning in 1965 for uses no more egregious than what we would have here. "Non" also gets a word entry, but no citations showing it appearing outside certain Latin phrases used in English; we might actually stretch the rule here, but I don't think we have to. So one solution is to make the DENs Notification Requirement. Post Event Notification Duration. Measure Notification Requirement. Pre Event Notification Duration. Measure Transportation Service. Nonsupported_ Transport Equipment. Transport Equipment Transportation Service. Nonsupported_ Commodity Classification. Commodity Classification Or perhaps even better, make the last two Transportation Service. Unsupported_ Transport Equipment. Transport Equipment Transportation Service. Unsupported_ Commodity Classification. Commodity Classification Will either of these work? Jon G. Ken Holman wrote: At 2012-05-25 12:25 -0400, Jon Bosak wrote: I don't understand the problem; as far as I know, none of our NDRs prohibit camel case in DENs. Is there a prohibition of camel case in CCTS? ... G. Ken Holman wrote: [java] Malformed dictionary entry name "Transportation Service. NonSupported_ Commodity Classification. Commodity Classification" because of the presence of camel case [GNR2]. The wording of GNR2 is: UBL XML element and type names MUST be consistently derived from CCTS conformant Dictionary Entry Names. When writing the test that produced the message above, I documented the test as follows: Note that [CTN2] already checks the element name against the property term and representation term, so this test only checks the Dictionary Entry Name. We can relax the camel case in DENs but perhaps add the proviso that we only do this for prefixes ... though I'm not sure I could then properly test for it. Here is the wording from CCTS 2.01: [C25] The components of a Dictionary Entry Name shall be separated by dots. The space character shall separate words in multi-word Object Class Terms and/or multi-word Property Terms. Every word shall start with a capital letter. To allow spell checking of the Directory Entry Names’ words, the dots after Object Class Terms and Property Terms shall be followed by a space character. [Note] The use of CamelCase for Dictionary Entry Names has been considered, but has been rejected for following reasons: • Use of CamelCase will not allow the use of spell checkers • Strict use of CamelCase makes it impossible to use separators (“.”) and therefore doesn’t allow an unambiguous identification of the composing parts of the Dictionary Entry Name. . . . . . . . . Ken -- Public XSLT, XSL-FO, UBL and code list classes in Europe -- Oct 2012 Contact us for world-wide XML consulting and instructor-led training Free 5-hour lecture:
http://www.CraneSoftwrights.com/links/udemy.htm Crane Softwrights Ltd.
http://www.CraneSoftwrights.com/o/ G. Ken Holman mailto:
gkholman@CraneSoftwrights.com Google+ profile:
https://plus.google.com/116832879756988317389/about Legal business disclaimers:
http://www.CraneSoftwrights.com/legal --------------------------------------------------------------------- To unsubscribe, e-mail:
ubl-unsubscribe@lists.oasis-open.org For additional commands, e-mail:
ubl-help@lists.oasis-open.org --------------------------------------------------------------------- To unsubscribe, e-mail:
ubl-unsubscribe@lists.oasis-open.org For additional commands, e-mail:
ubl-help@lists.oasis-open.org begin:vcard fn:Tim McGrath n:McGrath;Tim org:Document Engineering Services email;internet:
tim.mcgrath@documentengineeringservices.com title:Managing Director tel;work:+61893352228 tel;home:+61438352228 tel;cell:+61438352228 url:www.documentengineeringservices.com version:2.1 end:vcard