W3C home > Mailing lists > Public > public-xml-core-wg@w3.org > January 2010

AssocSS comments

From: Simon Pieters <simonp@opera.com>
Date: Wed, 27 Jan 2010 18:51:19 +0100
To: public-xml-core-wg@w3.org
Message-ID: <op.u67c7t0cidj3kv@simon-pieterss-macbook.local>
I'm pasting the comments from  
http://www.w3.org/XML/2010/01/disposition.html here for easier discussion.


Associating Style Sheets with XML documents 1.0 (Second Edition)  
Disposition of Comments
13 January 2010

Issue kay-1 (editorial, pending)
Wants summary of changes added
Origin: Michael Kay <mike@saxonica.com>:  
http://lists.w3.org/Archives/Public/www-xml-stylesheet-comments/2009Dec/0001.html
> 1. It would be nice to have a more detailed explanation of what has  
> changed.
Discussions:

Issue kay-2 (editorial, pending)
Wants advice on how users can best get interoperable behavious added
Origin: Michael Kay <mike@saxonica.com>:  
http://lists.w3.org/Archives/Public/www-xml-stylesheet-comments/2009Dec/0001.html
> 2. Since the specification is partially implemented in current browsers,  
> it
> would be useful to give users and implementors some advice on how to  
> achieve
> interoperable behavior taking the current legacy into account. For  
> example,
> it would be useful to note that the pseudo-attribute media="text/xsl"  
> works
> on many current browsers though disallowed by the spec, while the
> pseudo-attribute media="application/xml+xslt" is legal but poorly  
> supported
> by current products.
Discussions:

Issue kay-3 (substantive, pending)
Charset is (?) ignored if the stylesheet is an XML doc
Origin: Michael Kay <mike@saxonica.com>:  
http://lists.w3.org/Archives/Public/www-xml-stylesheet-comments/2009Dec/0001.html
> 3. It might be worth mentioning that the charset pseudo-attribute is  
> ignored
> if the stylesheet is an XML document.
Discussions:

Issue kay-4 (substantive, pending)
Suggests adding ref. to XSLT spec(s?)
Origin: Michael Kay <mike@saxonica.com>:  
http://lists.w3.org/Archives/Public/www-xml-stylesheet-comments/2009Dec/0001.html
> 4. It might be worth a reference to the XSLT specification which gives
> further information on the use of this processing instruction with XSLT
> stylesheets.
Discussions:

Issue kay-5 (process, pending)
Thinks this does not qualify as a new edition
Origin: Michael Kay <mike@saxonica.com>:  
http://lists.w3.org/Archives/Public/www-xml-stylesheet-comments/2009Dec/0001.html
> 5. So much of the text has been rewritten that calling this a second  
> edition
> rather than a point release would appear to many to be an abuse of  
> process.
Discussions:

Issue holman-1 (substantive, pending)
Needs clarification of the relation of HTML 'link' header elts to  
stylesheet PIs
Origin: G. Ken Holman <gkholman@CraneSoftwrights.com> :  
http://lists.w3.org/Archives/Public/www-xml-stylesheet-comments/2009Dec/0002.html
> (1) - the introduction associates HTML link instructions with PIs,but  
> the introduction is non normative ... is there any normativesection that  
> describes how a user agent is to interpret the PI valuesor is that out  
> of scope of this particular specification?  If theanswer is "the same  
> way as with HTML, then I believe there should bea normative statement  
> saying so.  If the answer is "the semanticsassociated with the  
> information expressed using this specificationare out of scope of the  
> specification", then explicitly stating thatwill prevent readers from  
> making guesses.
Discussions:

Issue holman-2 (substantive, pending)
What is significance of the ordering of links?
Origin: G. Ken Holman <gkholman@CraneSoftwrights.com> :  
http://lists.w3.org/Archives/Public/www-xml-stylesheet-comments/2009Dec/0002.html
> (2) - external links are said to occur before associations specifiedby  
> PIs ... but what is the interpretation of the order of the links?(or is  
> that covered off in the answer to the first question?)
Discussions: reference

Issue taylor-1 (editorial, pending)
4 low-level editorial points, [from paras 3, 5, 6 and 7]
Origin: Philip Taylor <pjt47@cam.ac.uk>:  
http://lists.w3.org/Archives/Public/www-xml-stylesheet-comments/2009Dec/0003.html
> "Each PredefEntityRef in PseudoAttValue is replaced with with ..."s/with  
> with/with/
>
> "If it's not reported to the application" - s/it's/it is/
>
> " [1] StyleSheetPI ::= "<?xml-stylesheet" (S PseudoAtts)? - (Char* "?>" 
> Char*) "?>" "
> Should be:
> " [1] StyleSheetPI ::= "<?xml-stylesheet" ((S PseudoAtts)? - (Char* "?>" 
> Char*)) "?>" "
> since the precedence of the XML EBNF '-' operator is undefined.
>
> "If specified, documents may use any string as the value." - seems like 
> abuse of RFC2119 terminology. "X may do Y" means X can optionally choose 
> to do Y or to not do Y, but it's impossible to choose not to use any 
> string as the value if you specify the value. Maybe s/may/can/ (there's 
> no need to use a conformance requirement keyword when you're not 
> requiring anything).
Discussions:

Issue taylor-2 (substantive, pending)
Get the quotes out of the PseudoAtt production [from para 2]
Origin: Philip Taylor <pjt47@cam.ac.uk>:  
http://lists.w3.org/Archives/Public/www-xml-stylesheet-comments/2009Dec/0003.html
> "The string matched by PseudoAttValue in the PseudoAtt production —after  
> any CharRefs and PredefEntityRefs are replaced with the charactersthey  
> represent — constitutes the value of the correspondingpseudo-attribute."  
> - the matched string includes the surrounding quotes;they ought to be  
> stripped off before determining the pseudo-attribute value.
Discussions:

Issue taylor-3 (substantive, pending)
What is the parsing result in section 3? [from para 4]
Origin: Philip Taylor <pjt47@cam.ac.uk>:  
http://lists.w3.org/Archives/Public/www-xml-stylesheet-comments/2009Dec/0003.html
> Section 3 doesn't says what the parsing result is, except in the cases 
> where it's an error. It should probably say something explicit like "If 
> the parsing result is not an error, then it is the set of 
> pseudo-attributes represented when the given string is matched by the 
> PseudoAtts production."
Discussions:

Issue taylor-4 (substantive, pending)
Significance of link order, again [from para 8]
Origin: Philip Taylor <pjt47@cam.ac.uk>:  
http://lists.w3.org/Archives/Public/www-xml-stylesheet-comments/2009Dec/0003.html
> "Any links to style sheets that are specified externally to the document 
> (e.g. Link headers in some versions of HTTP [RFC2068]) are considered to 
> occur before the associations specified by the xml-stylesheet processing 
> instructions." - what considers them, in what context? This isn't a 
> conformance requirement, and doesn't apply to the listed conformance 
> classes, and it doesn't look like an example or a note, and it doesn't 
> reference any spec that defines that behaviour, so I don't understandwhy  
> the sentence is in this spec. It should be removed, or rephrased tomake  
> its intentions clear.
Discussions: reference
Received on Wednesday, 27 January 2010 17:51:56 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Wednesday, 27 January 2010 17:51:56 GMT