Re: RDF Canonicalization is a Rec

út 21. 5. 2024 v 12:48 odesílatel Phil Archer <phil.archer@gs1.org> napsal:

> Creating standards is never quick. Nor should it be. It takes time to
> reach consensus that something needs to be standardized, to ensure that
> there is a community that wants it and will implement it. Then you actually
> create the standard itself and prove it works. In this case, that initial
> phase took a long time. The need for an RDF Canonicalization algorithm was
> discussed back at the start of the Sem Web but there wasn't the consensus
> that it was needed or that there was a best way to do it. Once that need
> was agreed the work kicked off in September 2022 and now, less than 2 years
> later, RDFC is a W3C Recommendation. See
> https://www.w3.org/news/2024/rdf-dataset-canonicalization-is-a-w3c-recommendation/
>
> If you have an RDF graph and you want a canonical representation of it,
> for whatever reason, there's now a W3C Rec for that, along with a test
> suite and implementation reports.
>
> Thanks are due to many people who have thought about this over the years
> including Jeremy Carrol and Aidan Hogan.  For the production of the Rec
> itself, thanks go especially to Dave Longley, David Lehn and Manu Sporny at
> Digital Bazaar; Gregg Kellogg as lead editor supported by Dave Longley and
> Dan Yamamoto. Active WG members include Sebastian Crane, Ted Thibodeau and
> Kazue Sako. Markus Sabadello and I had the privilege of working together as
> co-chairs with W3C staff Pierre-Antoine Champin and Ivan Herman.
>
> Thanks everyone!
>

Congrats!

Does it support RDF 1.2 out of the box?


>
> Phil
>
>
> ---
>
> Phil Archer
> Web Solutions Director, GS1
> https://www.gs1.org
>
> https://philarcher.org
> +44 (0)7887 767755
> @philarcher1
>
> CONFIDENTIALITY / DISCLAIMER: The contents of this e-mail are
> confidential and are not to be regarded as a contractual offer or
> acceptance from GS1 (registered in Belgium).
> If you are not the addressee, or if this has been copied or sent to you in
> error, you must not use data herein for any purpose, you must delete it,
> and should inform the sender.
> GS1 disclaims liability for accuracy or completeness, and opinions
> expressed are those of the author alone.
> GS1 may monitor communications.
> Third party rights acknowledged.
> (c) 2020.
>
>
>