Skip to content
New issue

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

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

Already on GitHub? # to your account

add rdf:dirLangString, rdf:reifies, rdf:Proposition, and modify rdf:JSON #31

Closed
wants to merge 2 commits into from

Conversation

domel
Copy link
Contributor

@domel domel commented Dec 17, 2024

This PR updates http://www.w3.org/1999/02/22-rdf-syntax-ns#. It modifies the Turtle file and changes from v1.1 to v1.2.

Added

  • rdf:dirLangString
  • rdf:reifies,
  • rdf:Proposition

Modified

  • rdf:JSON

@domel domel added the spec:substantive Change in the spec affecting its normative content (class 3) –see also spec:bug, spec:new-feature label Dec 17, 2024
Copy link

@niklasl niklasl left a comment

Choose a reason for hiding this comment

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

This looks good.

I presume we're making this repository the official source of this vocabulary? If this is correct I gladly welcome it.

I just have one wish for that: to first commit the original (the turtle as served on the official IRI), and then commit these changes upon that. To make it clear exactly what we're adding/changing. (I.e. do a rebase so this change is shown as a distinct commit (or commits).)

(Also adding the rdfs: source as rdfs.ttl seems appropriate?)

@gkellogg
Copy link
Member

I agree with @niklasl that we should start with a base which is based on the RDF 1.1 version of the RDF Vocabulary (and the RDFS Vocabulary, as well). We might also consider providing the namespace documents in different formats: The JSON-LD Namespace files generate Turtle, JSON-LD, and HTML versions of the JSON-LD vocabulary, and we could similarly do that for the RDF(S) vocabularies.

I would put rdf.ttl in an "ns" sub-directory, along with rdfs.ttl.

@niklasl
Copy link

niklasl commented Dec 18, 2024

Can this be on hold until #33 is merged, and then rebased upon that?

@domel
Copy link
Contributor Author

domel commented Dec 18, 2024

@niklasl I closed this one temporarily. When ns directory will be merged I will create a new PR only with rdf:dirLangString, rdf:reifies, rdf:Proposition, rdf:JSON

@domel domel closed this Dec 18, 2024
@niklasl
Copy link

niklasl commented Dec 18, 2024

@domel Sounds great; thanks!

# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
spec:substantive Change in the spec affecting its normative content (class 3) –see also spec:bug, spec:new-feature
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants