- From: Manu Sporny <msporny@digitalbazaar.com>
- Date: Sat, 04 Sep 2010 14:34:38 -0400
- To: RDFa WG <public-rdfa-wg@w3.org>
I haven't thought this through very well, but was wondering if it would be advisable to have an ondata attribute for the <body> element? This would work very much like the onload attribute that is already on the <body> element. I can see a few implementers complaining that the RDFa processing of a document could take a long time (as in more than 100ms), especially if certain RDFa profiles take a while to retrieve or timeout. The worst case is that a bad implementation of the RDFa API would cause the document not to render because the RDFa profiles are being fetched/processed. Ideally, RDFa processing should happen asynchronously. However, if it happens asynchronously, how do we signal developer code that the RDFa/Microformats/Microdata has been extracted and is ready to be read. The only approach that I could think of (in the 10 minutes that I've been thinking about the problem) is to have an "ondata" attribute on the BODY element that is called whenever all data extraction has completed for the document and there is data available in document.data.store. Have we thought about this problem before? -- manu -- Manu Sporny (skype: msporny, twitter: manusporny) President/CEO - Digital Bazaar, Inc. blog: WebID - Universal Login for the Web http://blog.digitalbazaar.com/2010/08/07/webid/2/
Received on Saturday, 4 September 2010 18:35:08 UTC