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

Add an example of a Client/Server scenario demonstrating profile inheritence #748

Open
nicholascar opened this issue Feb 10, 2019 · 3 comments

Comments

@nicholascar
Copy link
Contributor

commented Feb 10, 2019

From ShEx IG:

We were unsure what to make of "inheritance", as we are not aware of any generalized notion of inheritance that would make sense across implementation technologies. It would be helpful to motivate this with a testable use case, e.g., a server implementation which responds to Accept-Profile by calculating the "best" response for processing a Profile Ontology description. A test of inheritance would include the notion that inheriting imposes further constraints, and that the entity being inherited from may in turn inherit from something else. ShEx shape inheritance has this behavior.

@nicholascar

This comment has been minimized.

Copy link
Contributor Author

commented Feb 10, 2019

The server should attempt to reply with a profile that best matches the client request. The order of preference is an exact match, followed by a profile (perhaps transitively) of the requested profile.

(+EXAMPLE)

@larsgsvensson larsgsvensson added this to To do in Content Negotiation by Profile via automation Feb 11, 2019

@nicholascar nicholascar modified the milestones: PROF 3PWD, Conneg 2PWD Feb 13, 2019

@nicholascar

This comment has been minimized.

Copy link
Contributor Author

commented Feb 28, 2019

If a client requests a profile but gets a narrower profile, the Server should set its responses Content-Profile header to the profile identifier that the Client requested, not the identifier of the narrower profile as the client might not understand the narrower profile identifier.

@nicholascar

This comment has been minimized.

Copy link
Contributor Author

commented May 2, 2019

This Issue is now addressed by Section 6.2.2 in the document

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.