W3C home > Mailing lists > Public > semantic-web@w3.org > August 2008

fragment-ID granularity

From: carmen r <_@whats-your.name>
Date: Thu, 14 Aug 2008 21:38:22 -0400
To: semantic-web@w3c.org
Message-ID: <20080815013822.GA6552@m.hsd1.ma.comcast.net>

perhaps ESW or similar site should have a Wiki page compiling approaches to fragment-identifier granularity and flexibility

i am aware of Hyperdata, or whatever the guy who inented the mouse in 1968's project is called/ hofstader maybe? englebart.. yeah\\

eg in a URI, one can guess that ^http:// means you could try fetching the data over HTTP

particularly interested in ways one could denote that the fragment identifier is actually a CSS selector, XPATH expression, etc

or maybe even another HTTP URI

eg in scenarios when multiple resources are displayed on a page, which can also be retrieved individually


this dovetails with granularity of requests. (eg requesting a particular fragment of a large doc, to fill in some empty cell in a GUI without wasting a ton of bandwidth)

sending the fragment ID in a GET tends to cause most HTTP parsers (that ive tried) to balk/fa


side note, is it possible for the list systems used by w3 to support read-only subscriptions, eg for AWWSW?
Received on Friday, 15 August 2008 01:39:06 GMT

This archive was generated by hypermail 2.3.1 : Tuesday, 26 March 2013 21:45:24 GMT