[XML-DEV Mailing List Archive Home] [By Thread] [By Date] [Recent Entries] [Reply To This Message]

Re: RelaxNG problem about section 7.4. Restrictions on interle

• To: James Clark <jjc@j...>
• Subject: Re: RelaxNG problem about section 7.4. Restrictions on interleave
• From: Daniel Veillard <veillard@r...>
• Date: Mon, 17 Feb 2003 14:28:38 -0500
• Cc: xml-dev@l...
• In-reply-to: <498736294.1045533363@[192.168.0.10]>; from jjc@j... on Tue, Feb 18, 2003 at 01:56:03AM +0700
• References: <20030217080054.X29764@r...> <498736294.1045533363@[192.168.0.10]>
• Reply-to: veillard@r...
• User-agent: Mutt/1.2.5.1i

On Tue, Feb 18, 2003 at 01:56:03AM +0700, James Clark wrote:
> That's correct, because it's equivalent (per 4.12) to
> 
> <element xmlns="http://relaxng.org/ns/structure/1.0" name="foo">
>   <mixed>
>     <group>
>       <element name="bar">
>         <empty/>
>       </element>
>       <element name="bar">
>         <empty/>
>       </element>
>       <element name="bar">
>         <empty/>
>       </element>
>     </group>
>   </mixed>
> </element>

  Okay, thanks I missed the fact that auto-grouping applied to <mixed>,
that was easy to fix :-)

  While I have your focus, I feel a bit annoyed by letting the validator
accept values broken by PIs or comments in the serialization pass through
the WXS datatype checker.
  Do people really expect 
     "12<!-- comment -->e-12"
to validate as an xs:float in practice ? I have mixed feeling about
letting this go through unnoticed.
In theory the RelaxNG data model simply wipes out the comments and PIs ...
Well more precisely there is nothing said about them in the data model
section 2 so I assume ignoring them is the expected behaviour.

    thanks,

Daniel

-- 
Daniel Veillard      | Red Hat Network https://rhn.redhat.com/
veillard@r...  | libxml GNOME XML XSLT toolkit  http://xmlsoft.org/
http://veillard.com/ | Rpmfind RPM search engine http://rpmfind.net/

• Follow-Ups:
  • Re: RelaxNG problem about section 7.4. Restrictions on interleave
    • From: Jirka Kosek <jirka@k...>

• References:
  • RelaxNG problem about section 7.4. Restrictions on interleave
    • From: Daniel Veillard <veillard@r...>
  • Re: RelaxNG problem about section 7.4. Restrictions oninterleave
    • From: James Clark <jjc@j...>

• Prev by Date: Re: Safari and XSLT
• Next by Date: Re: Anyone wanna speculate about what this means?
• Previous by thread: Re: RelaxNG problem about section 7.4. Restrictions oninterleave
• Next by thread: Re: RelaxNG problem about section 7.4. Restrictions on interleave
• Index(es):
  • Date
  • Thread