ietf
[Top] [All Lists]

Re: [art] Artart last call review of draft-ietf-core-links-json-07

2017-04-25 07:50:57
On Tue, Apr 25, 2017 at 2:35 PM, Erik Wilde 
<erik(_dot_)wilde(_at_)dret(_dot_)net> wrote:

hello carsten.

On 2017-04-24 14:55, Carsten Bormann wrote:

it would be better to make sure that serializations of web links actually
can represent web links and not just some of the information that they
convey. that train may have left the station with RFC 6690, but maybe for
the JSON and CBOR serializations that can be changed.

Right.  Can you be more specific what you would want to see here?


two possibilities:

- to do things well it would be better to have web link serializations
that cover *all* of RFC 5988 (bis). that's a hard thing to do and will take
a while.


As Erik previously indicated, it would be great if this could be done as
part of RFC5988bis.


- for the RFC 6690-based variants under consideration right now, it would
be helpful to very explicitly point out that they are *not* general-purpose
serializations of web links, but instead inherit the limitations of the
underlying spec.


That would, indeed, be good. But, in case RFC5988bis would spec a (JSON)
serialization, it seems to me that it would be rather helpful for the CORE
community if the RFC 6690 JSON serialization would be based on it.

Cheers

herbert




cheers,

dret.

--
erik wilde | mailto:erik(_dot_)wilde(_at_)dret(_dot_)net |
           | http://dret.net/netdret    |
           | http://twitter.com/dret    |




-- 
Herbert Van de Sompel
Digital Library Research & Prototyping
Los Alamos National Laboratory, Research Library
http://public.lanl.gov/herbertv/
http://orcid.org/0000-0002-0715-6126

==