Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Use cases #110

Closed
philarcher opened this issue Jun 7, 2023 · 4 comments
Closed

Use cases #110

philarcher opened this issue Jun 7, 2023 · 4 comments
Assignees
@philarcher
Labels
spec:editorial

Comments

@philarcher
Copy link
Contributor

The Explainer document provides a good basis for the WG's work. However, during the evolution of the c14n spec, we have recognized further features that need to be documented. Therefore, the use cases section of the spec can usefully be filled with a reference to the explainer doc plus some text around the features around output formats and mappings.
@philarcher philarcher added the Editorial Purely about the way the doc is written, not about the substantive content label Jun 7, 2023
@philarcher philarcher self-assigned this Jun 7, 2023
@philarcher philarcher added spec:editorial and removed Editorial Purely about the way the doc is written, not about the substantive content labels Jun 21, 2023
@philarcher
Copy link
Contributor Author

@gkellogg Are you able to provide some text around output formats and mappings that I can incorporate into the explainer please? Rough notes are sufficient, I can do the wordsmithing stuff but I need a bit of hand-holding to make sure the doc says the right thing. This, I hope, will also address the TAG review question around quads #118 as well as allowing me to finish tidying up the explainer.

@philarcher
Copy link
Contributor Author

Initial updating of the text of the explainer can be seen at w3c/rch-explainer#4

philarcher added a commit that referenced this issue Sep 11, 2023
@philarcher
Updated Use Cases section. Will fix Issue #110
750c017
gkellogg pushed a commit that referenced this issue Oct 19, 2023
@philarcher
Updated Use Cases section. Will fix Issue #110 (#175)
5341946 
* Updated Use Cases section. Will fix Issue #110
* Added link to now published explainer
@gkellogg
Copy link
Member

Fixed by #110.

@TallTed
Copy link
Member

TallTed commented Oct 20, 2023

[@gkellogg] Fixed by #110.

This is #110. I think that should say "Fixed by #175"

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@philarcher philarcher

Labels
spec:editorial
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@gkellogg @TallTed @philarcher