LD client responsibilities

Hi,

The (in)famous Four Practices of LD conspicuously omit mention of
client side responsibilities.  One might argue that this is fine since
the D in LD stands for "Data".  But that can't be right, since the
third practice essentially says "make sure your server, serves".
Since the concept of LD really only makes sense as a kind of
ecosystem, it seems appropriate to say something about what clients
ought to do in order to count as playing nice in the LD world.

Would it make sense to add a fifth practice along the lines of "if in
the response to an HTTP IRI lookup you receive data containing IRIs,
make them appropriately discoverable and actionable."  Maybe add "for
the user or other client."  "Appropriately" being a necessary hedge,
since we cannot provide a global definition of "actionable" that will
work in every case.

Something like this seems especially appropriate for JSON-LD given its
likely uses.

Gregg

Received on Friday, 14 June 2013 14:05:20 UTC