W3C home > Mailing lists > Public > whatwg@whatwg.org > September 2008

[whatwg] RDFa

From: Philipp Serafin <phil127@gmail.com>
Date: Tue, 9 Sep 2008 14:26:52 +0200
Message-ID: <f042876c0809090526q3e966857r99aa29cb19f21e2f@mail.gmail.com>
Please correct me if I'm wrong here, but it looks to me as if RDFa
uses namespaced identifiers nowhere outside attribute values right
now. So couldn't you just introduce a "rdf specific" namespacing
system for example like eRDF does[1]? This way, RDF parsers could
still look up metainformation about RDF properties while RDF-unaware
agents could parse the attribute values as simple text.

[1] http://research.talis.com/2005/erdf/wiki/Main/RdfInHtml#schemas

On Tue, Sep 9, 2008 at 10:58 AM, Ian Hickson <ian at hixie.ch> wrote:

> Both introducing a namespace prefix processing model and introducing DOM
> inconsistencies at the XML/HTML boundary intentionally are simply not an
> option in WHATWG specs at this point. Experience borne out of mechanisms
> that have had these characteristics [1] has shown these problems to be
> simply unacceptable for a Web authoring-level specification. This is
> feedback I have received from browser vendors and authors a lot.
>
> ([1] e.g. XML namespaces, which has the former characteristic when used in
> XHTML1 documents processed as XML and the latter characteristic when used
> in XHTML documents processed as HTML4.)
>
> --
> Ian Hickson               U+1047E                )\._.,--....,'``.    fL
> http://ln.hixie.ch/       U+263A                /,   _.. \   _\  ;`._ ,.
> Things that are impossible just take longer.   `._.-(,_..'--(,_..'`-.;.'
>
Received on Tuesday, 9 September 2008 05:26:52 UTC

This archive was generated by hypermail 2.4.0 : Wednesday, 22 January 2020 16:59:05 UTC