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

feat(context): use "@type" instead of "rdf:type" #1468

Merged
merged 2 commits into from
May 4, 2022

Conversation

ethieblin
Copy link

Similarly to #1466

The input data of these examples was generated by transforming a TD into RDF and the RDF into json-ld with rdflib
(same result when uploading/downloading the RDF triples from a SPARQL endpoint)

"type" does not round trip on the TD properties type

playground with original context

"properties": {
    "airpressure": {
      "@type": "number",
      }
 }

playground with new context

"properties": {
    "airpressure": {
      "type": "number",
      }
 }

this is needed for json-ld framing
@ethieblin
Copy link
Author

@wiresio fyi

@sebastiankb
Copy link
Contributor

same situation: see #1466 (comment)

1 similar comment
@sebastiankb
Copy link
Contributor

same situation: see #1466 (comment)

@sebastiankb sebastiankb added Editorial Issues with no technical impact on implementations non-normative labels May 3, 2022
@sebastiankb
Copy link
Contributor

from today's TD call, decided to merge

@w3cbot
Copy link

w3cbot commented May 4, 2022

ashimura marked as non substantive for IPR from ash-nazg.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Editorial Issues with no technical impact on implementations
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants