W3C home > Mailing lists > Public > public-xml-core-wg@w3.org > June 2009

Re: Assoc SS issue list

From: Simon Pieters <simonp@opera.com>
Date: Wed, 24 Jun 2009 03:23:42 +0200
To: "John Cowan" <cowan@ccil.org>
Cc: "Grosso, Paul" <pgrosso@ptc.com>, public-xml-core-wg@w3.org
Message-ID: <op.uvz8ts0aidj3kv@simon-pieterss-macbook.local>
On Wed, 24 Jun 2009 02:52:20 +0200, John Cowan <cowan@ccil.org> wrote:

> Simon Pieters scripsit:
>> >        href MUST be a LEIRI
>> LEIRI seems to allow whitespace. Why would we want to allow whitespace  
>> in
>> href? In HTML, that's considered an error.
> For compatibility with the other URI-like strings in XML (system  
> identifiers,
> XLinks, etc.)

I see more value in being consistent with HTML <link>.

>> >        charset MUST be a Name
>> Why a Name?
>> HTML5 says about <meta charset>:
>> "The value must be a valid character encoding name, and must be the
>> preferred name for that encoding. [IANACHARSET]"
> If you look at the IANA charset names, they are all XML Names in syntax.

It's not clear to me how it follows that it would be useful to check as  
Name rather than IANA encoding name.

> I'm only trying to constrain syntax here: we can't expect the  
> stylesheet-pi
> processor to know what the valid names are.

We can expect a validator to know that. http://validator.nu/ has such  
knowledge for HTML5.

>> I think handling of invalid values should be consistent with HTML <link
>> rel="stylesheet">:
>> href: resolve against document's URL according to Web addresses, using
>> utf-8 as the URL's encoding. If this returns an error, ignore the PI.
>> media: refer to Media Queries. If the query evaluates to false, ignore  
>> the
>> PI.
>> type: if it is a type the UA does not support, the UA may opt to not  
>> fetch
>> the resource.
>> charset: HTML5 does not have <link charset> at all. But if we keep it,  
>> and
>> the value is an encoding the UA does not support or is not an encoding
>> name, then ignore the pseudo-attribute.
> The stylesheet-pi processor doesn't know these things, so it can't do  
> full validity
> testing.

I'm not sure I follow.

Are you saying that what I described above is on the application level?

>  What I'm saying here is that the pseudo-atts should conform to certain
> syntax rules.

I think we should either have useful syntax rules, or not constrain the  
syntax at all. Having arbitrary syntax rules are not useful for anyone,  

Simon Pieters
Opera Software
Received on Wednesday, 24 June 2009 01:24:38 UTC

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