Well didn't really thougt about it thoroughly but :
On this page
http://www.mail-archive.com/whatwg@list ... 14468.html a few of the use-case requirements say :
The information should be convertible into a dedicated form (RDF, JSON, XML, BibTex) in a consistent manner, so that tools that use this information separate from the pages on which it is found have a standard way of conveying the information.
I can imagine apps storing the JSON serializations of html pages directly into a database for searching, for example couchDB.
Which could lead to the following scenario :
* Mei-Li, from China, is an international exchange student and searches the Amsterdam university (VU) history domain database for Chinese language fragments (maybe to review the quality of translations in the domain) in stored documents
* Lizzy is an Art student and wants to use some Chinese names in here work, she browses the web and clicks a browserbutton with the following function :
- Code: Select all
discoverMicrodata({"lang" : ['zh-CN'],"property" : ['http://xmlns.com/foaf/spec/index.rdf#name']}
It would be nice if such a function can make use of the standard JSON serialization
This is all kind of new to me (the whole point of my project) so bear with me if it doesn't make any sense.