XML.orgXML.org
FOCUS AREAS |XML-DEV |XML.org DAILY NEWSLINK |REGISTRY |RESOURCES |ABOUT
OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index]
Re: [xml-dev] RELAX NG require oneOrMore optional elements

On July 15, 2008 12:39:55 PM -0700 Frank Cusack <fcusack@redhat.com> wrote:
> Is it possible to require one or more from a list of optional elements?

What if I did this with attributes instead of elements?  (I wouldn't
change to attributes just to get the behavior I want; I am considering
using attributes anyway.)  Since attributes cannot be repeated anyway,
I'm thinking that the

  <oneOrMore>
    <choice>
      <attribute ... />
      <attribute ... />
      ...
    </choice>
  </oneOrMore>

pattern will do what I want.  With elements, the problem was that the
pattern itself doesn't prevent repetition of any given element.  Here
I'm taking advantage of the built-in restriction on non-duplication
of attributes to get my desired restriction.

I'm testing this now, but would like to know, *should* I expect this
to work?

-frank


[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index]


News | XML in Industry | Calendar | XML Registry
Marketplace | Resources | MyXML.org | Sponsors | Privacy Statement

Copyright 1993-2007 XML.org. This site is hosted by OASIS