- From: Nathan <nathan@webr3.org>
- Date: Thu, 14 Apr 2011 12:05:05 +0100
- To: Manu Sporny <msporny@digitalbazaar.com>
- CC: RDFa WG <public-rdfa-wg@w3.org>
Manu Sporny wrote: > 3. Remaining issues for RDF API > http://www.w3.org/2010/02/rdfa/sources/rdf-api/ Of which there are still quite a few, for example: change PrefixMap.resolve return null if prefix not set remove import*FromGraph methods from TermMap, PrefixMap and Profile separation of concerns, these interface should not require a full set of RDF Interfaces just to be implemented. remove Profile.base ... maybe remove Parser.profile will often lead to unexpected results since each format can declare the same prefix/term and override the definition down the tree, what ends up in the profile? - which would be out of scope for us to define Profile.reduce must be: return tp.indexOf(":") >= 0 ? this.prefixes.resolve(tp) : this.terms.resolve(tp); try method on TripleAction change to 'run' or other try is a reserved word get rid of NCName description. define term as string w/ no colon or whitespace since it's an RDF API, not just RDFa perhaps change 'term' to 'alias'. (AliasMap) appears to make more sense, and term is used heavily through RDF and sparql to refer to other things. Ideally I was hoping to get these in to the API document before today's meeting, although I don't think I'll have a chance to finish it till later today. Cheers, Nathan
Received on Thursday, 14 April 2011 11:06:04 UTC