OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help



   Re: Ambiguity in XML spec

[ Lists Home | Date Index | Thread Index ]
  • From: "Brown, Bryan" <bryanb@upshot.com>
  • To: "'xml-dev@xml.org'" <xml-dev@xml.org>
  • Date: Thu, 18 May 2000 12:09:10 -0700

>> So after reading 'PUBLIC' you have no idea if you are looking for "S 
>>S PubidLiteral S SystemLiteral " or just "S PubidLiteral" 
>>What am i missing ? 
> Nothing, but what's the problem? It's ambiguous (in the content model 
> sense of non-deterministic), but the productions in the spec are not 
> intended to correspond that directly to an implementation. 

Ok, well I have a parser that i wrote from scratch, and of the 83 or so
productions this is the only one my parser has a problem with. If when a
NotationDecl has a publicID the systemliteral is optional (which is what the
current spec implies) then the spec should have had productions like the
[83] NotationDecl ::= '<!NOTATION' S Name S (SystemID | PublicID )
[84] PublicID ::= 'PUBLIC' S PubicLiteral (S SystemLiteral)?
[85] SystemID ::= 'SYSTEM' S SystemLiteral	
[[83] NotationDecl ::= '<!NOTATION' S Name S (ExternalID | PublicID )
[84] PublicID ::= 'PUBLICID' S PubicLiteral
- Bryan

This is xml-dev, the mailing list for XML developers.
To unsubscribe, mailto:majordomo@xml.org&BODY=unsubscribe%20xml-dev
List archives are available at http://xml.org/archives/xml-dev/


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

Copyright 2001 XML.org. This site is hosted by OASIS