Skip to content

Added informative reference to SPARQL11-OVERVIEW in intro #110

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

Merged
merged 1 commit into from
Dec 18, 2018

Conversation

pchampin
Copy link
Contributor

@pchampin pchampin commented Dec 18, 2018

@gkellogg I'd rather use a PR for the moment, to be sure I don't mess things up.

You'll have to explain to me what magic inserted the correct text for SPARQL11-OVERVIEW in the reference section -- and what would have been required to insert it in the normative references instead...


Preview | Diff

@gkellogg
Copy link
Member

@iherman will need to figure out the IPR issues.

Regarding normative/informative references, ReSpec recently added some magic to figure this out, based on if it’s in a normative or informative section. It can be overridden, but the details of this are on the ReSpec wiki.

@@ -284,7 +284,7 @@ <h1>Introduction</h1>
<p>
JSON-LD is designed to be usable directly as JSON, with no knowledge of RDF
[[RDF11-CONCEPTS]]. It is also designed to be usable as RDF, if desired, for
use with other Linked Data technologies like SPARQL. Developers who
use with other Linked Data technologies like SPARQL [[SPARQL11-OVERVIEW]]. Developers who
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I believe [[!SPARQ=OVERVIEW]] would be normative.

@iherman
Copy link
Member

iherman commented Dec 18, 2018

@gkellogg @pchampin: there is an automatic mechanism to check the possible IPR issues with PRs. @pchampin, you should associate your W3C account with your github account on https://www.w3.org/users/myprofile/connectedaccounts. Once this association is done, the system knows you are part of the WG and things happen (and you will not be asked again).

I can give a green light for one specific contribution (I believe...) but it is better to do this association once and for all.

@gkellogg
Copy link
Member

Once IPR is figured out, please go ahead and pull the PR.

@pchampin
Copy link
Contributor Author

Sorry about the IPR issue. I just associated by github account to my W3C account.

@pchampin pchampin merged commit 6f92b1d into master Dec 18, 2018
@gkellogg gkellogg deleted the ref_to_sparql branch January 9, 2019 21:23
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 this pull request may close these issues.

3 participants