What problem is this solving? What human readable content is this marking up?
This is sounding off-topic for microformats. Am I missing something? Thanks, Tantek On 5/25/06 8:46 AM, "Chris Messina" <[EMAIL PROTECTED]> wrote: > Ooo.. that would be cool... I might sound dumb by saying this, but > would that be like a RESTian way of accessing data in a microformatted > page? > > Chris > > On 5/25/06, Dimitri Glazkov <[EMAIL PROTECTED]> wrote: >> So, this is like W3 Selectors for URLs? >> >> :DG< >> >> On 5/25/06, Scott Reynen <[EMAIL PROTECTED]> wrote: >>> On May 25, 2006, at 3:04 AM, Chris Messina wrote: >>> >>>> how do we create URIs for partial bits of data like a word >>>> or hcard in the middle of a paragraph? >>>> >>>> http://www.eekim.com/blog/tech/hyperscope/hyperscopeuri.html >>> >>> I'm not sure that's really the question being asked by Eugene. It >>> sounds like the addressing of HyperScope goes beyond specific fragments: >>> >>> "It can do path expressions, similar in spirit to XPath, which allows >>> you to reference some subset of nodes in a document." >>> >>> This sounds to me like, e.g., a URI that references all the TEL >>> elements in a document, and only those elements, so the client can >>> read the URI, load the document, and strip it down to the specified >>> nodes. So the question being asked is whether this would be better >>> as http://domain.org/?hyperscope=class:tel or http://domain.org/ >>> #hyperscope:class-tel or something else. >>> >>> Peace, >>> Scott _______________________________________________ microformats-discuss mailing list [email protected] http://microformats.org/mailman/listinfo/microformats-discuss
