Re: The new charter is now in place

Thanks Gregg for articulating what I was also thinking concerning what a “CBOR-LD” would represent.

Leonard

From: Gregg Kellogg <gregg@greggkellogg.net>
Date: Sunday, August 16, 2020 at 5:50 PM
To: Leonard Rosenthol <lrosenth@adobe.com>
Cc: Manu Sporny <msporny@digitalbazaar.com>, "public-json-ld-wg@w3.org" <public-json-ld-wg@w3.org>
Subject: Re: The new charter is now in place

While I would like to see the group come up with an official CBOR-LD spec, I think it’s focus should be closer to what we already have [1]. It should mostly concern itself with transforming between CBOR and our Internal representation [2]. It should also likely deal with intermixing CBOR-LD and JSON-LD resources, so that a JSON-LD context might be used in a CBOR-LD document and visa-versa.

Beyond interoperability, considerations for compaction and any other processing steps to improve the compression factor of the resulting CBOR along with the potential for additional primitive types (e.g. base64Binary or Date/Time) would be useful. Manu’s proposal speaks towards optimizing the encoding of a CBOR-LD document, which is not, strictly-speaking, an interoperability issue, but speaks to the core motivation behind using such a format, in the fist place. Storage efficiency could be considered a normative requirement of such a spec.

The chief basic concept behind Manu’s proposal is to leverage the external context with the representation of a document making use of that context. External contexts do change, and this could suffer from the same issues discussed in various JSON-LD issues [3]. Perhaps a core aspect of this is that it can only be used with some form of SRI or other scheme where the URL uniquely identifies a particular version of a context (e.g., Hashlink), which may be just fine for the given use cases, but is definitely a concern that narrows the focus of a broader CBOR-LD encoding.

Both the CG and the newly re-commissioned JSON-LD Maintenance WG are in some summer doldrums right now, but hopefully we can come out of this soon to start disucssions on this, and other important post-Rec discussions.

Gregg Kellogg
gregg@greggkellogg.net<mailto:gregg@greggkellogg.net>

[1] https://w3c.github.io/json-ld-cbor/<https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fw3c.github.io%2Fjson-ld-bp%2F&data=02%7C01%7Clrosenth%40adobe.com%7C11402df8918b4e94876308d8422e6c32%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637332114435818548&sdata=G799AjOIWchqMUNXA3Y0IT%2FWyddUdClAi%2FZj%2BugrI0M%3D&reserved=0>
[2] https://www.w3.org/TR/json-ld11-api/#dfn-internal-representation<https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.w3.org%2FTR%2Fjson-ld11-api%2F%23dfn-internal-representation&data=02%7C01%7Clrosenth%40adobe.com%7C11402df8918b4e94876308d8422e6c32%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637332114435823526&sdata=ihKRXkH%2FP0ezX2Md%2BsJZIqO1lcWwh1dqF6qfcq56g7E%3D&reserved=0>
[3] https://github.com/w3c/json-ld-syntax/issues?q=is%3Aissue+hash<https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fw3c%2Fjson-ld-syntax%2Fissues%3Fq%3Dis%3Aissue%2Bhash&data=02%7C01%7Clrosenth%40adobe.com%7C11402df8918b4e94876308d8422e6c32%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637332114435823526&sdata=btsRSw1pcfyD6u4pB8Dmz2UfI9qBMl42Kes7ggXJiFM%3D&reserved=0>



On Aug 16, 2020, at 6:52 AM, Leonard Rosenthol <lrosenth@adobe.com<mailto:lrosenth@adobe.com>> wrote:

I would support the creation of a CBOR-LD, Manu, but not what you are have been proposing as such.

I think that your work is better defined as a compact serialization of specialized data types in CBOR - which is a worthwhile project.   But that is quite different from working on the generalized expression of linked data in CBOR.

Leonard

