-
Notifications
You must be signed in to change notification settings - Fork 838
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 a (wikidata) example to /sameAs #2482
Comments
I'm trying to work through how this relates to EIDR in #2469. There are some complications. Example 1 - work/title levelThis example talks about the movie in its most abstract general sense first, mentioning a wikidata sameAs link, a titleEIDR, and its name and a disambiguatingDescription. It then lists 4 specific edits with eidrEIDR and disambiguatingDescription for each.
Example 2 - edit(ion) levelThis example is all about a specific edition ("expression" in FRBR terminology). Therefore to
|
Being pedantic shouldn't the Wikidata uri be |
@RichardWallis definition for sameAs says it's the "URL of a reference Web page..." so it should be /wiki/ URL not the /entity/ |
Note to self: RTFM |
@philbarker But where is "Web page" defined ? |
This issue is being tagged as Stale due to inactivity. |
Shipped in V11.0 release. |
To be fair the examples here use the dbpedia ID, not the dbpedia page: And Wikipedia itself is linking to the wikidata.org/entity link: |
This reminds me of a discussion about adding the subtype homePage (#2062). That discussion exposed that some people use social media profiles as their main web-presence, so Further discussion exposed that these social-media sites generally use aliases called folksonomy tags as identifiers which are specific to the domain, usually the ampersand is used to prefix an identity and a hashtag identifies a collection of related topics. For instance, the politician @ocasio2018, is now far more widely known for the folksonomy tag that twitter gifted to her @aoc. My suggestion here is that having two new properties, ontologies (Wikidata, ISNI etc) and folksonomies (ampersand and hashtag identities -- accompanied with the specific domain) might make it easier for data-consumers to do more targeted searches. I've always used sameAs, to point to the human readable page because many persons and organizations are too new for Wikipedia pages and without a Wikipedia page, you can't get a Wikidata entity. Additionally, most webpages have the structured data embedded within the human readable version. (I believe the previous guidance for https://schema.org/sameAs included news articles social media pages as a collection.) IMHO Wikidata (and therefore Wikipedia) may be trustworthy as "a reference Web page that unambiguously indicates the item's identity." for the thing type, but it is highly dubious for persons and creativeworks because the platform has been captured by politicos and special interests. |
Let's use Douglas Adams, @vrandezo
The text was updated successfully, but these errors were encountered: