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

Distinguish the RDF Data Model from the Abstract Syntax #129

Open
gkellogg opened this issue Jan 16, 2025 · 0 comments
Open

Distinguish the RDF Data Model from the Abstract Syntax #129

gkellogg opened this issue Jan 16, 2025 · 0 comments
Labels
ms:CR Milestone: Candidate Recommendation spec:substantive Change in the spec affecting its normative content (class 3) –see also spec:bug, spec:new-feature

Comments

@gkellogg
Copy link
Member

From @afs's review.

Observation

There is a mixture of "Abstract Syntax" and "Data Model". We should have a consistent way to say "Abstract Syntax" vs "Data Model". One way is to use "Abstract Syntax" as the basis of semantics and usually say "Data Model" in Concepts otherwise.

Section 1.1 Graph-based Data Model

suggestion

Possible improvement - rename as "RDF Data Model". Here, the section is called "Graph-based Data Model" but immediately it says "abstract syntax".

Change: ==> "The core structure of RDF is a graph, represented as a set of triples,"

Section 3. RDF Graphs

suggestion

This is the data model (abstract syntax). Maybe change the section name to "RDF Graph Data Model".

The intro section could have the preliminary explanation of RDF Strings.

@gkellogg gkellogg added ms:CR Milestone: Candidate Recommendation spec:substantive Change in the spec affecting its normative content (class 3) –see also spec:bug, spec:new-feature labels Jan 16, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
ms:CR Milestone: Candidate Recommendation spec:substantive Change in the spec affecting its normative content (class 3) –see also spec:bug, spec:new-feature
Projects
None yet
Development

No branches or pull requests

1 participant