Re: Event Updated: RDF Canonicalization and Hash Working Group

Hi Gregg,

all this worries me. I do not want to find the RCH work suspended unnecessarily on this issue, which is not really ours. As you say, the details of the nquads canonicalization doe not affect the algorithm, and the goal of this WG is to standardize that one and nothing else.

The reason this is the problem because, if we are not careful, we may find ourselves hooked on the CR phase unnecessarily. Any change on the nquads canonicalization will have to spread to various RDF frameworks/libraries out there, and that will take some time. On the other hand, the implementation of URDNA usually relies on such general frameworks. I do not want to find ourselves in a state whereby the URDNA implementer would have to re-implement the nquads serialization along the line of the new RDF specification to pass all the tests.

What I would propose this WG could do is to look at all the tests which could be affected by any of those proposed changes and either remove them or make them optional tests. These tests would not affect or main goal of the CR testing, namely to prove that the URDNA algorithm, and its textual specification, is correct and interoperable (which is the real goal of the CR phase); as a consequence, these tests should not stand in a way of passing to Proposed Rec when the time comes.

I realize that the RDF changes may and will affect the URDNA deployment as well, and that also worries me. But our first obligation is to correctly finalize the standard URDNA specification...

Ivan

----
Ivan Herman, W3C
Home: http://www.w3.org/People/Ivan/
mobile: +33 6 52 46 00 43
ORCID ID: https://orcid.org/0000-0003-0782-2704
On 1 Mar 2023 at 00:13 +0100, Gregg Kellogg <gregg@greggkellogg.net>, wrote:
> We might want to sped a little time on N-Quads Canonicalization. There’s an open pull request in the N-Quads repo [1] that’s facing some short-term hurdles due to questions of procedure and RDF-star WG charter. There is also an issue on reconsidering how characters are escaped [2], which would affect existing test results, particularly if simple literals are always serialized with the xsd:string datatype. While they don’t affect the canonicalization algorithm, they may affect the hashes produced for quads containing literals. The RDF-star WG will need some feedback from the RCH WG, and whatever is needed to clear any charter issues. (Note, it is an open erratum against N-Quads [3][4], which is in scope, but the extent of changes to be considered needs clarification).
>
> Gregg Kellogg
> gregg@greggkellogg.net
>
> [1] https://github.com/w3c/rdf-n-quads/pull/17
> [2] https://github.com/w3c/rdf-n-quads/issues/16
> [3] https://www.w3.org/2001/sw/wiki/RDF1.1_Errata#erratum_32
> [4] https://www.w3.org/2001/sw/wiki/RDF1.1_Errata#erratum_33
>
> > On Feb 21, 2023, at 2:21 AM, Phil Archer (W3C Calendar) <noreply+calendar@w3.org> wrote:
> >
> > View this event in your browser
> > RDF Canonicalization and Hash Working Group Upcoming Confirmed
> > 01 March 2023, 10:00 -10:55 America/New_York
> > Event is recurring every other week on Wednesday, starting from 2023-02-01, until 2024-07-17
> > RDF Dataset Canonicalization and Hash Working Group
> > Bi-weekly meeting of the RCH group, back after a short break.
> >
> > Agenda
> >
> > 1. Scribe list (most recent first) Gregg, pchampin, DLongley, Ahmad, PhilA, AndyS, Manu)
> > 2. New introductions
> > 3. Round the room including any comments from VCWG F2F in Miami
> > 4. Canon Issue 4 (What is the output)
> > 5. Hash Issue 2
> > 6. Issue bashing
> >
> >
> > Joining Instructions
> > Instructions are restricted to meeting participants. You need to log in to see them.
> >
> > Participants
> > Organizers
> >
> > • Phil Archer
> > • Markus Sabadello
> >
> > Groups
> >
> > • RDF Dataset Canonicalization and Hash Working Group (View Calendar)
> >
> > Report feedback and issues on GitHub.
> > <event.ics>
>