From: "Mike Schinkel" <[EMAIL PROTECTED]>
http://listserver.dreamhost.com/pipermail/whatwg-whatwg.org/2006-December/00
8462.html
I wonder if his issues can be addressed?
How about a distributed parser-discovery service
More specifically a YADIS discovered JSON returning uf-specific parser:
1. Place an entry on the uf-authored page detailing the ufs-used
<meta name="ufs-used" content="hreveiew hatom hwidget" />
2. Place a yadiservices discovery pointer to where parser(s)
maybe found, (on the same uf-authored page)
<meta name="ufs-used" content="hreveiew hatom hwidget" />
<meta http-equiv="X-YADIS-Location"
content="http://www.blahblah.com/path/to/yadis-file"; />
3. add parser service data to the (existing) yadis file pointed to within
the uf-authored page.
<?xml version="1.0" encoding="UTF-8"?>
<xrds:XRDS xmlns:xrds="xri://$xrds" xmlns="xri://$xrd*($v*2.0)"><XRD>
<Service>
<Type>http://openid.net/signon/1.0</Type>
<URI>http://www.livejournal.com/openid/server.bml</URI>
</Service>
<Service>
<Type>http://microformats.org/hreview/1.0</Type>
<URI>http://www.blah.com/path/to/uf2json-parser</URI>
</Service>
<Service>
<Type>http://mysite.com/hwidget/1.0</Type>
<URI>http://www.mysite.com/path/to/uf2json-parser</URI>
</Service>
</XRD></xrds:XRDS>
4. ..domain../path/to/uf2json-parser is a REST-call that is passed
a 'uf-snippet' and returns a JSON object.
Browsers that are uf-aware would call the parser with the uf-snippet,
and than hand of the JSON to the storing module.
CONS: The parser needs to be 'hosted', incurring bandwidth costs.
PROS: Roll your own microformat and parser - or - *leave your html
as is and just build a parser for it and point tothe parser from within the
page.*
S. Sriram
_______________________________________________
microformats-discuss mailing list
microformats-discuss@microformats.org
http://microformats.org/mailman/listinfo/microformats-discuss
