Arto,

Could not find a way to contact you otherwise, so I figured it best to file a ticket.

I'm the maintainer of the Calais module and in a nutshell, the Calais web service returns RDF. We are currently parsing the RDF directly with the ARC2 class, getting the simple index, and processing that way looking for certain guids, etc.

I was wondering how your RDF modules would be best used in that process. Could the RDF be retrieved from Calais, imported into your RDF data store then queried as needed for nodes? In what other ways would it be useful to leverage what is in this RDF API module? Sorry for such an open ended question, but after reading the docs, etc I am just left wondering what could be the best way to take advantage of existing modules built around some of the same technologies I'm using.

Thanks for any insight, feel free to ping me offline if you want.

Comments

febbraro’s picture

febbraro commented

Any update or thoughts on this?

I'm looking for a way to store the RDF returned from Calais so that as I develop new functionality I can re-query old processed data to take advantage of data I am currently passing by, but would like to take advantage of in the future.

Feel free to PM me or respond here. Thanks for any thoughts on this.

Arto’s picture

Arto commented
Title: How best to use the RDF Module? » Using RDF API in the Calais project
Version: 6.x-1.0-alpha3 » 6.x-1.x-dev
Assigned: Unassigned » Arto

Frank, my apologies for the radio silence on this. I'm about to roll a new RDF API release in the next few days, and I will get back to you right after that.

Arto’s picture

Arto commented
Component: Documentation » Calais integration
febbraro’s picture

febbraro commented

Thanks. I look forward to hearing from you. Good luck on the release.

febbraro’s picture

febbraro commented
Status: Active » Closed (fixed)

Figured this out, now storing RDF data locally. However I did run into #348758: Support both URI and IRI values from ARC2 in rdf_unserialize() that needs to be resolved.