Re: Custom properties for no SPARQL LOD scenario

Hi Juan,

This is not a SKOS problem strictly speaking, but one of data publishing, and the assumption that all relevant information on a resource should be represented with this resource as the subject of the RDF statements (what is called "outbound" triples).

But there are in fact Linked Open Data publication receipes that would match your original requirements better. Check out the patterns that recommend "inbound" triples to be also published as part of the data served at a resource's URI. Especially the "Symmetric Concise Bounded Description" at http://www.w3.org/Submission/CBD/

Usually this can be configured as part of an RDF/SPARQL engine that lies behind the linked data service. Or if you're not using an RDF/SPARQL engine tuned for different style LOD publication, then you have to make sure that the Linked Data service layer on top of your storage retrieves the "inbound" triples and adds them to the data.

Best,

Antoine


> Dear all,
>
> I'm involved in a new modelling versión of UNESCO Thesaurus. The current is at http://skos.um.es/unescothes
>
> The integration of this vocabulary into Linked Open Data enviroment it's a bit difficult. The main reason for this is that there is serveral situations in which the request of a SKOS resource deliver incomplete information about the real structure of a KOS.
>
> Case 1
>
> <COL> rdf:type  skos:Collection;
>      skos:member  <Concept_A> .
>
> <Concept_A>  rdf:type  skos:Concept .
>
> With a direct request to <Concept_A> it's impossible to know the collections <Concept_A> belong to.
>
>
> Case 2
>
> Other issue is the location of access points to a concept collection. Sometimes modelling micro-thesaurus as skos:Collection has been suggested. But, How can be possible identify access points (Top Concepts) into a skos:Collection? The recommendation set skos:ConceptScheme as the domain of skos:hasTopConcept (same for range of skos:topConceptOf).
>
>
> Certainly, an SPARQL Endpoint could solve both issues:
>
> For Case 1:
>
> SELECT ?col WHERE {
> ?col skos:member <Concept_A> .
> }
>
> For Case 2:
>
> SELECT ?topcol WHERE {
> ?concept skos:topConceptOf ?scheme .
> ?col skos:member ?concept .
> }
>
> But the scenario that I propose don't have an SPARQL Endpoint. Only directly request to SKOS resorce from a RDF Client, dereferencing URI resource, with content negotiation and follow the SKOS properties to discover links with other resources of the same KOS. I repeat: NO SPARQL AVALAIBLE.
>
> For this reason, we had develop a set of custom properties to solve all this and obtain an adecuate modelling. I attach the RDF/OWL file. Personally, I do not like to develop this kind of solution, but there isn't suitable properties in the SKOS recommendation to solve the issues in the posed scenario.
>
> We want to know your opinion and suggestions on our work.
>
> Thanks in advance and Regards,
> Juan
>
> --
> Juan Antonio Pastor Sánchez, Ph.D.
> Dep. of Information and Documentation
> Faculty of Communication and Documentation
> University of Murcia
> phone: +34 868 88 7252
> http://webs.um.es/pastor
> pastor@um.es <mailto:pastor@um.es>

Received on Tuesday, 1 October 2013 21:27:04 UTC