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

Re: some AssocSS comments on the latest draft

From: Henry S. Thompson <ht@inf.ed.ac.uk>
Date: Wed, 10 Mar 2010 13:11:05 +0000
To: "Grosso, Paul" <pgrosso@ptc.com>
Cc: <public-xml-core-wg@w3.org>
Message-ID: <f5bpr3cgw46.fsf@calexico.inf.ed.ac.uk>
Hash: SHA1

Grosso, Paul writes:

> Simon writes

>> "Editorial note: HST	2010-02-24
>> Addresses holman-1
>> . . .
>> I don't see how this addresses his comment.

I've changed the draft in a way which I think encorporates something
very close to your suggestion.

>> > ACTION to Henry:  Delete the final sentence of the body
>> > (done) and craft Appendix B.


>> > ACTION to Henry:  Provide a rationale for making this
>> > a second edition.

Still pending, will be outside the draft.

>> "Editorial note: HST	2010-02-24
>> Addresses kay-3
>> The value is advisory in that it must be ignored if the referenced
>> stylesheet itself provides character encoding information, either
>> explicitly via an HTTP header, or implicitly via its media type, as in
>> the case of XML documents."
>> I think this should be made non-normative (e.g. s/must/will likely/ or
>> similar), since we agreed to not have processing requirements on
>> pseudo-attribute values.
> I think I tend to agree that we should avoid "must" terminology here.

Hmm.  We should discuss this -- I think the XML spec. itself requires
us to say MUST here.

>> "Editorial note: HST	2010-02-24
>> Addresses taylor-2
>> [Definition: The string matched by PseudoAttValue in the PseudoAtt
>> production €” after any CharRefs and PredefEntityRefs are replaced with
>> the
>> characters they represent and with the start and end quotes removed €”
>> constitutes the value of the corresponding pseudo-attribute.] Each
>> CharRef
>> in PseudoAttValue is replaced with the character it represents
>> according
>> to XML [XML]. Each PredefEntityRef in PseudoAttValue is replaced with
>> with
>> U+0026 (&) if it is "&amp;", U+003C (<) if it is "&lt;", U+003E (>) if
>> it
>> is "&gt;", U+0022 (") if it is "&quot;" and U+0027 (') if it is
>> "&apos;"."
>> The definition doesn't place any requirements, it just defines a term
>> (maybe we should make this clearer by saying "...after being modified
>> as
>> follows" instead of listing how it's modified). So the processing
>> hasn't
>> actually changed. We need to insert a sentence after the definition,
>> something like: "The first and the last character (i.e. the quotes) in
>> PseudoAttValue are removed."
> I'm not sure I agree that changing a definition doesn't change
> processing requirements, but I will leave such wording decisions
> up to the editors for now.

I've tried to take Simon's suggestion. . .

>> The references section has "(Non-normative.)" and "(non-normative)"; we
>> should probably change one of those.


- -- 
       Henry S. Thompson, School of Informatics, University of Edinburgh
                         Half-time member of W3C Team
      10 Crichton Street, Edinburgh EH8 9AB, SCOTLAND -- (44) 131 650-4440
                Fax: (44) 131 651-1426, e-mail: ht@inf.ed.ac.uk
                       URL: http://www.ltg.ed.ac.uk/~ht/
[mail really from me _always_ has this .sig -- mail without it is forged spam]
Version: GnuPG v1.2.6 (GNU/Linux)

Received on Wednesday, 10 March 2010 13:11:35 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:16:41 UTC