Missing licencing on Linked Data pages

[ajtucker]

Hi,

I've been trying to figure out where the metadata for the Linked Data pages is generated so that I can submit a PR for adding some licensing/copyright statements to the pages.

E.g. fetching http://linkedgeodata.org/triplify/node264695865 as Turtle gives the following metadata for the page:

<http://linkedgeodata.org/data/triplify/node264695865>
      rdfs:label "RDF description of B'liebig" ;
      foaf:primaryTopic lgd:node264695865 .

as well as the rest of the normal data describing the place.  In line with Geonames and others, it would be good to declare the licensing and/or copyright of the data here as well, e.g.:

<http://linkedgeodata.org/data/triplify/node264695865>
      rdfs:label "RDF description of B'liebig" ;
      foaf:primaryTopic lgd:node264695865 ;
      dcterms:licence <http://opendatacommons.org/licenses/odbl/1.0/> .

Can you point to where this metadata is generated?  I've been trying to untangle the Github project and its dependencies, but can't see where these statements are made.

Cheers,
Alex.

[Claus Stadler]

Hi Alex,

Thank you for your the pointer to the lack of licence information on the Linked Data pages.

On the Github page

    https://github.com/GeoKnow/LinkedGeoData

there is a link labelled "You can view the Sparqlify Mappings for LinkedGeoData here.", which points to

    https://raw.githubusercontent.com/GeoKnow/LinkedGeoData/master/linkedgeodata-core/src/main/resources/org/aksw/linkedgeodata/sml/LinkedGeoData-Triplify-IndividualViews.sml

I created a separate mapping file specifically for the licence information:

    https://raw.githubusercontent.com/GeoKnow/LinkedGeoData/master/linkedgeodata-core/src/main/resources/org/aksw/linkedgeodata/sml/LinkedGeoData-Triplify-Licences.sml

You will notice that on the Linked Data resources, such as http://linkedgeodata.org/triplify/node264695865 there are now rdfs:isDefinedBy triples, which then carry the license information.


I yet need to find out how to make pubby expose resources and their metadata at the same time. (Maybe you have a suggestion?)


Cheers,
Claus

--
You received this message because you are subscribed to the Google Groups "Linked Geo Data" group.
To unsubscribe from this group and stop receiving emails from it, send an email to linked-geo-da...@googlegroups.com.
To post to this group, send email to linked-...@googlegroups.com.
Visit this group at http://groups.google.com/group/linked-geo-data.
For more options, visit https://groups.google.com/d/optout.

-- 
Dipl. Inf. Claus Stadler
Department of Computer Science, University of Leipzig
Research Group: http://aksw.org/
Workpage & WebID: http://aksw.org/ClausStadler
Phone: +49 341 97-32260

[Alex Tucker]

Hi Claus,

Thanks for having a look at this and getting back so quickly.

I'm not sure the extra mapping file quite does what's needed though.  Taking your example node, let's call it N (URIs below).  Fetching N using HTTP GET results in a 303 redirect to N'.

Following the Geonames pattern, I'd expect the license statement to be (N' dct:license O).  As I understand it, N' is the URI of the published RDF document containing the RDF statements that talk about N.  As such, when we assert the license of the document, we're essentially saying that the contained information is licensed in the same way.

However, the extra mapping file expresses that (N rdfs:isDefinedBy M) and (M dct:license O).  But M isn't the RDF document containing the statements about N, it's just a separate resource and actually has a published RDF document at M'.

It looks as though the Pubby config is the place to add this kind of metadata, but I can't see how this is all wired up just yet...

Cheers,

Alex.

N = <http://linkedgeodata.org/triplify/node264695865>

N' = <http://linkedgeodata.org/data/triplify/node264695865>

M = <http://linkedgeodata.org/triplify/meta/node264695865>

M' = <http://linkedgeodata.org/data/triplify/meta/node264695865>

O = <http://opendatacommons.org/licenses/odbl/1.0/>

[ajtucker]

Hi Claus,

I've had chance to dig into this, but haven't come to many useful conclusions I'm afraid.

I wanted to get a local version of LGD up and running in order to dig into where in Pubby to fix the metadata about the published LOD pages.  I've followed https://github.com/GeoKnow/LinkedGeoData and got a local db running where I can run the sparqlify commandline tools to generate instance data and the ontology.  I further looked into how to get the sparqlify web service running so that I could put Pubby on top, but things seem to be in quite a state of bit-rot and I've not managed to get a version of sparqlify that runs or even compiles in order to run it as a SPARQL service.

What's the current architecture of LGD and what's the future?  I had hoped that by digging into this and offering up a patch, I could help get the licensing information into the LOD pages, but I'm not sure that my efforts are heading in the right direction.

Cheers,

Alex.

To unsubscribe from this group and stop receiving emails from it, send an email to linked-geo-data+unsubscribe@googlegroups.com.
To post to this group, send email to linked-geo-data@googlegroups.com.

Visit this group at http://groups.google.com/group/linked-geo-data.
For more options, visit https://groups.google.com/d/optout.

-- 
Dipl. Inf. Claus Stadler
Department of Computer Science, University of Leipzig
Research Group: http://aksw.org/
Workpage & WebID: http://aksw.org/ClausStadler
Phone: +49 341 97-32260

--
You received this message because you are subscribed to the Google Groups "Linked Geo Data" group.

To unsubscribe from this group and stop receiving emails from it, send an email to linked-geo-data+unsubscribe@googlegroups.com.
To post to this group, send email to linked-geo-data@googlegroups.com.