search

w3c / rch-wg-charter

Charter proposal for an “RDF Dataset Canonicalization and Hash Working Group”
https://w3c.github.io/rch-wg-charter/
Other
12 stars 7 forks source link

Added an out-of-scope section to the explainer #82

Closed iherman closed 3 years ago

iherman commented 3 years ago

Making the out-of-scope part in the charter is, editorially, probably not feasible.

The section was inspired by the mail of @danbri, although shortened significantly.

Preview | Diff

danbri commented 3 years ago

Looks good to me

iherman commented 3 years ago

@pchampin, good point. I have added a remark to the end of the first paragraph. It now reads as:

These are all but a few examples where the complexities around the usage of Linked Data/RDF are real, and may affect the usage patterns of signed RDF content and what the social meaning on those signatures are.

The next paragraph starts by saying that all those are out-of-scope:-)

iherman commented 3 years ago

Merging to make further discussions easier and avoiding merge hells. The addition is an incremental addition to what was there, ie, further improvement (if necessary) can be done without problems.

kdenhartog commented 3 years ago

I'm not sure I understand the implications of this well enough to agree or disagree with this. One of the footguns we've commonly encountered is that due to the nature of the contexts resolvability and contents properties within the JSON-LD may be getting dropped during the signature or verification process. Is the intent of this statement to place that work out of scope?

iherman commented 3 years ago

If I understand well your question, probably neither yes or no, but more closely to 'yes', ie, it may be out of scope indeed.

The specs are all defined on the abstract data type level, ie, on the RDF graph/dataset side. The specs also define a vocabulary to express the results. The specs are not aimed to make any normative statement on the specific serializations, and JSON-LD is but one of these. I would expect the documents (or additional notes) may address these types of issues, too, but not as part of the normative sections. The "out-of-scope" sections in the charter (or, in this case, the explainer document) concentrate on the normative parts of the future specifications.

Does this help?

kdenhartog commented 3 years ago

Yeah, thanks for the response. I found the issue which precipitated this PR (#83) , so I've moved the discussion over there.