geo4web-testbed / ldproxy-design

Design of the "linked data proxy"/"crawlifier proxy"
0 stars 0 forks source link

Backlink from WFS to CSW #8

Closed pvgenuchten closed 8 years ago

pvgenuchten commented 8 years ago

On the proxied wfs-capabilities page and the feature-type page and it's relevant json-ld representations there should be links back to the service metadata (if capabilities has that link; inspire extension) and the dataset/featuretype metadata. Consider that there may be 0, 1 or many links in capabilitities

Rules:

Content negotiation (via the accept header) should return the proper format (html/json-ld/xml) on both endpoints

liekeverhelst commented 8 years ago

In schema.org we have this sequence:

schema:DataCatalog schema:dataset schema:Dataset

The backlink (inverse property) does not exist, so I propose to use

schema:DataCatalog schema:hasPart schema:Dataset

and its inverse:

schema:Dataset schema:isPartOf schema:DataCatalog
cportele commented 8 years ago

@liekeverhelst This looks reasonable to me! Thanks.

azahnen commented 8 years ago

@pvgenuchten When trying to use on of these urls I am redirected to the login. Am I doing it wrong?

In the meantime I am linking to: http://opendatacat.net/geonetwork-geo4web/doc/dataset/76091be7-358a-4a44-8182-b4139c96c6a4

pvgenuchten commented 8 years ago

The csw proxy is not yet available, so those urls will forward to login page

Groet Paul van Genuchten

Op 9 mrt. 2016 om 11:05 heeft Andreas Zahnen notifications@github.com het volgende geschreven:

@pvgenuchten When trying to use on of these urls I am redirected to the login. Am I doing it wrong?

http://opendatacat.net/geonetwork-geo4web/id/dataset/76091be7-358a-4a44-8182-b4139c96c6a4 http://opendatacat.net/geonetwork-geo4web/srv/id/dataset/76091be7-358a-4a44-8182-b4139c96c6a4 http://opendatacat.net/geonetwork-geo4web/cswproxy?url=... http://opendatacat.net/geonetwork-geo4web/srv/cswproxy?url=... In the meantime I am linking to: http://opendatacat.net/geonetwork-geo4web/doc/dataset/76091be7-358a-4a44-8182-b4139c96c6a4

— Reply to this email directly or view it on GitHub.