Issue kay-1 (editorial, agreed)

Wants summary of changes added
Origin: Michael Kay <mike@saxonica.com>: origin
Discussions: WG agrees that we do need some appendix or other writeup explaining what has changed, but we can wait for this. The editors can write this at some point. reference
WG Response: accepted

Added appendix as requested. OP happy

Issue kay-2 (editorial, agreed)

Wants advice on how users can best get interoperable behaviours added wrt e.g. type="text/xsl"
Origin: Michael Kay <mike@saxonica.com>: origin
Discussions: WG agreed to add a Note pointing out that our reference to 2616 does not disallow type="text/xsl". 2616 just defines the general syntax and then says "Use of non-registered media types is discouraged" which is like a "should not". We do not intend for there to be anything in this spec. to disallow type="text/xsl". reference
WG Response: accepted

Added note. OP happy

Issue kay-3 (substantive, agreed)

Charset is (?) ignored if the stylesheet is an XML doc
Origin: Michael Kay <mike@saxonica.com>: origin
Discussions: WG agreed to clarify that the charset pseudo-attribute is really just a hint and may be ignored (e.g., if the stylesheet is an XML document). See also reference reference
WG Response: accepted

Added additional para. OP happy

Issue kay-4 (substantive, agreed)

Suggests adding ref. to XSLT spec(s?)
Origin: Michael Kay <mike@saxonica.com>: origin
Discussions: WG agreed to add a note and a non-normative reference. The relevant section is reference reference
WG Response: accepted

Added additional para. OP happy

Issue kay-5 (process, agreed)

Thinks this does not qualify as a new edition
Origin: Michael Kay <mike@saxonica.com>: origin
Discussions: WG agreed that the staff contact would provide a rationale
WG Response: accepted

SoTD and Appendix B address this point. OP happy

Issue holman-1 (substantive, agreed)

Needs clarification of the relation of HTML 'link' header elts to stylesheet PIs
Origin: G. Ken Holman <gkholman@CraneSoftwrights.com> : origin
Discussions: WG agreed to adopt the proposed wording at reference. Subsequent discussion suggested modifying this more in the direction of user intention reference reference
WG Response: accepted

New material added. OP happy

Issue holman-2 (substantive, agreed)

What is significance of the ordering of links?
Origin: G. Ken Holman <gkholman@CraneSoftwrights.com> : origin
Discussions: Same as reference, q.v.
WG Response: accepted

New material added. OP happy

Issue taylor-1 (editorial, agreed)

4 low-level editorial points, [from paras 3, 5, 6 and 7]
Origin: Philip Taylor <pjt47@cam.ac.uk>: origin
Discussions: Agreed to correct these as suggested reference
WG Response: accepted

Corrections made. OP happy

Issue taylor-2 (substantive, agreed)

Get the quotes out of the PseudoAtt production [from para 2]
Origin: Philip Taylor <pjt47@cam.ac.uk>: origin
Discussions: Agreed to correct this as suggested reference
WG Response: accepted

Correction made. OP happy

Issue taylor-3 (substantive, agreed)

What is the parsing result in section 3? [from para 4]
Origin: Philip Taylor <pjt47@cam.ac.uk>: origin
Discussions: Agreed to correct this as suggested reference
WG Response: accepted

Correction made. OP happy

Issue taylor-4 (substantive, agreed)

Significance of link order, again [from para 8]
Origin: Philip Taylor <pjt47@cam.ac.uk>: origin
Discussions: WG agreed to adopt the wording suggested in reference reference
WG Response: accepted

Correction made. OP happy

Issue glazman-1 (substantive, agreed)

Should specify a default interpretation if 'media' is absent
Origin: Daniel Glazman <daniel@glazman.org>: origin
Discussions: WG declined, on the basis that interpretation is reserved to applications. reference OP pushed back, there was a further exchange. reference reference reference After further interaction, the WG added new language clarifying the nature and responsibilities of AssocSS *applications* reference
WG Response: accepted-in-part
OP remains unsatisified,OP now satisfied