Re: [core] draft-bormann-core-links-json: call for adoption

[Bert Greevenbosch <[e-mail]>]

+1

Not sure if I agree with the fact that it is only suitable outside the constraint environment though; the JSON variant seems easy enough to parse. How to avoid IOP trouble due to two endpoints using the different formats?

Some things for consideration:
- Change ".well-known/core" to ".well-known/jlink" or something?
- Register new mime type?
- Does this allow multivalue attributes, e.g. through arrays? Definitely possible in JSON, but it would break easy conversion to the conventional link format.
- In JCARD, we started with a similar construction. However we later changed to a construction of {"name", "parameter", "type", "value"} to allow more flexibility and signalling, especially concerning the type (e.g. string or integer) of the value.

Bert


From: [e-mail] [mailto:[e-mail]] On Behalf Of Rahman, Akbar
Sent: 2013年5月21日 11:50
To: Andrew Mcgregor; [e-mail]
Subject: Re: [core] draft-bormann-core-links-json: call for adoption

+1

Akbar

From: [e-mail] [mailto:[e-mail]] On Behalf Of Andrew Mcgregor
Sent: Monday, May 20, 2013 8:28 PM
To: [e-mail]
Subject: [core] draft-bormann-core-links-json: call for adoption

Consensus of the room in Orlando was to adopt draft-bormann-core-links-json as a working group document.  This email is a call for confirmation of that consensus.  Please respond if you support the adoption of this document.

From the charter:

    5) A definition of how to use CoAP to advertise about or query for a
    Device's description. This description may include the device name and
    a list of its Resources, each with a URL, an interface description URI
    (pointing e.g. to a Web Application Description Language (WADL)
    document) and an optional name or identifier. The name taxonomy used
    for this description will be consistent with other IETF work,
    e.g. draft-cheshire-dnsext-dns-sd.

This is for making the resource discovery information available to backends.  On a technical level, this is a no-brainer.

* May 2013 Submission to IESG of "Representing CoRE Link Collections
  in JSON" for Proposed Standard

--
Andrew McGregor | SRE | [e-mail]<mailto:[e-mail]> | [phone]