ISSUE-38: The RDFa API should elaborate on how it can operate in non-browser environments
non-browser generalization of rdfa api
The RDFa API should elaborate on how it can operate in non-browser environments
- State:
- POSTPONED
- Product:
- RDFa 1.1 API
- Raised by:
- Manu Sporny
- Opened on:
- 2010-08-01
- Description:
- The goal of the RDFa API is two-fold:
1. To provide a simple in-browser mechanism to extract data from a Web Document as RDF.
2. To provide a simple non-browser mechanism to extract data from a Web Document as RDF.
http://lists.w3.org/Archives/Public/public-rdfa-wg/2010Jun/0065.html
We should clarify how the RDFa API can be implemented in both a browser-based development environment as well as non-browser-based development environments. - Related Actions Items:
- No related actions
- Related emails:
- Comments on RDFa Core 1.1 Working Draft (from david@3roundstones.com on 2012-01-11)
- RDFa API new Issues - summary (from nathan@webr3.org on 2010-10-28)
- ISSUE-38 (non-browser generalization of rdfa api): The RDFa API should elaborate on how it can operate in non-browser environments [RDFa 1.1 Core] (from sysbot+tracker@w3.org on 2010-08-01)
Related notes:
We should just follow Nathan's advice - he's done a good job of showing us what needs to change to resolve this issue:
http://lists.w3.org/Archives/Public/public-rdfa-wg/2010Jun/0068.html
Display change log
