W3C home > Mailing lists > Public > public-rdfa-wg@w3.org > June 2011

Re: ISSUE-96 (document not ready): Define how each API should behave when the document isn't fully loaded [RDFa 1.1 API]

From: Nathan <nathan@webr3.org>
Date: Fri, 17 Jun 2011 22:04:57 +0100
Message-ID: <4DFBC179.8060302@webr3.org>
To: RDF Web Applications Working Group WG <public-rdfa-wg@w3.org>
Related, do we have any notes or issues on how the API should work when 
(possibly external) scripts edit the dom contents?

RDF Web Applications Working Group Issue Tracker wrote:
> ISSUE-96 (document not ready): Define how each API should behave when the document isn't fully loaded [RDFa 1.1 API]
> 
> http://www.w3.org/2010/02/rdfa/track/issues/96
> 
> Raised by: Manu Sporny
> On product: RDFa 1.1 API
> 
> Henri Sivonen writes:
> 
> http://lists.w3.org/Archives/Public/public-rdfa-wg/2011Jun/0026.html
> 
> It seems to me that http://www.w3.org/TR/2010/WD-rdfa-api-20100608/
> isn't explicit about how the API is supposed to work when the main
> document itself hasn't loaded fully and when external RDFa Profiles
> haven't been loaded yet.
> 
> Please define how the API should behave when the relevant resources
> haven't been fully loaded and how a JavaScript application can find out
> that all the relevant resources have been loaded.
> 
> 
> 
> 
> 
> 
Received on Friday, 17 June 2011 21:06:11 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Friday, 27 April 2012 04:55:17 GMT