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.

Sign up for GitHub

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

Jump to bottom

fixed typo #179

Merged
merged 1 commit into from
Oct 8, 2021
Merged

fixed typo #179

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion CONVENTIONS.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -158,5 +158,5 @@ One impact of this change is that the Google Structured Data Testing Tool presen
**Using external vocabulary prefixes**
In addition, if one uses [schema:additionalType](https://schema.org/additionalType), then one can not use prefixes defined in the `@context` section when referencing these external concepts. Instead, the concept must be specified with its full URL. This is illustrated in the example above, where we have to use `"additionalType": "http://vocabulary.example.org/ScientificInstrument"` rather than the more compact prefixed version `"@type": ["ex:ScientificInstrument"]`.

If one does decide to use `additionalType`, then opening the example in the JSON-LD Playground will show how the element type is nnot expanded and there is no triple generated for the additionalType. Thus, we recommend using the `@type` field directly for associating fields with types so that they become part of the knowledge graph for the Dataset.
If one does decide to use `additionalType`, then opening the example in the JSON-LD Playground will show how the element type is not expanded and there is no triple generated for the additionalType. Thus, we recommend using the `@type` field directly for associating fields with types so that they become part of the knowledge graph for the Dataset.