Re: RDF/CBOR: A CBOR-based Serialization of RDF

On Wed, 21 Sep 2022 at 13:13, pukkamustard <pukkamustard@posteo.net> wrote:

>
> Gregg Kellogg <gregg@greggkellogg.net> writes:
>
> > Have you looked at CBOR-LD [1]? Basically, JSON-LD encoded as CBOR,
> > but with some space optimizations. The JSON-LD CG is considering
> > pushing something forward on this, as it has a lot in common with
> > current work on YAML-LD [2].
>
> I have and have noted it in the specification of RDF/CBOR.
>
> The major reason for not using JSON-LD/CBOR-LD is the reliance on
> external contexts. I understand that it might be possible to define a
> restricted subset of JSON-LD/CBOR-LD that does not use remote contexts
> and admits a canonical form. However, the complexity of JSON-LD plus the
> definition of restrictions does not seem very appealing to me.


+1 to avoiding external contexts wherever possible!

Dan

p.s. “ An important requirement on the metadata framework is that parsers
must be able to produce a parse tree of the metadata without the assistance
of an auxiliary format description” - Ralph Swick in
https://www.w3.org/Submission/1997/8/Comment.html reviewing
https://www.w3.org/TR/NOTE-MCF-XML-970606



>
> Best regards,
> pukkamustard
>
> >
> > Gregg Kellogg
> > gregg@greggkellogg.net
> >
> > [1] https://digitalbazaar.github.io/cbor-ld-spec/
> > [2] https://json-ld.github.io/yaml-ld/spec/
> >
> >  On Sep 18, 2022, at 12:30 PM, pukkamustard <pukkamustard@posteo.net>
> wrote:
> >
> >  Hello semantic-web,
> >
> >  I'd like to share some recent work towards a binary serialization of RDF
> >  using CBOR:
> >
> >  https://openengiadina.codeberg.page/rdf-cbor/
> >
> >  CBOR (RFC 8949) is a binary data serialization that provides basic data
> >  types (string, integer, arrays, etc.) as well as extendable tags for
> >  annotating more complex data types. RDF/CBOR encodes RDF into CBOR
> >  types. CBOR types are re-used for efficient binary serialization of
> >  literal values and certain binary IRIs (e.g. UUIDs).
> >
> >  RDF/CBOR is very much inspired by the HDT serialization and uses a very
> >  similar encoding (front-coded dictionaries and BitMapTriples). Unlike
> >  HDT, RDF/CBOR is optimized for small pieces of content that are created,
> >  transported and read by possibly constrained devices.
> >
> >  The serialization is defined using the Concise Data Definition Language
> >  (CDDL; RFC 8610) which allows a very concise and precise specification.
> >
> >  RDF/CBOR also allows groups of RDF statements to be content-addressed,
> >  i.e. identifiers are the cryptographic hash of the serialized
> >  statements. This can be used for cryptographic signature schemes and
> >  makes RDF viable on distributed, peer-to-peer systems.
> >
> >  I look forward to your feedback and comments.
> >
> >  Best regards,
> >  pukkamustard
>
>
>