Re: OODBMS <-> RDF

Pedro,

There is work going on in the OMG community that may be of interest and 
potentially useful.  The Ontology Definition Metamodel (ODM)[1] is close 
to finalization - there may be minor tweaks coming over the next couple 
of months, but it's been relatively stable for over a year, especially 
with regard to the metamodels it contains (RDF, OWL, Topic Maps, and 
Common Logic).  In parallel, there is a relatively new activity to 
revise the Common Warehouse Metamodel (CWM)[2], called the Information 
Management Metamodel (IMM)[3], which contains a metamodel for OODBMS.  
The OODBMS metamodel is relatively stable, and the CWM version may be 
sufficient for what you need as a starting point.

There is technology available today for metamodel transformations, 
called MOF (Meta-Object Facility) Query View Transformations, or QVT[4], 
to automate the process of metamodel to metamodel and related model to 
model transformations. There have been a few open source efforts to 
leverage this, and some folks have experimented with mappings for the 
ODM metamodels for RDF and OWL (although I have yet to see a "perfect", 
or even "really good" implementation).  See CIMTool [5] and ATL [6] 
among others, as well as projects on IBM's Alphaworks site under [7].  
ATL may provide a starting point that you could modify to suit your 
needs, though.

Having said this, we work with a partner company called Adaptive [8] who 
have commercial QVT-based capabilities for metamodel to metamodel and 
model to model transformation, including supporting infrastructure, a 
query-able repository, etc.  We've been working off and on with Adaptive 
to investigate some of the transformation capabilities, but haven't 
looked at the OODBMS case to date.  I've copied Pete Rivett on this to 
provide his email address in case you would like to follow up with 
either one or both of us off list.

I hope this turns out to be helpful.

Best regards,

Elisa

[1] http://www.omg.org/docs/ptc/07-09-09.pdf
[2] http://www.omg.org/technology/cwm/
[3] http://www.omg.org/cgi-bin/doc?ab/05-12-02  (IMM RFP)
[4] http://www.omg.org/cgi-bin/doc?ptc/2007-07-07
[5] http://cimtool.org/
[6] http://www.eclipse.org/m2m/atl/ and 
http://www.eclipse.org/m2m/atl/usecases/ODMImplementation/
[7] 
http://www.alphaworks.ibm.com/topics/semantics?open&S_TACT=106AH21W&S_CMP=AWLP 
and 
http://www.alphaworks.ibm.com/tech/semanticstk?open&S_TACT=106AH21W&S_CMP=AWLP
[8] http://www.adaptive.com/


Jesse Erdmann wrote:

>The only other D2R like software I'm aware of is Squirrel RDF,
>http://jena.sourceforge.net/SquirrelRDF/.  I don't know of any support
>of ZODB.  Is something like RDF Alchemy,
>http://www.openvest.com/trac/wiki/RDFAlchemy, or Oort,
>http://oort.to/, similar to what you're looking for?
>
>2008/1/25 José Pedro Ferreira <jose.pedro.ferreira@cern.ch>:
>  
>
>>Hello.
>>Yes, I know that RDF can be seen as object-oriented. But... I'm not
>>considering if it is possible to display OO data using RDF, but rather
>>how to make this translation in a smooth, fairly automatic way, without
>>having to write enormous amounts of replicated code, and taking
>>advantages of the similarities that exist between the two models. It's a
>>matter of "translation techniques".
>>
>>Cheers,
>>
>>Pedro
>>
>>cdr escreveu:
>>
>>    
>>
>>>On Fri Jan 25, 2008 at 02:34:28PM +0100, Jos? Pedro Ferreira wrote:
>>>
>>>      
>>>
>>>>Hello.
>>>>I need to make data stored in an object-oriented (ZODB) database available
>>>>as RDF. I've been looking for existing architectures and mapping
>>>>techniques, and eventually found D2RQ
>>>><http://www4.wiwiss.fu-berlin.de/bizer/D2RQ/spec/>. The problem is that
>>>>D2RQ seems too much oriented towards the relational paradigm.
>>>>Is there any research done on this particular area? I've been thinking
>>>>about something similar to D2RQ, but object-oriented. However, I'd like to
>>>>know if there's any work already done about this subject.
>>>>
>>>>        
>>>>
>>>your OOobject is your RDFsubject, your OOobject property is your RDFpredicate, and your OOobject property's value(s) is/are your RDFobject(s) (mind the nameclash)
>>>
>>>your OOobject have URI fields, of course.
>>>
>>>this also works with JSON.. which can be thought of as an OOobject serialization, and compatible with RDF so long as your property-symbols are URIs and each JSONobject has a URI property
>>>
>>>
>>>theyre pretty much identical. even RDFs with its subclassing and subtyping is an OO model.. replace 'object' with 'resource' in the literature
>>>
>>>
>>>
>>>      
>>>
>>>>Thanks in advance,
>>>>
>>>>Pedro
>>>>
>>>>        
>>>>
>>>      
>>>
>>>>begin:vcard
>>>>fn:Jose Pedro Ferreira
>>>>n:Ferreira;Jose Pedro
>>>>org:CERN;IT-UDS-AVC
>>>>adr:;;;Geneva;;;Switzerland
>>>>email;internet:jose.pedro.ferreira@cern.ch
>>>>title:Software Developer
>>>>tel;work:+41 22 76 75025
>>>>tel;cell:+41 763 045 795
>>>>x-mozilla-html:FALSE
>>>>url:http://www.zarquon.biz
>>>>version:2.1
>>>>end:vcard
>>>>
>>>>
>>>>        
>>>>
>>>
>>>      
>>>
>>    
>>
>
>
>
>  
>