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

explicit section references should replace abstract "the next section" references #65

Open
TallTed opened this issue Jan 3, 2025 · 3 comments · May be fixed by #64
Open

explicit section references should replace abstract "the next section" references #65

TallTed opened this issue Jan 3, 2025 · 3 comments · May be fixed by #64

Comments

@TallTed
Copy link
Member

TallTed commented Jan 3, 2025

Originally posted by @afs in w3c/rdf-concepts#122 (comment)

RDF Semantics section "5 Simple Interpretations" change note:

The full semantics for typed literals is given in the next section.

(The "next section" seems to mean section 7, not 5.1 or 6)

The text above is visible if you follow this link.

It seems to me that every occurrence of "the next section", "the previous section", or similar, should be converted to an explicit reference by title/id, e.g., the section [[[title]]] [[reference]]

@afs
Copy link

afs commented Jan 3, 2025

that every occurrence

There is only this one occurrence of "next section" and there are no occurrences of "previous section".

@TallTed Do you see others? Other places that might be converted to references?

@afs
Copy link

afs commented Jan 3, 2025

Done in #64.

@afs afs linked a pull request Jan 3, 2025 that will close this issue
@TallTed
Copy link
Member Author

TallTed commented Jan 6, 2025

@afs — My previous comment "that every occurrence" should be addressed was meant to extend my comment to all documents we're producing, not just this one.

I do note a few more instances of next/previous (not section, but still troublesome) in spec/index.html. I include suggested tweaks below.

  • Nevertheless, they are in a strong sense almost interchangeable, as shown the next two properties. The third property means that even when conclusions are drawn from the skolemized graph which do contain the new vocabulary, these will exactly mirror what could have been derived from the original graph with the original blank nodes in place. The replacement of blank nodes by IRIs does not effectively alter what can be validly derived from the graph, other than by giving new names to what were formerly anonymous entities. The fourth property, which is a consequence of the third, clearly shows that in some sense a skolemization of G can "stand in for" G as far as entailments are concerned. Using sk(G) instead of G will not affect any entailments which do not involve the new skolem vocabulary. </p>

    as shown the next two properties -> as shown by the third and fourth properties
  • <p class="changenote">The previous version of this specification defined the parameter D

    The previous version of this specification -> identify a specific version/date and make this text link to it. There'a a nearby preceding reference to the 2004 RDF 1.0 specification which should also be linked to that document.
  • <p>Using the terminology in the previous proof: if H does not contain any skolem IRIs, then H=ks(H).

    Using the terminology in the previous proof -> ??? I am guessing that the previous proof is the previous yellow block. It would be best to add titles to each proof, and a link from this "previous proof" text to the appropriate title, which would optimally be used as a replacement for the previous text.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants