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.

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

[ednote] Mentioning Fragment Identifiers #1874

Open
egekorkan opened this issue Aug 23, 2023 · 0 comments
Open

[ednote] Mentioning Fragment Identifiers #1874

egekorkan opened this issue Aug 23, 2023 · 0 comments
Labels
Defer to TD 2.0 Needs discussion more discussion is needed before getting to a solution

Comments

@egekorkan
Copy link
Contributor

Copying over the editor's note (soon to be removed)

Under 12.1 application/td+json Media Type Registration / Fragment identifier considerations:

Editor's note: Other Fragment Identifier Considerations

We may want to explictly allow use of JSON Pointer as a fragment identifier [RFC6901]. There is in fact an assertion requiring them in TMs for tm:optional. These are internal references, however, so we might not have to allow them for external references. By default the json media type does not support a fragment identifier but td+json could.

@github-actions github-actions bot added the needs-triage Automatically added to new issues. TF should triage them with proper labels label Aug 23, 2023
@egekorkan egekorkan added Needs discussion more discussion is needed before getting to a solution Defer to TD 2.0 and removed needs-triage Automatically added to new issues. TF should triage them with proper labels labels Aug 23, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Defer to TD 2.0 Needs discussion more discussion is needed before getting to a solution
Projects
None yet
Development

No branches or pull requests

1 participant