W3C home > Mailing lists > Public > public-html@w3.org > August 2008

RE: Pseudo-namespaces

From: Justin James <j_james@mindspring.com>
Date: Sun, 3 Aug 2008 00:07:15 -0400
To: "'Julian Reschke'" <julian.reschke@gmx.de>
Cc: "'Ian Hickson'" <ian@hixie.ch>, "'Sam Ruby'" <rubys@us.ibm.com>, "'HTML WG'" <public-html@w3.org>
Message-ID: <04f701c8f51e$6a461160$3ed23420$@com>

Julian -

What you describe below is exactly what I would expect and hope for, thank you! Since the actual class name as an URL is simply an author-level item, I suggest that we ignore the topic of "authority" over a URI, to keep us from having more questions like the ones I asked.

Thanks to all on this, I think that this is a good direction!


> -----Original Message-----
> From: public-html-request@w3.org [mailto:public-html-request@w3.org] On
> Behalf Of Julian Reschke
> Sent: Saturday, August 02, 2008 10:55 AM
> To: Justin James
> Cc: 'Ian Hickson'; 'Sam Ruby'; 'HTML WG'
> Subject: Re: Pseudo-namespaces
> Justin James wrote:
> >> Could you elaborate on that? Are you wondering whether a syntax like
> >> this could be used to automatically download associated scripts? (to
> >> which my answer would be: hopefully not :-)
> >
> > For example, if the page I am authoring is located at:
> > http://www.sitea.com/pages/page4.html
> >
> > and it contains a class name:
> > http://www.someothersite.com/price
> >
> > what happens? Should it be rejected? Let's make it even more
> interesting... let's say the style sheet I used came from:
> Nothing happens. It's just a name.
> > http://www.someothersite.com/css/style1.css
> >
> > Now, the class comes from the same pseudo-namespace (as I have
> decided to call this concept) as the stylesheet. Does that change the
> dynamics at all?
> >
> > Or to rephrase, should the browser be performing any kind of security
> checks/sandboxing/cross domain restrictions on the pseudo-namespace,
> even though it does not mean a hill of beans at the CSS level? Or
> should the browser treat all class names a "dumb values", even if it
> does not (as we hashed out in the last message) actually
> download/execute/etc. a pseudo-namespaced class?
> >
> > I think it should not enforce anything here, but we may want to.
> The name is an identifier only, just in an XML namespace.
> For instance, you can use the XHTML namespace without having authority
> over w3.org.
> BR, Julian
Received on Sunday, 3 August 2008 04:08:02 UTC

This archive was generated by hypermail 2.3.1 : Thursday, 29 October 2015 10:15:36 UTC