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

Link directly to targets #1536

Open
gregsdennis opened this issue Sep 30, 2024 · 7 comments · May be fixed by #1568
Open

Link directly to targets #1536

gregsdennis opened this issue Sep 30, 2024 · 7 comments · May be fixed by #1568
Assignees
Labels
core proposal Initial discussion of a new idea. A project will be created once a proposal document is created. validation

Comments

@gregsdennis
Copy link
Member

With the spec docs now in markdown and with us self-hosting the files, should we move to having links go directly to their targets rather than to an appendix (which is IETF style)? Personally, I never liked linking to an appendix.

OpenAPI uses direct links, which you can see with the JSON Schema spec link in Section 4.4.

@jdesrosiers
Copy link
Member

I agree. The appendix is unnecessary.

@gregsdennis gregsdennis added core validation proposal Initial discussion of a new idea. A project will be created once a proposal document is created. labels Oct 2, 2024
@gregsdennis gregsdennis added this to the stable-release milestone Oct 2, 2024
@gregsdennis
Copy link
Member Author

gregsdennis commented Oct 2, 2024

I'm happy for anyone who wants to do this to take it.

For references to specific sections of the target, the links should go directly to that section (or as close as possible).

@SanidhyaMadheshia
Copy link

I think an appendix is not preferred by many contributors . And if direct linking enhances usability without sacrificing clarity, it could be a beneficial shift.

@gregsdennis
Copy link
Member Author

@jdesrosiers do we have support in the markdown processor to link between files? For example, if I wanted to reference the security concerns section in Core from Validation, could I do something like [Security Concerns in Core](core.md#security) or {{core#security}}?

@jdesrosiers
Copy link
Member

No, that feature only works on the local page. I looked into it last time you asked about that. I learned a lot about how it could be done, but don't have a solution yet. It's one of the many things I'm trying to juggle right now.

@gregsdennis
Copy link
Member Author

gregsdennis commented Jan 5, 2025

Question of preference:

The current appendix entries link to RFC catalog pages rather than directly to the docs themselves. The benefit of this is that the user can decide what document format they want. The detriment is that there's not a way to link directly to a section within a document.

For example, we have a link like

[section 3.5 of RFC 3986](#rfc3986)

for which the appendix entry is

https://www.rfc-editor.org/info/rfc3986

As part of this, I think it would be beneficial if we can link directly to section 3.5, which has a URL of

https://www.rfc-editor.org/rfc/rfc3986.html#section-3.5

Note that the path has changed: /info/rfc{number} -> /rfc/rfc{number}.html

If we decide to link to the section directly, does it make sense to use the direct-to-document link for all of them?

@gregsdennis
Copy link
Member Author

There are also quite a few places where we're repeating links. I definitely think we can eliminate some of this, but I'm not sure to what degree. Sane approaches:

  • link the first time it appears in the document, remaining references are plain text
  • link the first time it appears in the section (maybe limit to the nearest <h3>?)

@gregsdennis gregsdennis linked a pull request Jan 5, 2025 that will close this issue
@gregsdennis gregsdennis self-assigned this Jan 5, 2025
@gregsdennis gregsdennis moved this from Awaiting PR to In Progress in Stable Release Development Jan 5, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
core proposal Initial discussion of a new idea. A project will be created once a proposal document is created. validation
Projects
Status: In Progress
Development

Successfully merging a pull request may close this issue.

3 participants