Re: Web Identity 1.0 -- Draft Spec

On Fri, Jan 3, 2014 at 3:00 PM, Manu Sporny <msporny@digitalbazaar.com> wrote:
>> 2) SPARQL update or JSON PATCH for this kind of operation
>
> We did look at SPARQL, but requiring it was deemed to be overkill.
> Hardly any Web Developers know what SPARQL is and asking them to use
> that stack just so they can read/write identity information places a
> very high barrier to entry. We're trying to do all of this with just
> JSON-based tools and what you'd already get in a web browser.
>
> While you can argue that HTTP Signatures are very much above this bar,
> remember that the standard read/write functionality will be accessible
> to anyone with a web stack that supports HTTP POST and JSON.
>
>> 3) The Changeset vocab [1]
>>
>> [1] http://docs.api.talis.com/getting-started/changesets
>
> Overkill and no real standard for it. I think it would be more wise to
> try to use a minimal set of JSON Patch until it becomes clear that we
> need something more.
>

There are issues to consider when comparing SPARQL, Changeset vocab,
JSON Patch, or other systems for triple editing.  SPARQL and the
Changeset vocab will be able to edit linked data at a lower triples
level.  JSON Patch may require that data be framed into a strict
JSON-LD format so that the patch paths make sense.  That could require
finishing the framing spec.  If you can read and write the full
resource data then just HTTP verbs and a read-modify-write process
could work for edits.  I imagine editing data with blank nodes is full
of issues too.  And the ease of any approach probably depends on
implementation details of the client and server.  It could be a
challenge to come up with a good general solution.

-dave

Received on Wednesday, 8 January 2014 01:17:07 UTC