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.

Sign up for GitHub

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

Jump to bottom

handle sameAs and deprecation in resources #72

Open
rob-metalinkage opened this issue Oct 15, 2021 · 0 comments
Open

handle sameAs and deprecation in resources #72

rob-metalinkage opened this issue Oct 15, 2021 · 0 comments

Comments

@rob-metalinkage
Copy link
Contributor

resources could gather all the known properties of a resource using the owl:sameAs semantics, deduplicating object values.

In addition status highlighting for deprecated could use a (configurable) predicate value to point users to the resource they should use by preference.

Should owl:sameAs semantics be used this way if the subject is marked deprecated? If not then strict semantics suggests sameAs cannot have different status values.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@rob-metalinkage