Suppose I publish a web page about a notable person, building or other entity; and that the subject has a Wikidata entry.
What's the best meta header, to assert that the page is about the same subject as the Wikidata entry?
I'm thinking of something like:
<link rel="foo" href="https://www.wikidata.org/wiki/Q42">
or
<meta name="DC.bar" content="https://www.wikidata.org/wiki/Q42">
but what values of foo or bar?
Given the likely ubiquity of Wikidata in the near future, should we mint:
<link rel="wikidata"
or a more generic:
<link rel="datasource" ?
Are there any such headers already in the wild? Should Wikipedia articles and pages on sister projects include such headers?
Hoi, Every Wikipedia, Wikivoyage, Wikisource and Commons "article" has an indicator that there is a Wikidata item associated with it already. It is part of the tools in the sidebar.
Or are you talking about web pages external to the WMF? Thanks, GerardM
On 26 February 2014 14:20, Andy Mabbett andy@pigsonthewing.org.uk wrote:
Suppose I publish a web page about a notable person, building or other entity; and that the subject has a Wikidata entry.
What's the best meta header, to assert that the page is about the same subject as the Wikidata entry?
I'm thinking of something like:
<link rel="foo" href="https://www.wikidata.org/wiki/Q42">
or
<meta name="DC.bar" content="https://www.wikidata.org/wiki/Q42">
but what values of foo or bar?
Given the likely ubiquity of Wikidata in the near future, should we mint:
<link rel="wikidata"
or a more generic:
<link rel="datasource" ?
Are there any such headers already in the wild? Should Wikipedia articles and pages on sister projects include such headers?
-- Andy Mabbett @pigsonthewing http://pigsonthewing.org.uk
Wikidata-l mailing list Wikidata-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikidata-l
On 26 February 2014 13:25, Gerard Meijssen gerard.meijssen@gmail.com wrote:
Every Wikipedia, Wikivoyage, Wikisource and Commons "article" has an indicator that there is a Wikidata item associated with it already. It is part of the tools in the sidebar.
But that's in the body of the article, not the head; and has no associated metadata. We already publish other "rel" metadata headers, for example:
<link rel="edit" <link rel="search" <link rel="EditURI"
Or are you talking about web pages external to the WMF?
Yes. "Suppose I publish..."
Isn't there some way to do this with schema.org?
On Wed, Feb 26, 2014 at 9:15 AM, Andy Mabbett andy@pigsonthewing.org.uk wrote:
On 26 February 2014 13:25, Gerard Meijssen gerard.meijssen@gmail.com wrote:
Every Wikipedia, Wikivoyage, Wikisource and Commons "article" has an indicator that there is a Wikidata item associated with it already. It is part of the tools in the sidebar.
But that's in the body of the article, not the head; and has no associated metadata. We already publish other "rel" metadata headers, for example:
<link rel="edit" <link rel="search" <link rel="EditURI"
Or are you talking about web pages external to the WMF?
Yes. "Suppose I publish..."
-- Andy Mabbett @pigsonthewing http://pigsonthewing.org.uk
Wikidata-l mailing list Wikidata-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikidata-l
How about using RDFa and foaf:primaryTopic like in this example https://en.wikipedia.org/wiki/RDFa#XHTML.2BRDFa_1.0_example
2014-02-26 20:18 GMT+02:00 Paul Houle ontology2@gmail.com:
Isn't there some way to do this with schema.org?
On Wed, Feb 26, 2014 at 9:15 AM, Andy Mabbett andy@pigsonthewing.org.uk wrote:
On 26 February 2014 13:25, Gerard Meijssen gerard.meijssen@gmail.com
wrote:
Every Wikipedia, Wikivoyage, Wikisource and Commons "article" has an indicator that there is a Wikidata item associated with it already. It
is
part of the tools in the sidebar.
But that's in the body of the article, not the head; and has no associated metadata. We already publish other "rel" metadata headers, for example:
<link rel="edit" <link rel="search" <link rel="EditURI"
Or are you talking about web pages external to the WMF?
Yes. "Suppose I publish..."
-- Andy Mabbett @pigsonthewing http://pigsonthewing.org.uk
Wikidata-l mailing list Wikidata-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikidata-l
-- Paul Houle Expert on Freebase, DBpedia, Hadoop and RDF (607) 539 6254 paul.houle on Skype ontology2@gmail.com
Wikidata-l mailing list Wikidata-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikidata-l
On 26 February 2014 10:45, Joonas Suominen joonas.suominen@wikimedia.fi wrote:
How about using RDFa and foaf:primaryTopic like in this example https://en.wikipedia.org/wiki/RDFa#XHTML.2BRDFa_1.0_example
2014-02-26 20:18 GMT+02:00 Paul Houle ontology2@gmail.com:
Isn't there some way to do this with schema.org?
The FOAF options were designed for relations between entities and documents -
foaf:primaryTopic relates a Document to a thing that the doc is primarily about (i.e. assumes entity IDs as value, pedantically).
the inverse, foaf:isPrimaryTopicOf, was designed to allow an entity description in a random page to anchor itself against well known pages. In particular we had Wikipedia in mind.
http://xmlns.com/foaf/spec/#term_primaryTopic http://xmlns.com/foaf/spec/#term_isPrimaryTopicOf
(Both of these share a classic Semantic Web pickyness about distinguishing things from pages about those things).
Much more recently at schema.org we've added a new property/relationship called http://schema.org/sameAs
It relates an entity to a reference page (e.g. wikipedia) that can be used as a kind of proxy identifier for the real world thing that it describes. Not to be confused with owl:sameAs which is for saying "here are two ways of identifying the exact same real world entity".
None of these are a perfect fit for a relationship between a random Web page and a reference page. But maybe close enough?
Both FOAF and schema.org are essentially dictionaries of hopefully-useful terms, so you can use them in HTML head, or body, according to taste, policy, tooling etc. And you can choose a syntax (microdata, rdfa, json-ld etc.).
I'd recommend using the new schema.org 'sameAs', .e.g. in rdfa lite,
<link href="https://en.wikipedia.org/wiki/Buckingham_Palace" property="http://schema.org/sameAs" />
This technically says "the thing we're describing in the current element is Buckingham_Palace. If you want to be more explicit and say "this Web page is about a real world Place and that place is Buckingham_Palace ... you can do this too with a bit more nesting; the HTML body might be a better place for it.
Dan
Hello
*Really* not meaning to jump down any http-range-14 rabbit holes but wasn't there a plan for wikidata to have uris representing things and pages about those things?
From conversations on this list I sketched a picture a while back of all
the planned URIs: http://smethur.st/wp-uploads/2012/07/46159634-wikidata.png
Where http://wikidata.org/id/Qetc Was the "thing" uri (which you could point a foaf:PrimaryTopic at) and http://wikidata.org/wiki/Qetc
Was the document uri
Mainly asking not for the wikipedia > wikidata relationships but wondering if there's a more up to date picture of supported wikidata uri patterns and redirects?
Recently I was trying to find a way to programmatically get wikidata uris from wikipedia uris and tried various combinations of: http://wikidata.org/title/enwiki:Berlin http://en.wikidata.org/item/Berlin http://en.wikidata.org/title/Berlin
(all mentioned on the list / wiki) but all of them return a 404
Is the a way to do this?
Michael
On 26/02/2014 19:09, "Dan Brickley" danbri@danbri.org wrote:
On 26 February 2014 10:45, Joonas Suominen joonas.suominen@wikimedia.fi wrote:
How about using RDFa and foaf:primaryTopic like in this example https://en.wikipedia.org/wiki/RDFa#XHTML.2BRDFa_1.0_example
2014-02-26 20:18 GMT+02:00 Paul Houle ontology2@gmail.com:
Isn't there some way to do this with schema.org?
The FOAF options were designed for relations between entities and documents -
foaf:primaryTopic relates a Document to a thing that the doc is primarily about (i.e. assumes entity IDs as value, pedantically).
the inverse, foaf:isPrimaryTopicOf, was designed to allow an entity description in a random page to anchor itself against well known pages. In particular we had Wikipedia in mind.
http://xmlns.com/foaf/spec/#term_primaryTopic http://xmlns.com/foaf/spec/#term_isPrimaryTopicOf
(Both of these share a classic Semantic Web pickyness about distinguishing things from pages about those things).
Much more recently at schema.org we've added a new property/relationship called http://schema.org/sameAs
It relates an entity to a reference page (e.g. wikipedia) that can be used as a kind of proxy identifier for the real world thing that it describes. Not to be confused with owl:sameAs which is for saying "here are two ways of identifying the exact same real world entity".
None of these are a perfect fit for a relationship between a random Web page and a reference page. But maybe close enough?
Both FOAF and schema.org are essentially dictionaries of hopefully-useful terms, so you can use them in HTML head, or body, according to taste, policy, tooling etc. And you can choose a syntax (microdata, rdfa, json-ld etc.).
I'd recommend using the new schema.org 'sameAs', .e.g. in rdfa lite,
<link href="https://en.wikipedia.org/wiki/Buckingham_Palace" property="http://schema.org/sameAs" />
This technically says "the thing we're describing in the current element is Buckingham_Palace. If you want to be more explicit and say "this Web page is about a real world Place and that place is Buckingham_Palace ... you can do this too with a bit more nesting; the HTML body might be a better place for it.
Dan
Wikidata-l mailing list Wikidata-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikidata-l
----------------------------- http://www.bbc.co.uk This e-mail (and any attachments) is confidential and may contain personal views which are not the views of the BBC unless specifically stated. If you have received it in error, please delete it from your system. Do not use, copy or disclose the information in any way nor act in reliance on it and notify the sender immediately. Please note that the BBC monitors e-mails sent or received. Further communication will signify your consent to this. -----------------------------
Hi,
On 26/02/14 22:40, Michael Smethurst wrote:
Hello
*Really* not meaning to jump down any http-range-14 rabbit holes but wasn't there a plan for wikidata to have uris representing things and pages about those things?
From conversations on this list I sketched a picture a while back of all the planned URIs: http://smethur.st/wp-uploads/2012/07/46159634-wikidata.png
Where http://wikidata.org/id/Qetc Was the "thing" uri (which you could point a foaf:PrimaryTopic at)
As Denny said in reply to another message, the preferred URI for this is
http://www.wikidata.org/entity/Qetc
This is also the form of URIs used within Wikidata data for certain things (e.g., coordinates that refer to earth use the URI "http://www.wikidata.org/entity/Q2" to do so, even in JSON).
and http://wikidata.org/wiki/Qetc
Was the document uri
Yes. However, for metadata it is usually preferred to use the entity URI, since the document http://wikidata.org/wiki/Qetc is just an automatic UI rendering of the data, and as such relatively uninteresting. One will eventually get (using content negotiation) all data in RDF from http://www.wikidata.org/entity/Qetc (JSON should already work, and html works of course, when opening the entity URI in normal browsers). The only reason for using the wiki URI directly would be if one uses a property that requires a document as its value, but in this case one should probably better use another property.
Best regards,
Markus
Mainly asking not for the wikipedia > wikidata relationships but wondering if there's a more up to date picture of supported wikidata uri patterns and redirects?
Recently I was trying to find a way to programmatically get wikidata uris from wikipedia uris and tried various combinations of: http://wikidata.org/title/enwiki:Berlin http://en.wikidata.org/item/Berlin http://en.wikidata.org/title/Berlin
(all mentioned on the list / wiki) but all of them return a 404
Is the a way to do this?
Michael
On 26/02/2014 19:09, "Dan Brickley" danbri@danbri.org wrote:
On 26 February 2014 10:45, Joonas Suominen joonas.suominen@wikimedia.fi wrote:
How about using RDFa and foaf:primaryTopic like in this example https://en.wikipedia.org/wiki/RDFa#XHTML.2BRDFa_1.0_example
2014-02-26 20:18 GMT+02:00 Paul Houle ontology2@gmail.com:
Isn't there some way to do this with schema.org?
The FOAF options were designed for relations between entities and documents -
foaf:primaryTopic relates a Document to a thing that the doc is primarily about (i.e. assumes entity IDs as value, pedantically).
the inverse, foaf:isPrimaryTopicOf, was designed to allow an entity description in a random page to anchor itself against well known pages. In particular we had Wikipedia in mind.
http://xmlns.com/foaf/spec/#term_primaryTopic http://xmlns.com/foaf/spec/#term_isPrimaryTopicOf
(Both of these share a classic Semantic Web pickyness about distinguishing things from pages about those things).
Much more recently at schema.org we've added a new property/relationship called http://schema.org/sameAs
It relates an entity to a reference page (e.g. wikipedia) that can be used as a kind of proxy identifier for the real world thing that it describes. Not to be confused with owl:sameAs which is for saying "here are two ways of identifying the exact same real world entity".
None of these are a perfect fit for a relationship between a random Web page and a reference page. But maybe close enough?
Both FOAF and schema.org are essentially dictionaries of hopefully-useful terms, so you can use them in HTML head, or body, according to taste, policy, tooling etc. And you can choose a syntax (microdata, rdfa, json-ld etc.).
I'd recommend using the new schema.org 'sameAs', .e.g. in rdfa lite,
<link href="https://en.wikipedia.org/wiki/Buckingham_Palace" property="http://schema.org/sameAs" />
This technically says "the thing we're describing in the current element is Buckingham_Palace. If you want to be more explicit and say "this Web page is about a real world Place and that place is Buckingham_Palace ... you can do this too with a bit more nesting; the HTML body might be a better place for it.
Dan
Wikidata-l mailing list Wikidata-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikidata-l
http://www.bbc.co.uk This e-mail (and any attachments) is confidential and may contain personal views which are not the views of the BBC unless specifically stated. If you have received it in error, please delete it from your system. Do not use, copy or disclose the information in any way nor act in reliance on it and notify the sender immediately. Please note that the BBC monitors e-mails sent or received. Further communication will signify your consent to this.
Wikidata-l mailing list Wikidata-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikidata-l
hello
On 27/02/2014 08:44, "Markus Krötzsch" markus@semantic-mediawiki.org wrote:
Hi,
On 26/02/14 22:40, Michael Smethurst wrote:
Hello
*Really* not meaning to jump down any http-range-14 rabbit holes but wasn't there a plan for wikidata to have uris representing things and pages about those things?
From conversations on this list I sketched a picture a while back of all the planned URIs: http://smethur.st/wp-uploads/2012/07/46159634-wikidata.png
Where http://wikidata.org/id/Qetc Was the "thing" uri (which you could point a foaf:PrimaryTopic at)
As Denny said in reply to another message, the preferred URI for this is
http://www.wikidata.org/entity/Qetc
This is also the form of URIs used within Wikidata data for certain things (e.g., coordinates that refer to earth use the URI "http://www.wikidata.org/entity/Q2" to do so, even in JSON).
Ok, makes sense
So the correct "sem web way" would be: <link rel="foaf:primaryTopic" href="https://www.wikidata.org/entity/Qetc">
And the schema.org way would be <link href="https://wikidata.org/wiki/Qetc" property="http://schema.org/sameAs" />
and http://wikidata.org/wiki/Qetc
Was the document uri
Yes. However, for metadata it is usually preferred to use the entity URI, since the document http://wikidata.org/wiki/Qetc is just an automatic UI rendering of the data, and as such relatively uninteresting. One will eventually get (using content negotiation) all data in RDF from http://www.wikidata.org/entity/Qetc (JSON should already work, and html works of course, when opening the entity URI in normal browsers). The only reason for using the wiki URI directly would be if one uses a property that requires a document as its value, but in this case one should probably better use another property.
Does that conflate the can't send that / 303 part with the content negotiation part?
Guessing it follows the dbpedia pattern which isn't always nice to work with
Personally would prefer /entity/ to 303 to a generic document uri and do the conneg part from there
===
What about the second part of the question? Is there a full list of supported uri patterns for wikidata?
If I know everything needed to construct a wikipedia uri (language and uri key) is it possible to construct a uri that redirects to a wikidata Q style uri?
Are there any convenience uris to map from wikipedia to wikidata?
Thanks michael
Best regards,
Markus
Mainly asking not for the wikipedia > wikidata relationships but wondering if there's a more up to date picture of supported wikidata uri patterns and redirects?
Recently I was trying to find a way to programmatically get wikidata uris from wikipedia uris and tried various combinations of: http://wikidata.org/title/enwiki:Berlin http://en.wikidata.org/item/Berlin http://en.wikidata.org/title/Berlin
(all mentioned on the list / wiki) but all of them return a 404
Is the a way to do this?
Michael
On 26/02/2014 19:09, "Dan Brickley" danbri@danbri.org wrote:
On 26 February 2014 10:45, Joonas Suominen joonas.suominen@wikimedia.fi wrote:
How about using RDFa and foaf:primaryTopic like in this example https://en.wikipedia.org/wiki/RDFa#XHTML.2BRDFa_1.0_example
2014-02-26 20:18 GMT+02:00 Paul Houle ontology2@gmail.com:
Isn't there some way to do this with schema.org?
The FOAF options were designed for relations between entities and documents -
foaf:primaryTopic relates a Document to a thing that the doc is primarily about (i.e. assumes entity IDs as value, pedantically).
the inverse, foaf:isPrimaryTopicOf, was designed to allow an entity description in a random page to anchor itself against well known pages. In particular we had Wikipedia in mind.
http://xmlns.com/foaf/spec/#term_primaryTopic http://xmlns.com/foaf/spec/#term_isPrimaryTopicOf
(Both of these share a classic Semantic Web pickyness about distinguishing things from pages about those things).
Much more recently at schema.org we've added a new property/relationship called http://schema.org/sameAs
It relates an entity to a reference page (e.g. wikipedia) that can be used as a kind of proxy identifier for the real world thing that it describes. Not to be confused with owl:sameAs which is for saying "here are two ways of identifying the exact same real world entity".
None of these are a perfect fit for a relationship between a random Web page and a reference page. But maybe close enough?
Both FOAF and schema.org are essentially dictionaries of hopefully-useful terms, so you can use them in HTML head, or body, according to taste, policy, tooling etc. And you can choose a syntax (microdata, rdfa, json-ld etc.).
I'd recommend using the new schema.org 'sameAs', .e.g. in rdfa lite,
<link href="https://en.wikipedia.org/wiki/Buckingham_Palace" property="http://schema.org/sameAs" />
This technically says "the thing we're describing in the current element is Buckingham_Palace. If you want to be more explicit and say "this Web page is about a real world Place and that place is Buckingham_Palace ... you can do this too with a bit more nesting; the HTML body might be a better place for it.
Dan
Wikidata-l mailing list Wikidata-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikidata-l
http://www.bbc.co.uk This e-mail (and any attachments) is confidential and may contain personal views which are not the views of the BBC unless specifically stated. If you have received it in error, please delete it from your system. Do not use, copy or disclose the information in any way nor act in reliance on it and notify the sender immediately. Please note that the BBC monitors e-mails sent or received. Further communication will signify your consent to this.
Wikidata-l mailing list Wikidata-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikidata-l
Wikidata-l mailing list Wikidata-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikidata-l
----------------------------- http://www.bbc.co.uk This e-mail (and any attachments) is confidential and may contain personal views which are not the views of the BBC unless specifically stated. If you have received it in error, please delete it from your system. Do not use, copy or disclose the information in any way nor act in reliance on it and notify the sender immediately. Please note that the BBC monitors e-mails sent or received. Further communication will signify your consent to this. -----------------------------
On Thu, Feb 27, 2014 at 11:49 AM, Michael Smethurst < michael.smethurst@bbc.co.uk> wrote:
If I know everything needed to construct a wikipedia uri (language and uri key) is it possible to construct a uri that redirects to a wikidata Q style uri?
Are there any convenience uris to map from wikipedia to wikidata?
You can use Special:ItemByTitle like this: http://www.wikidata.org/wiki/Special:ItemByTitle/enwiki/BBC
Cheers, Micru
Which is great !
And it also work with aliases
http://www.wikidata.org/wiki/Special:ItemByTitle/enwiki/British Broadcasting Corporation
Mohamed
On Thu, Apr 24, 2014 at 12:10 PM, David Cuenca dacuetu@gmail.com wrote:
On Thu, Feb 27, 2014 at 11:49 AM, Michael Smethurst michael.smethurst@bbc.co.uk wrote:
If I know everything needed to construct a wikipedia uri (language and uri key) is it possible to construct a uri that redirects to a wikidata Q style uri?
Are there any convenience uris to map from wikipedia to wikidata?
You can use Special:ItemByTitle like this: http://www.wikidata.org/wiki/Special:ItemByTitle/enwiki/BBC
Cheers, Micru
Wikidata-l mailing list Wikidata-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikidata-l
On 24/04/2014 11:10, "David Cuenca" dacuetu@gmail.com wrote:
On Thu, Feb 27, 2014 at 11:49 AM, Michael Smethurst michael.smethurst@bbc.co.uk wrote:
If I know everything needed to construct a wikipedia uri (language and uri key) is it possible to construct a uri that redirects to a wikidata Q style uri?
Are there any convenience uris to map from wikipedia to wikidata?
You can use Special:ItemByTitle like this: http://www.wikidata.org/wiki/Special:ItemByTitle/enwiki/BBC
Haha, fantastic
Thanks Micru
michael
Cheers, Micru
----------------------------- http://www.bbc.co.uk This e-mail (and any attachments) is confidential and may contain personal views which are not the views of the BBC unless specifically stated. If you have received it in error, please delete it from your system. Do not use, copy or disclose the information in any way nor act in reliance on it and notify the sender immediately. Please note that the BBC monitors e-mails sent or received. Further communication will signify your consent to this. -----------------------------
Am 27.02.2014 09:44, schrieb Markus Krötzsch:
Yes. However, for metadata it is usually preferred to use the entity URI, since the document http://wikidata.org/wiki/Qetc is just an automatic UI rendering of the data, and as such relatively uninteresting. One will eventually get (using content negotiation) all data in RDF from http://www.wikidata.org/entity/Qetc (JSON should already work, and html works of course, when opening the entity URI in normal browsers). The only reason for using the wiki URI directly would be if one uses a property that requires a document as its value, but in this case one should probably better use another property.
To recap and add some details:
http://www.wikidata.org/entity/Q12345 is the canonical URI for the concept
http://www.wikidata.org/wiki/Special:EntityData/Q12345 is the format-agnostic canonical URI of the *description* of the object (the data URI, for short).
http://www.wikidata.org/wiki/Q12345 is the URL of the HTML representation of the description of the concept (i.e. the wiki page)
http://www.wikidata.org/wiki/Special:EntityData/Q12345.json is the URL of the JSON representation of the description of the concept
http://www.wikidata.org/entity/Q12345.json works as a redirect to the above, but is discouraged, since it mixes the concept URI with a format suffix that is meaningful only for the description, not the concept.
HTH Daniel
On Feb 27, 2014 11:02 AM, "Daniel Kinzler" daniel.kinzler@wikimedia.de wrote:
To recap and add some details:
http://www.wikidata.org/entity/Q12345 is the canonical URI for the concept
http://www.wikidata.org/wiki/Special:EntityData/Q12345 is the
format-agnostic
canonical URI of the *description* of the object (the data URI, for
short).
http://www.wikidata.org/wiki/Q12345 is the URL of the HTML representation
of the
description of the concept (i.e. the wiki page)
http://www.wikidata.org/wiki/Special:EntityData/Q12345.json is the URL of
the
JSON representation of the description of the concept
http://www.wikidata.org/entity/Q12345.json works as a redirect to the
above, but
is discouraged, since it mixes the concept URI with a format suffix that
is
meaningful only for the description, not the concept.
HTH Daniel
Is this documented on-wiki?
Am 27.02.2014 12:17, schrieb Andy Mabbett:
On Feb 27, 2014 11:02 AM, "Daniel Kinzler" <daniel.kinzler@wikimedia.de mailto:daniel.kinzler@wikimedia.de> wrote:
To recap and add some details:
http://www.wikidata.org/entity/Q12345 is the canonical URI for the concept
http://www.wikidata.org/wiki/Special:EntityData/Q12345 is the format-agnostic canonical URI of the *description* of the object (the data URI, for short).
http://www.wikidata.org/wiki/Q12345 is the URL of the HTML representation of the description of the concept (i.e. the wiki page)
http://www.wikidata.org/wiki/Special:EntityData/Q12345.json is the URL of the JSON representation of the description of the concept
http://www.wikidata.org/entity/Q12345.json works as a redirect to the above, but is discouraged, since it mixes the concept URI with a format suffix that is meaningful only for the description, not the concept.
HTH Daniel
Is this documented on-wiki?
It's here: https://meta.wikimedia.org/wiki/Wikidata/Notes/URI_scheme
But it should probably be documented on wikidata.org, on Wikidata:URIs or some such. Feel free ;)
-- daniel
Hi all!
To recap and add some details:
http://www.wikidata.org/entity/Q12345 is the canonical URI for the concept
http://www.wikidata.org/wiki/Special:EntityData/Q12345 is the format- agnostic canonical URI of the *description* of the object (the data URI, for short).
http://www.wikidata.org/wiki/Q12345 is the URL of the HTML representation of the description of the concept (i.e. the wiki page)
http://www.wikidata.org/wiki/Special:EntityData/Q12345.json is the URL of the JSON representation of the description of the concept
http://www.wikidata.org/entity/Q12345.json works as a redirect to the above, but is discouraged, since it mixes the concept URI with a format suffix that is meaningful only for the description, not the concept.
Just to make things clear: This is the way it will be in future, too?
If I want to use Wikidata URIs instead of minting my own, I'll take http://www.wikidata.org/entity/Q12345 and Wikidata will keep that URI cool as in "cool URIs don't change"?
Thanks, Christian
On Thu, Apr 24, 2014 at 11:24 AM, Christian.Hauschke@hs-hannover.de wrote:
Just to make things clear: This is the way it will be in future, too?
If I want to use Wikidata URIs instead of minting my own, I'll take http://www.wikidata.org/entity/Q12345 and Wikidata will keep that URI cool as in "cool URIs don't change"?
That's the idea, yes.
Cheers Lydia
Lydia,
If I want to use Wikidata URIs instead of minting my own, I'll take
http://www.wikidata.org/entity/Q12345 and Wikidata will keep that URI cool as in "cool URIs don't change"?
That's the idea, yes.
Thanks a lot! Christian
On 26 February 2014 19:09, Dan Brickley danbri@danbri.org wrote:
I'd recommend using the new schema.org 'sameAs', .e.g. in rdfa lite,
<link href="https://en.wikipedia.org/wiki/Buckingham_Palace" property="http://schema.org/sameAs" />
Thank you. IIRC, "property" is not a valid attribute in HTML 4.01, so that option's not available on some sites (though would be in Wikimedia sites such as Wikipedia)
Am 26.02.2014 20:09, schrieb Dan Brickley:
On 26 February 2014 10:45, Joonas Suominen joonas.suominen@wikimedia.fi wrote:
How about using RDFa and foaf:primaryTopic like in this example https://en.wikipedia.org/wiki/RDFa#XHTML.2BRDFa_1.0_example
2014-02-26 20:18 GMT+02:00 Paul Houle ontology2@gmail.com:
Isn't there some way to do this with schema.org?
The FOAF options were designed for relations between entities and documents -
foaf:primaryTopic relates a Document to a thing that the doc is primarily about (i.e. assumes entity IDs as value, pedantically).
the inverse, foaf:isPrimaryTopicOf, was designed to allow an entity description in a random page to anchor itself against well known pages. In particular we had Wikipedia in mind.
In the RDF mapping of Wikidata, we currently use schema:about for this relationship. E.g. on https://www.wikidata.org/entity/Q42.ttl you will find:
http://de.wikipedia.org/wiki/Douglas_Adams a schema:Article ; schema:about entity:Q42 ; schema:inLanguage "de" .
Note that we say that the Wikipedia page is about the *concept* with the URI https://www.wikidata.org/entity/Q42, not about the *page* with the URI https://www.wikidata.org/wiki/Q42.
As mentioned, foaf:primaryTopic/foaf:isPrimaryTopicOf can also be used to describe such a relationship between an article and a concept/topic. I'm tempted to add that the the RDF mapping, actually...
Anyway: wikidata already defines the schema:about relationship for this. So I suggest to use
<link rel="schema:about" href="https://www.wikidata.org/wiki/Q42">
in the HTML header on Wikipedia. The Wikibase client extension could actually just do that.
-- daniel
On 26 February 2014 18:45, Joonas Suominen joonas.suominen@wikimedia.fi wrote:
How about using RDFa and foaf:primaryTopic like in this example https://en.wikipedia.org/wiki/RDFa#XHTML.2BRDFa_1.0_example
So:
<link rel="foaf:primaryTopic" href="https://www.wikidata.org/wiki/Q42">
That's certainly seems to be a viable option, thank you.
I wonder what are the advantages and disadvantages of that method, over some other @rel value?
Just to be a nitpicker...
On Wed, Feb 26, 2014 at 2:13 PM, Andy Mabbett andy@pigsonthewing.org.ukwrote:
<link rel="foaf:primaryTopic" href="https://www.wikidata.org/wiki/Q42">
/entity/ instead of /wiki/ in the href attribute would be more standard compliant.
Why would you put metadata in the head rather than in the body? Visible metadata is preferable to invisible metadata.
The RDFa foaf:primaryTopic solution looks best with my SemWeb hat on.
On 26 February 2014 18:50, Tom Morris tom@tommorris.org wrote:
Why would you put metadata in the head rather than in the body? Visible metadata is preferable to invisible metadata.
I'm not ruling out visible metadata in the body; but I'm interested to know what options are available for metaheaders in the document head, for instance for cases where changing the body content is not an option; or where the desire is to provide information to parsers which only retrieve the head, or only do so initially.
my 2c: I trust your judgement, so to the last two queries: No and Yes respectively.
2014-02-26 14:20 GMT+01:00, Andy Mabbett andy@pigsonthewing.org.uk:
Suppose I publish a web page about a notable person, building or other entity; and that the subject has a Wikidata entry.
What's the best meta header, to assert that the page is about the same subject as the Wikidata entry?
I'm thinking of something like:
<link rel="foo" href="https://www.wikidata.org/wiki/Q42">
or
<meta name="DC.bar" content="https://www.wikidata.org/wiki/Q42">
but what values of foo or bar?
Given the likely ubiquity of Wikidata in the near future, should we mint:
<link rel="wikidata"
or a more generic:
<link rel="datasource" ?
Are there any such headers already in the wild? Should Wikipedia articles and pages on sister projects include such headers?
-- Andy Mabbett @pigsonthewing http://pigsonthewing.org.uk
Wikidata-l mailing list Wikidata-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikidata-l
On 26 February 2014 13:20, Andy Mabbett andy@pigsonthewing.org.uk wrote:
What's the best meta header, to assert that the page is about the same subject as the Wikidata entry?
It additionally occurs to me that if a web page has a meta header (or indeed on-page visible metadata) asserting that the topic of the page is the same as the subject of a Wikidata entry; and the Wikidata page lists that page as the, or an, official page of or about the subject, then we have round-trip verification, similar to the "rel-me" attribute in microformats.