RE: What an XML processor must/may not tell a processor

Intrigued by your message subject but uninformed by your 
message content, I'm wondering if you found anything that 
an XML processor *may not* tell a processor.

paul

> -----Original Message-----
> From: public-xml-processing-model-wg-request@w3.org
[mailto:public-xml-
> processing-model-wg-request@w3.org] On Behalf Of Henry S. Thompson
> Sent: Tuesday, 2010 July 13 9:49
> To: public-xml-core-wg@w3.org; public-xml-processing-model-wg@w3.org
> Subject: What an XML processor must/may not tell a processor
> 
> I've just searched the XML spec. for what it says about information
> passed to processors.  Here's a tabulation of my findings --
> comments/corrections welcome:
> 
> Required for all processors
> 
>  PIs
>  Non-markup character data
>  Attribute+default if declared and missing
>  Name and external idents of notations in attr val, attr def or entity
>   decl
> 
>  [implicitly, attribute values, since we have the prose "Before the
>   value of an attribute is passed to the application"]
> 
>  [implicitly, attributes, since we have their values]
> 
> Required for validating processors
> 
>  EC-Whitespace status
>  Unparsed entity SYS/PUB Idents and Notation
> 
> Required for non-validating
> 
>  Unread-entity notification
> 
> Optional
> 
>  Content of comments
>  [implicitly, comments as such ??]
> 
> Unclear
> 
>  Start and end tags
>  Declarations and definitions
> 
> I believe that it's been remarked before that start/end tags are not
> explicitly required to be reported, but everybody acts as if they are.
> In any case, I'd be very interested to hear arguments either way wrt
> these last two. . .

Received on Tuesday, 13 July 2010 14:57:23 UTC