- From: Shane McCarron <shane@aptest.com>
- Date: Thu, 07 Oct 2010 08:55:57 -0500
- To: Tim Berners-Lee <timbl@w3.org>
- CC: nathan@webr3.org, Ivan Herman <ivan@w3.org>, RDFA Working Group <public-rdfa-wg@w3.org>
Sure, but you didn't answer the key question here, Tim. WHERE should that RDF API work happen? We think it should happen in the RDFa Working Group because 1) there is one, and 2) we have already done lots of the work. What do you think? On 10/7/2010 8:51 AM, Tim Berners-Lee wrote: > Good Question. > > I think that there are some parts of the spec which are very RDFa-sepcific which could be > defined now, if there was a rough draft of the basic RDF service. > But the definition of the RDF API should happen in parallel. > > Tim > > > On 2010-10 -05, at 17:50, Nathan wrote: > >> Hi Tim, one clarification asked below: >> >> Tim Berners-Lee wrote: >>> On 2010-10 -05, at 11:27, Ivan Herman wrote: >>>> With my RDFLib background: of course. But I really wonder whether we are not going beyond the RDFa API level here. That was what I said in my previous mail... >>> The (complicated RDF meets DOM) RDFa API should be designed as an extension to the (simple clean RDF model only) RDF API. >>> If the RDFa is designed first, then the design will be terrible as you can't design the extension before that extended. >>> Because any RDFa script will want to have the basic RDF API. >> Can you clarify if you mean that the generic RDF part of the RDFa API should be designed first, then RDFa DOM specific functionality added as an extension. (all within the RDFa WG and carrying on as planned) >> >> -OR- >> >> The RDFa API and WG should wait for another group to standardize an RDF API, then extend that? >> >> Thanks, >> >> Nathan >> > -- Shane P. McCarron Phone: +1 763 786-8160 x120 Managing Director Fax: +1 763 786-8180 ApTest Minnesota Inet: shane@aptest.com
Received on Thursday, 7 October 2010 13:56:28 UTC