Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Link to landing page from all responses? #181

Closed
sampov2 opened this issue Nov 7, 2018 · 4 comments
Closed

Link to landing page from all responses? #181

sampov2 opened this issue Nov 7, 2018 · 4 comments
Labels
no change OGC API: Common Issue related to general resources or requirements (see #190) OGC API: Features Issue related to feature resources (see #190) Part 1: Core Issue related to Part 1 - Core progress: resolution agreed

Comments

@sampov2
Copy link
Contributor

sampov2 commented Nov 7, 2018

I would like to raise a topic for discussion: should responses from a WFS 3.0 should link back to the landing page of the service?

This would allow clients to backtrack from any server response to the landing page and retrieve more information about the service. This would allow clients to discover which extensions are supported by the service as well as find related documentation as well as the collections available in the service.

@akuckartz
Copy link

Which RDF property so you suggest for this?

@sampov2
Copy link
Contributor Author

sampov2 commented Nov 8, 2018

By RDF property, do you mean the rel value of the link? I think "home" might be appropriate

@cportele cportele added the Part 1: Core Issue related to Part 1 - Core label Feb 25, 2019
@cportele cportele added OGC API: Common Issue related to general resources or requirements (see #190) OGC API: Features Issue related to feature resources (see #190) labels Mar 5, 2019
@pvretano
Copy link
Contributor

pvretano commented Apr 8, 2019

08-APR-2019: Teleconference notes: The core already defines a links section in most responses which gives implementors the option to add a home link and/or to interlink their service as much as they like. The sentiment of the group was that making this mandatory was a bit too strong and a better case would be required before going that.

@cportele
Copy link
Member

cportele commented Jun 3, 2019

Conference call, 3 June 2019: Closing this issue as there was no further discussion. If new aspects are to be considered, the issue can be reopened.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
no change OGC API: Common Issue related to general resources or requirements (see #190) OGC API: Features Issue related to feature resources (see #190) Part 1: Core Issue related to Part 1 - Core progress: resolution agreed
Projects
Part 1: Core
  
Done
Development

No branches or pull requests

4 participants