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


Help: OASIS Mailing Lists Help | MarkMail Help



   Re: [xml-dev] Why you should avoid Notation Declarations (by

[ Lists Home | Date Index | Thread Index ]

At 2005-02-23 14:51 +0000, Henry S. Thompson wrote:
>Sorry not to be clearer -- in both this and your next message, the
>things you're expressing surprise/concern about are attempts to
>understand my messages as if they were about NOTATIONs and their
>declaration and use in XML 1.0/1.1 DTDs and DTD-based validation of
>But my message was about the simple type definition of the same name
>in W3C XML Schema, which reconstructs but does _not_ interact with the
>DTD-declared attribute type.

My apologies, Henry, thanks for this clarification.

So, I now see when using NOTATION declarations in W3C Schema, part 1 
section 3.12.1 makes reference to a target namespace.

But W3C Schema part 2 section 3.2.19 states that notation represents the 
notation attribute type from XML 1.0 ... and XML section 3.3.1 production 
[58] makes reference to only a simple Name, not a QName.  Wait, that's 
because XML 1.0 doesn't do namespaces.  Okay, so looking at Namespaces 1.1, 
section 7 says that notation names cannot contain any colons.

So, I have an XML document:

<!DOCTYPE doc [
<!ELEMENT doc ( thing+ )>
<!ELEMENT thing ( #PCDATA )>
<!ATTLIST thing n NOTATION ( abc | def ) #REQUIRED>
<!NOTATION abc SYSTEM "abc-stuff">
<!NOTATION def SYSTEM "def-stuff">
   <thing n="abc">abc here</thing>
   <thing n="def">def here</thing>

When abandoning the DTD and writing a W3C Schema expression for this 
instance, I gather from your comment that the notation names are QNames, 
just like the element names are QNames. But while interpreting the elements 
as QNames is consistent with the XML Information set section 2.2, section 
2.3 Attribute Information Items makes reference to attributes of type 
NOTATION as naming the NOTATION information item, which doesn't have a 
namespace component.

So, I wasn't expecting W3C Schema to change the game for components of XML 
in this fashion, because W3C Schema Part 1, section 1.2 states it depends 
on the XML Infoset.  Though I do note that Annex D does not require support 
for notation information items.

Are many other XML Information Set items changed by W3C Schema 
treatment?  I'm not including in my question the information in the PSVI 
that supplements the XML information set, just what more in the XML 
information set is being treated differently.

I apologize for my confusion ... thank you again for your guidance.

....................... Ken

World-wide on-site corporate, govt. & user group XML/XSL training.
G. Ken Holman                 mailto:gkholman@CraneSoftwrights.com
Crane Softwrights Ltd.          http://www.CraneSoftwrights.com/x/
Box 266, Kars, Ontario CANADA K0A-2E0    +1(613)489-0999 (F:-0995)
Male Breast Cancer Awareness  http://www.CraneSoftwrights.com/x/bc
Legal business disclaimers:  http://www.CraneSoftwrights.com/legal


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

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