Altova Mailing List Archives>Archive Index >xmlschema-dev Archive Home >Recent entries >Thread Prev - simple attribute question >Thread Next - RE: Pattern constraint on string content of complexType having attribute and choice RE: Pattern constraint on string content of complexType having attribute and choiceTo: Michael Kay <mhk@---.--.-->, 'Jeni Tennison' <jeni@------------.---> Date: 8/11/2004 1:24:00 PM Hi Michael, Thanks for the feedback. A complicating factor in our requirements is that (unlike your <note> tag [see your message below] which, when present, always comes as the second of a pair of tags), our tag for <location-specific_Comment> can appear *anywhere* in the character data. [Basically, we are marking up transcriptions of medieval manuscripts, where the manuscript content is character data, and editorial comments are treated as markup.] The content of our <target_Type> must, I think, be "mixed". JT suggested leaving the Pattern out of our Schema declarations, and enforcing our RegEx via a separate validation-step. I expect she is thinking this could be triggered by an <xs:appinfo> tag, or somehow by pipelining the Schema-validator with another program. Such a program would need to enforce the RegEx on character data within <target_Type> and ignore any <location-specific_Comment> tags. By our requirements, it is crucial that the character data beween the <target_Type> tags *must* be RegEx- valid. I'm unsure how we could implement pipelining in an automated way, except at the data-entry side. Our instance docs are intended to be "first-class objects" on the Web, and I see no way currently to invoke a proprietary second-step validator during the course of browser retrieval of an XML doc. Any suggestions -- from anyone -- would be most welcome. Cheers, - Wyatt --- Michael Kay <mhk@m...> wrote: > If you do a direct translation of GEDCOM into XML > you get a similar > requirement. GEDCOM uses elements that contain a > value followed by > qualifiers, for example > > <occupation>baker > <date>10 MAR 1566 > <note>unsure which calendar > <author>MHK</author> > <date>10 AUG 2004</date> > </note> > </date> > </occupation> > > The obvious answer of puttting the value in another > layer of markup: > > <occupation><value>baker</value> > <date><value>10 MAR 1566</value> > <note><value>unsure which calendar</value> > <author><value>MHK</value></author> > <date><value>10 AUG 2004</value></date> > </note> > </date> > </occupation> > > Michael Kay < From mhk@m... Thu Aug 12 09:55:15 2004 Received: from dr-nick.w3.org ([18.29.1.73]) by frin | ||||||
| Company | Legal | Press | Partners | Careers | Sitemap | Contact Us | Altova Blog | Mobile | Full Site | |||
|
