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

Re: First sketch of the new RDF-API

From: Ivan Herman <ivan@w3.org>
Date: Fri, 29 Apr 2011 18:55:13 +0200
Cc: benjamin.adrian@dfki.de, RDFa WG <public-rdfa-wg@w3.org>, Manu Sporny <msporny@digitalbazaar.com>
Message-Id: <78B18231-57C2-4B8A-9578-344029A6863F@w3.org>
To: nathan@webr3.org

On Apr 29, 2011, at 18:47 , Nathan wrote:

> Ivan Herman wrote:
>> On Apr 29, 2011, at 18:25 , Nathan wrote:
>>> yup, small note (well not small tbh).. the RDF Interfaces kind of needs the PrefixMap, TermMap, Profile and RDFEnvironment, else it's totally unusable and indeed isn't anything. Indeed I was quite surprised to even see them in this document, thought it was to be a developer focused read only API similar to the RDFa API, a layer of abstraction above?
>> Wait, it is not so bad... There is a _reference_ to the rdfenvironment, nothing else.
> 
> Hmm, I see it re-defined in the RDF API:
> http://www.w3.org/2010/02/rdfa/sources/rdf-api/Overview-src1.html#rdf-environment


Ah! Sorry, I missed that.

So the question is: would we allow for a level 2 interface like RDF API to use the same interface but with a restricted number of properties? It is obviously not the intention of removing the RDF environment from the RDF Interfaces, that is clear. Conceptually, we have a subset here. How would one go about defining this properly in the IDL/Javascript world?

Time to call it a day:-)

Cheers


Ivan

> 
>> The only interfaces that were 'lifted' into the rdf api were the term and prefix maps (and I indeed believe they are essential in the rdf interface level). Referring to the rdf environment to get to the mappings is probably fine.
> 
> Yup, although it possibly isn't needed since there is the setMapping method common to both the RDF API and the RDFa API, doesn't matter whether the implementation uses the RDFEnvironment, TermMap, PrefixMap, Profile or the like, that's all hidden behind the setMapping method and of no concern as it were.
> 
> Best,
> 
> Nathan
> 
>>> Ivan Herman wrote:
>>>> Brilliant.
>>>> Just a few things
>>>> - you still have a reference to the rdfa environment in Document Data. We should certainly not keep it under that type and name. On the other hand, afaik the only role of the rdfa environment was to have the query, I wonder whether not calling it rdfa might be better for both and use that accordingly
>>>> - should the rdf environment in the same interface still be optional? - I wonder whether it makes sense to elevate the term and prefix mapping interfaces into this level; these can be accessed via the rdf environment of the document data...
>>>> - What I miss is how to get to a parser. THe RDFa API did not need this because, well, we had the Document object; in here we would need some access to the parsers with maybe much less options than in the core RDF Interfaces, ie, a stripped down version of that stuff...
>>>> Great...
>>>> Ivan On Apr 29, 2011, at 17:35 , Benjamin Adrian wrote:
>>>>> Hi,
>>>>> 
>>>>> I just added first draft of a new RDF-API [1] which consists of copied
>>>>> passages from the old RDF API (now RDF Interfaces) and RDFa API.
>>>>> 
>>>>> At the moment the section 1.Introduction remained the same. I will
>>>>> re-edit it after a discussion about the content of Section 2. The RDF
>>>>> API Specification.
>>>>> 
>>>>> As this is just a first sketch of a draft, much more editing work
>>>>> remains to bring this Spec in good shape.
>>>>> This evening I am going to add notes to the RDFa-API / RDF-interfaces
>>>>> on each passage that I copied to this new spec.
>>>>> 
>>>>> Best regards and a wonderful weekend,
>>>>> 
>>>>> Ben
>>>>> 
>>>>> [1] http://www.w3.org/2010/02/rdfa/sources/rdf-api/Overview-src1.html
>>>>> 
>>>>> -- 
>>>>> __________________________________________
>>>>> Benjamin Adrian
>>>>> Email : benjamin.adrian@dfki.de
>>>>> WWW : http://www.dfki.uni-kl.de/~adrian/
>>>>> Tel.: +49631 20575 1450
>>>>> Twitter: http://twitter.com/BenBanBun
>>>>> Skype: benbanbun
>>>>> __________________________________________
>>>>> Deutsches Forschungszentrum für Künstliche Intelligenz GmbH
>>>>> Firmensitz: Trippstadter Straße 122, D-67663 Kaiserslautern
>>>>> Geschäftsführung:
>>>>> Prof. Dr. Dr. h.c. mult. Wolfgang Wahlster (Vorsitzender) Dr. Walter Olthoff
>>>>> Vorsitzender des Aufsichtsrats:
>>>>> Prof. Dr. h.c. Hans A. Aukes
>>>>> Amtsgericht Kaiserslautern, HRB 2313
>>>>> __________________________________________
>>>>> 
>>>> ----
>>>> Ivan Herman, W3C Semantic Web Activity Lead
>>>> Home: http://www.w3.org/People/Ivan/
>>>> mobile: +31-641044153
>>>> PGP Key: http://www.ivan-herman.net/pgpkey.html
>>>> FOAF: http://www.ivan-herman.net/foaf.rdf
>> ----
>> Ivan Herman, W3C Semantic Web Activity Lead
>> Home: http://www.w3.org/People/Ivan/
>> mobile: +31-641044153
>> PGP Key: http://www.ivan-herman.net/pgpkey.html
>> FOAF: http://www.ivan-herman.net/foaf.rdf
> 


----
Ivan Herman, W3C Semantic Web Activity Lead
Home: http://www.w3.org/People/Ivan/
mobile: +31-641044153
PGP Key: http://www.ivan-herman.net/pgpkey.html
FOAF: http://www.ivan-herman.net/foaf.rdf
Received on Friday, 29 April 2011 16:54:13 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:19:51 UTC