 |
 |
 |
<span style='font-size:
10.0pt;font-family:Arial;color:navy'>Compact syntax:<o:p></o:p>
<span style='font-size:
10.0pt;font-family:Arial;color:navy'><o:p> </o:p>
<span style='font-size:
10.0pt;font-family:Arial;color:navy'>start = anyElement<o:p></o:p>
<span style='font-size:
10.0pt;font-family:Arial;color:navy'>anyElement =<o:p></o:p>
<span style='font-size:
10.0pt;font-family:Arial;color:navy'> element * {<o:p></o:p>
<span style='font-size:
10.0pt;font-family:Arial;color:navy'> (attribute * { text }<o:p></o:p>
<span style='font-size:
10.0pt;font-family:Arial;color:navy'> | text<o:p></o:p>
<span style='font-size:
10.0pt;font-family:Arial;color:navy'> | anyElement)*<o:p></o:p>
<span style='font-size:
10.0pt;font-family:Arial;color:navy'> }<o:p></o:p>
<span style='font-size:
10.0pt;font-family:Arial;color:navy'><o:p> </o:p>
<span style='font-size:
10.0pt;font-family:Arial;color:navy'>This validates an element of any name with
an attribute of any name with content of same. I’m no RNG expert, but I’ve
tried this and one problem is that this definition conflicts with element
definitions already defined that have ID/IDREF’s (I get an error when
parsing with Jing). I don’t have time right now to give a complete
example, but I’m thinking (perhaps wrongly) that the above definition
will not restrict content for those elements already defined, so it’s
more like processContent=”skip” than “lax”.<o:p></o:p>
<span style='font-size:
10.0pt;font-family:Arial;color:navy'><o:p> </o:p>
<span style='font-size:10.0pt;
font-family:Tahoma;font-weight:bold'>From: Radu Cernuta
[mailto:radu.cernuta@g...]
Sent: Tuesday, February 06, 2007
3:50 AM
To: Jeff Lowery
Cc: xml-dev@l...
Subject: Re: [xml-dev] RELAX NG
equivalent of <xsd:any processContents="lax">?<o:p></o:p>
<span style='font-size:
12.0pt'><o:p> </o:p>
For lax validation in
RELAX NG you could take a look at the RELAX NG Tutorial by James Clark and
Murata Makoto. Section 11 (Name Classes) handles this issue.
http://relaxng.org/tutorial-20011203.html#IDAFLZR
Greetings,
Radu Cernuta
<o:p></o:p>
2007/2/6, Jeff Lowery <jlowery@m...>: <o:p></o:p>
This has got to be a FAQ,
but no luck with googling:
Trying to find a shorthand method to validate content using lax
constraints in RELAX NG. I want something like this:
#=================
namespace foo = "http://www.w3.org/foo"
qux =
element baz {empty} # some
element
bar =
element bar { anyLax* } #allow baz, bar,
anyOtherElement
anyOtherElement =
element * -
foo:* { # any
elements not in this namespace
attribute * { text }*,
(text
| anyOtherElement)*
}
anyLax = (
grammar
{*}
#all patterns
)*
#===========
Don't work, though.
Only examples I've seen enumerate all the grammars by name in the
schema. Doesn't appear there is wildcard of that type.
_______________________________________________________________________
XML-DEV is a publicly archived, unmoderated list hosted by OASIS
to support XML implementation and development. To minimize
spam in the archives, you must subscribe before posting.
[Un]Subscribe/change address: http://www.oasis-open.org/mlmanage/
Or unsubscribe: xml-dev-unsubscribe@l...
subscribe: xml-dev-subscribe@l...
List archive: http://lists.xml.org/archives/xml-dev/
List Guidelines: http://www.oasis-open.org/maillists/guidelines.php<o:p></o:p>
<span style='font-size:
12.0pt'>
_________________________________________________
Scanned on 06 Feb 2007 11:50:20<o:p></o:p>
|
 | 

|  |
These Archives are provided for informational purposes only and have been generated directly from the Altova mailing list archive system and are comprised of the lists set forth on www.altova.com/list/index.html. Therefore, Altova does not warrant or guarantee the accuracy, reliability, completeness, usefulness, non-infringement of intellectual property rights, or quality of any content on the Altova Mailing List Archive(s), regardless of who originates that content. You expressly understand and agree that you bear all risks associated with using or relying on that content. Altova will not be liable or responsible in any way for any content posted including, but not limited to, any errors or omissions in content, or for any losses or damage of any kind incurred as a result of the use of or reliance on any content. This disclaimer and limitation on liability is in addition to the disclaimers and limitations contained in the Website Terms of Use and elsewhere on the site.
|  |
| |
 |
 |
 |