{"action":"created","issue":{"url":"https://api.github.com/repos/schemaorg/schemaorg/issues/1688","repository_url":"https://api.github.com/repos/schemaorg/schemaorg","labels_url":"https://api.github.com/repos/schemaorg/schemaorg/issues/1688/labels{/name}","comments_url":"https://api.github.com/repos/schemaorg/schemaorg/issues/1688/comments","events_url":"https://api.github.com/repos/schemaorg/schemaorg/issues/1688/events","html_url":"https://github.com/schemaorg/schemaorg/issues/1688","id":241796849,"number":1688,"title":"TP-inspired News-related improvements phase 2","user":{"login":"danbri","id":170265,"avatar_url":"https://avatars0.githubusercontent.com/u/170265?v=4","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,"assignees":[],"milestone":null,"comments":35,"created_at":"2017-07-10T18:02:39Z","updated_at":"2017-11-30T22:48:45Z","closed_at":null,"author_association":"CONTRIBUTOR","body":"Relaying from a conversation with Sally and Subbu from the TrustProject.\r\n\r\nWe looked over their efforts around author/producer info for per-article pages. It seems the majority can be described using existing schema.org, but there are a couple of areas where additional improvements would help.\r\n\r\n1. Language(s) that an article author speaks / has competency in.\r\n\r\nDesire here is for a fairly simple characterization of basic language ability, e.g. some journalist knows enough to talk to someone or read/write, but not a strong need to distinguish reading-vs-writing-vs-speaking, nor \"wants to learn\" vs \"is learning\" vs \"solid\" vs \"expert\" vs \"native speaker\", etc.\r\n\r\nExpectation is that a property would take language codes (as strings or Language objects, along lines of http://schema.org/inLanguage which says \"Please use one of the language codes from the IETF BCP 47 standard.\"). Perhaps in future as educational/learning metadata for competencies and skills grows, we might go deeper --- either language specific or more generally.\r\n\r\n2. Expertise\r\n\r\nThere is a desire to characterize the special expertise of an author, implicitly focussing on the expertise that is most pertinent either to the article at hand or the publishing site / organization.\r\n\r\n* We noted that the Text-valued \"skills\" property already existed for JobPosting, and could be generalized.\r\n* We noted that expertise in a topic is subtly but importantly different from skill in it, examples might include neuroscience, nanotechnology, and foreign policy. We can't plausibly recycle \"skills\" to mean \"expertise\".\r\n* We noted that unique ID concept codes for such things are attractive in general (e.g. for jobs etc.) but are unlikely to be commonly used in journalistic settings.\r\n* We suggest adding \"expertise\" and having both it and a tweaked \"skills\" property also accept the http://schema.org/Specialty (which is currently and perhaps incorrectly listed as an Enumeration). \r\n* We noted a particular use case for indicating local expertise, for example some author might be a \"Person\" with \"expertise\" which is a \"Specialty\" which has an association with a \"Place\" e.g. Tampa Florida (e.g. sameAs of https://www.wikidata.org/wiki/Q1059534). \r\n  * We suggest \"about\" might be a reasonable name to associate the specialty to the place, but that this construction might be a bit over-ambitious. \r\n"},"comment":{"url":"https://api.github.com/repos/schemaorg/schemaorg/issues/comments/348346320","html_url":"https://github.com/schemaorg/schemaorg/issues/1688#issuecomment-348346320","issue_url":"https://api.github.com/repos/schemaorg/schemaorg/issues/1688","id":348346320,"user":{"login":"subbuvincent","id":16565842,"avatar_url":"https://avatars3.githubusercontent.com/u/16565842?v=4","gravatar_id":"","url":"https://api.github.com/users/subbuvincent","html_url":"https://github.com/subbuvincent","followers_url":"https://api.github.com/users/subbuvincent/followers","following_url":"https://api.github.com/users/subbuvincent/following{/other_user}","gists_url":"https://api.github.com/users/subbuvincent/gists{/gist_id}","starred_url":"https://api.github.com/users/subbuvincent/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/subbuvincent/subscriptions","organizations_url":"https://api.github.com/users/subbuvincent/orgs","repos_url":"https://api.github.com/users/subbuvincent/repos","events_url":"https://api.github.com/users/subbuvincent/events{/privacy}","received_events_url":"https://api.github.com/users/subbuvincent/received_events","type":"User","site_admin":false},"created_at":"2017-11-30T22:48:44Z","updated_at":"2017-11-30T22:48:44Z","author_association":"NONE","body":"I reviewed [PublicationEvent](http://schema.org/PublicationEvent). The fundamental assumption that seems to be baked into the schema is that it is for real/physical events or release of titles/albums etc. For e.g. startDate, endDate, doorTime, etc are all time-related properties that allow use in event-like scenarios. \r\n\r\nWe could add an eventType property to PublicationEvent to allow for set types like 'Correction' and then use the inherited 'description' from 'Thing' to layout the text. \r\n\r\nHowever a 'date' needs to be captured. It will become a hack to try to use startDate or endDate. If we create another property called date under [Date](http://schema.org/Date) \r\n\r\nWe could also look at [Thing > Action > UpdateAction ](http://schema.org/UpdateAction). \r\n\r\nSince corrections are actions taken on articles, we could have a subtype of Action called CorrectionAction, mapped to a property of CreativeWork perhaps (new) called 'correction'. And then use 'description' of 'CorrectionAction' for the text. And we will need a way to signal the date. \r\n\r\nHere is a real BBC news article where I have attempted to show an array of two corrections. \r\n`\r\n<script type=\"application/ld+json\">\r\n{\"@context\":\"http:\\/\\/schema.org\",\r\n\r\n\t\"@type\":\"ReportageNewsArticle\",\r\n\t\"url\":\"http:\\/\\/www.bbc.com\\/news\\/world-us-canada-42160971\",\r\n\t\"publisher\": {\r\n\t\t\"@type\":\"NewsMediaOrganization\",\r\n\t\t\"name\":\"BBC News\",\r\n\t\t\"publishingPrinciples\":\"http:\\/\\/www.bbc.co.uk\\/news\\/help-41670342\",\r\n\t\t\"logo\":{\"@type\":\"ImageObject\",\"url\":\"http:\\/\\/www.bbc.co.uk\\/news\\/special\\/2015\\/newsspec_10857\\/bbc_news_logo.png?cb=1\"}\r\n\t},\r\n\r\n\t\"datePublished\":\"2017-11-29T22:44:09+00:00\",\r\n\t\"dateModified\":\"2017-11-29T22:44:09+00:00\",\r\n\t\"headline\":\"Has the US forgotten about World War One?\",\r\n\r\n\t\"image\":{\"@type\":\"ImageObject\",\"width\":720,\"height\":405,\"url\":\"https:\\/\\/ichef.bbci.co.uk\\/news\\/720\\/cpsprodpb\\/126F5\\/production\\/_98990557_171003renderposes.jpg\"},\r\n\t\"thumbnailUrl\":\"https:\\/\\/ichef-1.bbci.co.uk\\/news\\/208\\/cpsprodpb\\/126F5\\/production\\/_98990557_171003renderposes.jpg\",\r\n\r\n\t\"author\":{\"@type\":\"Person\",\"name\":\"Jane O'Brien\"},\r\n\t\"mainEntityOfPage\":\"http:\\/\\/www.bbc.com\\/news\\/world-us-canada-42160971\"}\r\n \r\n        \t“**correction**”: [ \r\n\t\t       {“@type”:”**CorrectionAction**”,\r\n\t\t\t“description”: “An earlier version of this article misstated the circumstances surrounding the departure of David Drummond, a top Alphabet executive, from Uber’s board. He resigned but was not asked to leave.”,\r\n \t\t\t“**dateCorrected**” : “<Date>”\r\n \t\t\t},\r\n\r\n\t\t\t{“@type”:”**CorrectionAction**”,\r\n\t\t\t“description”: “A previous version of this story conflated information about willingness to take a pay cut and the amount willing to be taken.”,\r\n \t\t\t“**dateCorrected**” : “<Date>”\r\n \t\t\t}\r\n\t\t       ]\r\n</script>\r\n  `\r\n(The properties that are mocked here are in bold) \r\n..."}}
{"actor":{"display_login":"subbuvincent"}}