{"action":"created","issue":{"url":"https://api.github.com/repos/schemaorg/schemaorg/issues/1186","repository_url":"https://api.github.com/repos/schemaorg/schemaorg","labels_url":"https://api.github.com/repos/schemaorg/schemaorg/issues/1186/labels{/name}","comments_url":"https://api.github.com/repos/schemaorg/schemaorg/issues/1186/comments","events_url":"https://api.github.com/repos/schemaorg/schemaorg/issues/1186/events","html_url":"https://github.com/schemaorg/schemaorg/issues/1186","id":157070129,"number":1186,"title":"Show how to use Wikidata terms, \"schema.org\"-style, particularly in JSON-LD","user":{"login":"danbri","id":170265,"avatar_url":"https://avatars.githubusercontent.com/u/170265?v=3","gravatar_id":"","url":"https://api.github.com/users/danbri","html_url":"https://github.com/danbri","followers_url":"https://api.github.com/users/danbri/followers","following_url":"https://api.github.com/users/danbri/following{/other_user}","gists_url":"https://api.github.com/users/danbri/gists{/gist_id}","starred_url":"https://api.github.com/users/danbri/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/danbri/subscriptions","organizations_url":"https://api.github.com/users/danbri/orgs","repos_url":"https://api.github.com/users/danbri/repos","events_url":"https://api.github.com/users/danbri/events{/privacy}","received_events_url":"https://api.github.com/users/danbri/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":2,"created_at":"2016-05-26T20:19:38Z","updated_at":"2016-05-26T20:58:22Z","closed_at":null,"body":"This builds on earlier exploration in #280 (mappings). Mappings will be needed. @vrandezo + @danbri collaboration notes live here now.\r\n\r\nGoal: we want to be able to write JSON-LD (or RDFa/Microdata) that draws upon Wikidata content. Specifically, properties, types and identified entities. This could be standalone markup or mixed in with schema.org and other vocabularies.\r\n\r\n* *Properties*: Wikidata has first class / built-in support for properties (these get P-identifiers e.g. see https://www.wikidata.org/wiki/Property:P1082 for 'population').\r\n* *Types*: These exist somewhat implicitly in Wikidata content but less so in the infrastructure (like hashtags and RTs in early Twitter). Types show up with P31 (instanceOf) and P279 (subClassOf) in Wikidata; these correspond roughly to rdf:type and rdfs:subClassOf in RDF (RDFa/JSON). For example https://www.wikidata.org/wiki/Q128207 (Earth) is instanceOf (P31) https://www.wikidata.org/wiki/Q128207 (Terrestrial Planet)\r\n* *Entities*: For example, https://www.wikidata.org/wiki/Q42 (Douglas Adams) is instanceOf  https://www.wikidata.org/wiki/Q5 (Human). We should show how to use Wikidata unique identifiers for well known entities within schema.org-style markup, e.g. using schema.org sameAs (see #1162).\r\n\r\nIdeally we would like to exploit mappings so that Wikidata terminology can be mixed in with common schema.org terms like Person, Place, Event etc., supplying properties when schema.org and its other extensions have nothing. \r\n\r\nSubtasks:\r\n\r\n* collect mappings where possible #280 (optional but very useful)\r\n* for each Wikidata property, we need to know if it is a string-valued vs thing-valued property i.e. whether or not the datatype of the property is pointing to an item. This distinction is needed in JSON-LD @context definitions and used in parsing JSON-LD to determine how to treat textual values e.g. whether \"../news/\" gets expanded to a full URL.\r\n* Optionally (but useful for discovery / overview) it would be good to have a view of Wikidata in more RDF-ish (schema.org-ish) terms. Specifically as a hierarchy of types, properties and their associations.\r\n * @mkroetzsch  has apparently done this (Denny will dig links)\r\n * Note that Wikidata is even weaker than schema.org in terms of type/property associations; these need to be mined from instance data e.g. via query.wikidata.org\r\n* Generate a JSON-LD context file that can be used in JSON-LD parsing\r\n* Write JSON-LD examples showing \r\n  * JSON-LD properties from Wikidata mixed into schema.org\r\n* Generate at least single page HTML overview / report of the terms.\r\n\r\nThis assumes that we are treating Wikidata as a schema.org \"[external extension](schema.org/docs/extension.html)\". If instead we handled it as an hosted extension we would need to ensure no type or property names clashed with existing usage. This is infeasible unless we used Q-nnn and P-nnn identifiers, which are not very usable.\r\n\r\nThe actual final markup ought to allow for ugly but permanent IDs to be used, but also for the (current and former) human readable labels e.g. \"population\" to be used in markup. A larger, later problem is how these are documented and discovered but we assume existing tools could be adapted, and that data consumers will give examples that interest them. \r\n\r\nWorked example\r\n=============\r\n\r\nUsecase. The [Finder-Spyder](https://en.wikipedia.org/wiki/Finder-Spyder) wants to use schema.org people descriptions, but needs a blood type property. At this time schema.org doesn't have such a property. One option would be to propose this as a schema.org addition or extension and wait for it to be added to schema.org's Pending extension or fully ratified. However, Wikidata already has such a property: https://www.wikidata.org/wiki/Property:P1853 \r\n\r\nWe want to show how Wikidata's \"blood type\" property can be used in markup.\r\n\r\nThings to remember\r\n===============\r\n\r\nProperty names within Wikidata are constrained to be unique (per language); types are not.\r\n"},"comment":{"url":"https://api.github.com/repos/schemaorg/schemaorg/issues/comments/221992682","html_url":"https://github.com/schemaorg/schemaorg/issues/1186#issuecomment-221992682","issue_url":"https://api.github.com/repos/schemaorg/schemaorg/issues/1186","id":221992682,"user":{"login":"vrandezo","id":663648,"avatar_url":"https://avatars.githubusercontent.com/u/663648?v=3","gravatar_id":"","url":"https://api.github.com/users/vrandezo","html_url":"https://github.com/vrandezo","followers_url":"https://api.github.com/users/vrandezo/followers","following_url":"https://api.github.com/users/vrandezo/following{/other_user}","gists_url":"https://api.github.com/users/vrandezo/gists{/gist_id}","starred_url":"https://api.github.com/users/vrandezo/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/vrandezo/subscriptions","organizations_url":"https://api.github.com/users/vrandezo/orgs","repos_url":"https://api.github.com/users/vrandezo/repos","events_url":"https://api.github.com/users/vrandezo/events{/privacy}","received_events_url":"https://api.github.com/users/vrandezo/received_events","type":"User","site_admin":false},"created_at":"2016-05-26T20:58:22Z","updated_at":"2016-05-26T20:58:22Z","body":"Here's an example of the properties that @mkroetzsch calculated for a Wikidata-item which is used as a type:\r\nhttp://tools.wmflabs.org/sqid/#/view?id=Q5 (see the field \"properties for this type\")\r\n\r\nNote that this is not about the domain of the property, but rather which properties are typically used for a given type."}}
{"actor":{"display_login":"vrandezo"}}