Skip to content

Commit efad54d

Browse files
meldraprogval
andauthored
Apply review contribution; better way to introduce keywords
Co-authored-by: Val Lorentz <[email protected]>
1 parent 2b76caa commit efad54d

File tree

1 file changed

+6
-8
lines changed

1 file changed

+6
-8
lines changed

content/user-guide.md

Lines changed: 6 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -115,16 +115,14 @@ objects. For example:
115115
#### Keywords
116116

117117
JSON-LD has the concept of Keywords, which are properties prefaced with a `@`.
118-
Keywords instruct the processor how to *expand* the document with linked data.
118+
Keywords which give instructions to the processor instead of describing relations
119+
between entities.
119120

120-
Keywords can pull in other data; like programming language includes, work
121-
like functions; repeating the same data in multiple places, or act like a
122-
setting; changing the rules for the data.
123-
{.tip}
121+
This includes:
124122

125-
Some refer to external resources (such as `@context`), some (like `@list` and
126-
`@type`) add new constraints on the values for the property, while others
127-
include a copy of previously recorded information (`@id`).
123+
* defining shorthands (`@context`, `@vocab`),
124+
* changing value semantics (`@list` and `@set`, `@value`, `@language`, ...),
125+
* intrinsically describing objects (`@id` and `@type`)
128126

129127
The diagram below visualises how `@context` instructs the externally stored
130128
definition for CodeMeta to be *embedded* to *expand* the `codemeta.json`

0 commit comments

Comments
 (0)