{"id":22,"date":"2019-04-05T13:39:52","date_gmt":"2019-04-05T13:39:52","guid":{"rendered":"https:\/\/www.w3.org\/community\/credibility\/?p=22"},"modified":"2019-04-05T13:40:49","modified_gmt":"2019-04-05T13:40:49","slug":"22","status":"publish","type":"post","link":"https:\/\/www.w3.org\/community\/credibility\/2019\/04\/05\/22\/","title":{"rendered":"Plans and Priorities for 2019"},"content":{"rendered":"\n

A quick update on where things are with Credibility at W3C. If you\u2019re interested, please join the group (if you haven’t) then answer this survey<\/a> on how you\u2019d like to be involved. Newcomers are welcome, not just folks who were involved last year, and please help spread the word.<\/p>\n\n\n\n

Things in the works for 2019:<\/p>\n\n\n\n

  1. Evolve Credibility Signals<\/a> into more of an open directory\/database of credibility signal definitions, with filtering and data about adoption and research for each signal, when available.<\/li>
  2. Document best practices for exchanging credibility data. Primarily technical (json-ld, csv), but also legal and commercial aspects.<\/li>
  3. Revise our draft report<\/a> on credibility tech, maybe splitting it up into chunks people are more likely to read, and with different section editors.<\/li>
  4. Have some general meetings, with presentations, to discuss various credibility-tech topics. This might include some of the signal provider companies or credibility tool projects.<\/li>
  5. Document how credibility issues fit into larger Online Safety issues. I\u2019d like a more specific and concrete handle on \u201cFirst, Do No Harm\u201d<\/a>.<\/li>
  6. Prototype a browser API which would support a market of credibility assessment modules, working together to protect the user in the browser. (See mockup<\/a>.)<\/li><\/ol>\n\n\n\n

    If you’re up for working on any of these topics, please fill in the survey<\/a>. We\u2019ll use that to help with meeting scheduling and general planning.<\/p>\n\n\n\n

    And of course, if you think the group should work on something not listed above, please reply on or off-list.<\/p>\n\n\n\n

    Thanks!<\/p>\n\n\n\n

    <\/p>\n","protected":false},"excerpt":{"rendered":"

    A quick update on where things are with Credibility at W3C. If you\u2019re interested, please join the group (if you haven’t) then answer this survey on how you\u2019d like to be involved. Newcomers are welcome, not just folks who were … Continue reading →<\/span><\/a><\/p>\n","protected":false},"author":3127,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_s2mail":"","footnotes":""},"categories":[1],"tags":[],"class_list":["post-22","post","type-post","status-publish","format-standard","hentry","category-uncategorized"],"_links":{"self":[{"href":"https:\/\/www.w3.org\/community\/credibility\/wp-json\/wp\/v2\/posts\/22","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.w3.org\/community\/credibility\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.w3.org\/community\/credibility\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.w3.org\/community\/credibility\/wp-json\/wp\/v2\/users\/3127"}],"replies":[{"embeddable":true,"href":"https:\/\/www.w3.org\/community\/credibility\/wp-json\/wp\/v2\/comments?post=22"}],"version-history":[{"count":3,"href":"https:\/\/www.w3.org\/community\/credibility\/wp-json\/wp\/v2\/posts\/22\/revisions"}],"predecessor-version":[{"id":25,"href":"https:\/\/www.w3.org\/community\/credibility\/wp-json\/wp\/v2\/posts\/22\/revisions\/25"}],"wp:attachment":[{"href":"https:\/\/www.w3.org\/community\/credibility\/wp-json\/wp\/v2\/media?parent=22"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.w3.org\/community\/credibility\/wp-json\/wp\/v2\/categories?post=22"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.w3.org\/community\/credibility\/wp-json\/wp\/v2\/tags?post=22"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}