W3C home > Mailing lists > Public > public-grddl-wg@w3.org > September 2006

GRDDL links in HTTP? (new issue?)

From: Dan Connolly <connolly@w3.org>
Date: Mon, 11 Sep 2006 11:58:39 -0500
Message-Id: <36ca4468a51390b06b1e012d3c97cdeb@w3.org>
To: public-grddl-wg <public-grddl-wg@w3.org>

As Chime observed, GRDDL links are sorta like
the <?xml-stylesheet?> mechanism. And that mechanism
is sorta like the <?access-control?> mechanism in the VoiceXML
spec. I just saw...

"Here is a proposal for an Access Control HTTP header. The
idea is that it does everything the XML PI can, but without
needing to modify the source content."

http://lists.w3.org/Archives/Public/public-appformats/2006Aug/0157.html

That reminded me: in theory, at least, you can express typed links
(i.e. RDF triples) in HTTP headers. So a GRDDL client could
look there, as well as in the text of the document. This might help
with the "but lots of microformat documents don't have profiles" 
tension,
and maybe even the tensions around non-well-formedness; an
HTTP header could say "I authorize you to run tidy on this content,
and I agree to the results."

I'm moderately inclined to add support for this in my code,
and thereby work out the details.
Maybe it should end up in the GRDDL standard, maybe it shouldn't.
If somebody else thinks it's important for the WG to decide one
way or another, please say so, and I'll add it to the WG issues list.

-- 
Dan Connolly, W3C http://www.w3.org/People/Connolly/
Received on Monday, 11 September 2006 16:58:29 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 8 January 2008 14:11:45 GMT