On 8/12/20, 11:41 AM, "Manu Sporny" <msporny@digitalbazaar.com<mailto:msporny@digitalbazaar.com>> wrote:

   On 8/12/20 11:30 AM, Ivan Herman wrote:

The new charter has been officially announced[1], so we are now
officially a maintenance group.

   Now that we're a Maintenance Group, would there be any interest in
   publishing a NOTE on CBOR-LD?

   https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdocs.google.com%2Fpresentation%2Fd%2F1ksh-gUdjJJwDpdleasvs9aRXEmeRvqhkVWqeitx5ZAE%2Fedit&amp;data=02%7C01%7Clrosenth%40adobe.com%7Ce9f7b87086d54f1938fe08d83ed62830%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637328436805309050&amp;sdata=NOQiMYXz0oiIwZbInGpbm3QR4vMGBh9xcNagcj10v30%3D&amp;reserved=0<https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdocs.google.com%2Fpresentation%2Fd%2F1ksh-gUdjJJwDpdleasvs9aRXEmeRvqhkVWqeitx5ZAE%2Fedit&data=02%7C01%7Clrosenth%40adobe.com%7C11402df8918b4e94876308d8422e6c32%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637332114435828504&sdata=0pj5iGD%2FvTnMo41LZc%2FO9b2t3EibwrsZxVD5blgnLw8%3D&reserved=0>

   The spec would need some major work, but trying to find a home for it first:

   https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdigitalbazaar.github.io%2Fcbor-ld-spec%2F&amp;data=02%7C01%7Clrosenth%40adobe.com%7Ce9f7b87086d54f1938fe08d83ed62830%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637328436805309050&amp;sdata=4GEJVUDJUdWgRZChlqKyXax99qWFalX4v5Y0dqX6H8s%3D&amp;reserved=0<https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdigitalbazaar.github.io%2Fcbor-ld-spec%2F&data=02%7C01%7Clrosenth%40adobe.com%7C11402df8918b4e94876308d8422e6c32%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637332114435833482&sdata=sP0bOD1fD84sVvBT4ggliKSuAkj%2FKO7NAukmtOTgbFM%3D&reserved=0>

   I note that this could fit under "Other Deliverables" per the recently
   approved Charter:

   """
   2.2 Other Deliverables
   ...
    * JSON-LD 1.1 specified in other serializations like YAML or CBOR.
   ...
   """

   -- manu

   --
   Manu Sporny - https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.linkedin.com%2Fin%2Fmanusporny%2F&amp;data=02%7C01%7Clrosenth%40adobe.com%7Ce9f7b87086d54f1938fe08d83ed62830%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637328436805309050&amp;sdata=9PZgLv%2F8bhJGtOEhkgTqqMU1nzqMcKf6rk0eN4I%2Flmk%3D&amp;reserved=0<https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.linkedin.com%2Fin%2Fmanusporny%2F&data=02%7C01%7Clrosenth%40adobe.com%7C11402df8918b4e94876308d8422e6c32%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637332114435838462&sdata=XuE9h9lFPfd0nxTc875hZonspA6ZD4%2BhmH%2FXXE%2Fey1A%3D&reserved=0>
   Founder/CEO - Digital Bazaar, Inc.
   blog: Veres One Decentralized Identifier Blockchain Launches
   https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Ftinyurl.com%2Fveres-one-launches&amp;data=02%7C01%7Clrosenth%40adobe.com%7Ce9f7b87086d54f1938fe08d83ed62830%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637328436805309050&amp;sdata=qj7oVKNGOQPv3TpIqQzF9z9o8SDv8BG91ROFJBxt2W4%3D&amp;reserved=0<https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Ftinyurl.com%2Fveres-one-launches&data=02%7C01%7Clrosenth%40adobe.com%7C11402df8918b4e94876308d8422e6c32%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637332114435843438&sdata=GhT%2F9hPGfK5oyiS6aEgio%2BueGfrvZZc6Dgl%2FuPYRx3Q%3D&reserved=0>