[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Re: [ubl-ndrsc] Re: [ubl-lcsc] NDR Rule [R5]
Tim McGrath wrote: > When we say clarity, we mean.... > > a. the issue is not "XML names" but "UBL Names" - it is unclear what > "XML names"(R5) and "Names" (R7) mean in this context. I think it is clear (UBL names of the XML elements, or, to put it differntly, but with the same meaning, the names of the UBL xml elements). But is not *made* clear. Yes, the statement could be more precise. > b. neither R5 nor R7 prevent punctuation characters appearing in the UBL > Name (and by definition the tag name derived from it). for example > apostrophe is not a separator (R5), the OED says it is spelt "e-mail" > not "email"(R7). we believe we want to avoid anything but a-Z and 0-9 > ever being used in UBL Names. this aids consistency of naming and also > avoids some of the syntacially issues with programming applications that > generate the schemas. > It seems we can identify and exclude each character individually (and > argue about what 'non letter characters' mean) or just say "we only > allow a to Z and 0 to 9" and be done with it. The problem, as I see it, and which you questioned in another message but I will answer in this one because why not, the problem is that NDR is, or will be, used not only for UBL in OED, but also for UBL or UBL derived or UBL compliant or any other combination of UBL in other languages. When I said in a previous message that "it is not in our purview" I meant not ISO 8859 languages but others (such as Hebrew, Arabic, South East Asian, Chinese, Japanese, Tibetan, Korean, etc. etc. etc.). I think that listing the range of characters in ISO 8859 1/7/15 and then saying something like "and their equivalents in other scripts" would be enough to give this a non English centric flavour (see? I do know my OED too!) IOW what I'm proposing is to say that we use the equivalent of [a-zA-Z] in a manner that includes scripts other than the one used by English but remains firmly rooted in the Latin script, which is the one most of us know. However, if this is too controversial or will cause any delays, then to hell w/it, let's just do l'anglais. > > NB as Mark points out the CCTS has its own rules which will apply to the > Dictionary Entry Names, but that is not the major issue here. the > primary concern is what we are allowing in the UBL Name. > > > Lisa-Aeon wrote: > >> Mark, >> In our NDR/LCSC joint QA Team meeting today we discussed the above rule >> which now reads: >> >> [R5] XML names constructed from dictionary entry names must not include >> periods, spaces, or other separators. >> >> I went back and looked through the NDR document and found this: >> >> [R7] Names must not contain non-letter characters unless required by >> language-specific rules. >> >> LCSC is looking for clarity. Their issue is to make sure people do >> not use >> characters that also are used with processing applications, such as >> "-" "*", >> etc. >> >> Do we need to make any changes, or is this sufficient for everyone? >> >> Lisa >> ++++++++++++++++++++++++++++++++++++++++++++++++++++ >> Lisa Seaburg >> AEON Consulting >> Website: http://www.aeon-llc.com >> Email: lseaburg@aeon-llc.com >> Alternative Email: xcblgeek@yahoo.com >> Phone: 662-562-7676 >> Cellphone: 662-501-7676 >> >> "If you obey all the rules, you miss all the fun." >> -Katharine Hepburn >> ++++++++++++++++++++++++++++++++++++++++++++++++++++ >> >> >> --- >> Outgoing mail is certified Virus Free. >> Checked by AVG anti-virus system (http://www.grisoft.com). >> Version: 6.0.474 / Virus Database: 272 - Release Date: 4/18/2003 >> >> > -- Eduardo Gutentag | e-mail: eduardo.gutentag@Sun.COM Web Technologies and Standards | Phone: +1 510 550 4616 x31442 Sun Microsystems Inc. | 1800 Harrison St. Oakland, CA 94612 W3C AC Rep / OASIS TAB Chair
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]