Re: Verifiable Text-based Claims

Dave,

Thank you for the comments.

If you get a minute, check out the recently updated pages:
https://w3c-ccg.github.io/verifiable-news/brainstorming.html

https://w3c-ccg.github.io/verifiable-news/sketchpad.html


I’m still working on the explanatory, clarifying text around the JSON source code examples.

As you indicated, the claim attribute is ordinarily as per: https://w3c.github.io/vc-data-model/#claims . I’m trying something new, to put an RDF literal or array of literals for the value of a “claim” attribute on a new overarching type, tentatively “Claim” or “LiteralClaim” (see “type”: ”Claim”). It could also be an attribute other than “claim”.

There are possibilities for graph-based approaches, however, including, but not limited to:


  1.
A property “says” which connects a subject to a statement, “Author says Statement”.
  2.
A property “contains”, “Article contains Statement”.

As you indicated, there are then some epistemological topics (“X says S”, “X contains S”, “S”) which pertain to the semantics and intention of asserting/publishing and revoking factual claims in a system.


Best regards,
Adam

P.S.: Also, the schema.org ClaimReview schema and a link about fact-checking:
http://schema.org/ClaimReview

https://developers.google.com/search/docs/data-types/factcheck


From: dlongley@digitalbazaar.com<mailto:dlongley@digitalbazaar.com>
Sent: ‎Wednesday‎, ‎September‎ ‎13‎, ‎2017 ‎3‎:‎39‎ ‎PM
To: Adam Sobieski<mailto:adamsobieski@hotmail.com>, public-credentials@w3.org<mailto:public-credentials@w3.org>

On 09/12/2017 05:13 PM, Adam Sobieski wrote:
> I’m exploring and sketching some ideas with regard to verifiable
> text-based claims.
>
> https://w3c-ccg.github.io/verifiable-news/sketchpad.html

>
> Questions, comments and suggestions welcomed.

I don't have a lot of time to review right now but I noticed that the
data modeling needs work -- `claim` should point at a node in the graph
with an identifier for the "thing" that the claim is about.

One approach could be for that node to include the ID (url) for the
article, some type information, and the content of the article. But
that's really just asserting that some things were said in an article.
Other approaches that have been considered focus on using schema.org
Reviews with links and timestamp/hash information on what was reviewed
and some "truthiness" measure. Hashes are tricky as the content may
change due to minor editorial updates.


--
Dave Longley
CTO
Digital Bazaar, Inc.
http://digitalbazaar.com