[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Re: [codelist] Interesting article about extending enumeration listsin XML Schema
I agree, for some clients, it's a very good option, and well worth writing up if you have the time. Cheers, Tony. On Sun, 28 Sep 2008 14:22:36 +0100, Paul Spencer <paul.spencer@boynings.co.uk> wrote: > I have a client that won't accept a different technology, so I just use > XSLT to convert the genericode to XML Schema. That works fine for simple > lists. Maybe we need to document that as an option if people are going > to rule out genericode because of a perceived complexity of validation. > You are welcome to the stylesheet, but it will need a little work to > make it general purpose. > > Regards > > Paul > > > >> -----Original Message----- >> From: Anthony B. Coates (DES) >> [mailto:anthony.coates@documentengineeringservices.com] >> Sent: 28 September 2008 06:40 >> To: codelist@lists.oasis-open.org >> Subject: Re: [codelist] Interesting article about extending enumeration >> lists in XML Schema >> >> >> I would note that genericode doesn't *require* you to do a two-pass >> validation, you could do a single-pass validation with a >> SAX-based parser >> that tracked XPaths and checked values as it went through the document. >> The only implementation that we have at present it two-pass, but perhaps >> we need to communicate better that there are multiple options. Just a >> thought. >> >> Cheers, Tony. >> >> On Thu, 25 Sep 2008 05:23:49 +0100, G. Ken Holman >> <gkholman@cranesoftwrights.com> wrote: >> >> > At 2008-09-25 04:05 +0000, kumar.sydney@gmail.com wrote: >> >> Came across this interesting article. >> > >> > Yes, I also saw reference to this and it was in today's Robin Cover >> > summary. >> > >> >> Rules out genericode based approach in the study. >> >> >> >> http://www.ibm.com/developerworks/library/x-extenum/ >> > >> > Sure he does ... but from what I read his proposal doesn't address >> > everything that genericode does for deployments such as UBL because of >> > his focus. >> > >> > The only genericode lists that are "extended" in UBL are those without >> > definition ... that is to say they are a restriction of an >> infinite set >> > of all possible values. >> > >> > I see using genericode with context/value association allowing >> different >> > users to have different restrictions on lists without having different >> > schemas. >> > >> > Furthermore genericode with context/value association allows different >> > restrictions on the same enumeration used in different contexts of the >> > one document. I don't believe this can be addressed in W3C >> Schema when >> > using global types. >> > >> > While, yes, you could put value-level meta data and list-level >> meta data >> > in appinfo constructs in a W3C Schema enumeration, genericode >> allows one >> > to selectively use the available keys without having to change >> the file >> > in any way. >> > >> > So I don't think his "ruling out" of genericode really affects people >> > considering solutions that need the flexibility not offered by W3C >> > Schema. >> > >> > In fact, I think that since the article is *about* extending lists in >> > W3C Schema (based on the title) it makes sense that he cannot >> talk about >> > genericode. His observation about genericode that reads "Adding new >> > technology requirements can be too costly or time-consuming in some >> > settings." is, I think too subjective ... if a user's problem >> is solved >> > by genericode and not by W3C Schema then either they change their >> > requirements or they accept that they need as much software as >> is needed >> > to solve their problem. There will be many implementations of >> > genericode and context/value association ... in many contexts such as >> > document data entry or document validation. >> > >> > But did you notice the last bullet of the conclusion? >> > >> > "If you want to keep enumerated values out of the parser, consider >> > the Genericode approach" >> > >> > Sounds to me like he is affirming genericode's existence and role when >> > users are prepared to do without W3C schema enumerations to get the >> > advantages of genericode and context/value association. >> > >> > . . . . . . . . . . Ken >> > >> > -- >> > Upcoming XSLT/XSL-FO hands-on courses: Wellington, NZ 2009-01 >> > Training tools: Comprehensive interactive XSLT/XPath 1.0/2.0 video >> > G. Ken Holman mailto:gkholman@CraneSoftwrights.com >> > Crane Softwrights Ltd. http://www.CraneSoftwrights.com/o/ >> > Male Cancer Awareness Nov'07 http://www.CraneSoftwrights.com/o/bc >> > Legal business disclaimers: http://www.CraneSoftwrights.com/legal >> > >> > >> > --------------------------------------------------------------------- >> > To unsubscribe from this mail list, you must leave the OASIS TC that >> > generates this mail. Follow this link to all your TCs in OASIS at: >> > https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php >> >> -- >> Anthony B. Coates >> Associate Director >> Document Engineering Services (Limited) >> UK: +44 (20) 8816 7700, US: +1 (239) 344 7700 >> Mobile/Cell: +44 (79) 0543 9026 >> Skype: abcoates >> anthony.coates@documentengineeringservices.com >> http://www.documentengineeringservices.com/ >> >> --------------------------------------------------------------------- >> To unsubscribe from this mail list, you must leave the OASIS TC that >> generates this mail. Follow this link to all your TCs in OASIS at: >> https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php >> > -- Anthony B. Coates Associate Director Document Engineering Services (Limited) UK: +44 (20) 8816 7700, US: +1 (239) 344 7700 Mobile/Cell: +44 (79) 0543 9026 Skype: abcoates anthony.coates@documentengineeringservices.com http://www.documentengineeringservices.com/
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]