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

Should we use seeAlso or create a predicate for LoCFDD or Wikidata? #6

Open
ross-spencer opened this issue Nov 10, 2019 · 0 comments
Open

Comments

@ross-spencer
Copy link
Member

I will hedge my bets and use seeAlso for both, but there seems to be a pattern out there of having specific properties. This has the benefit of being easy to find, but is yet another property. As a developer or user of the service I might only want a property if I also wanted to describe the resource type, e.g. what the LoC service offers and what users should consider when looking up those links.

@ross-spencer ross-spencer changed the title Should we use seeAlso or create a predicate for LoCFDD or Wikidata Should we use seeAlso or create a predicate for LoCFDD or Wikidata? Nov 10, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant