You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/explore-and-author/graph-exploration/building-a-customized-user-interface/datatype-reference/index.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -17,7 +17,7 @@ This is a list of supported data types in shapes.
17
17
#### anyURI
18
18
19
19
20
-
The ·lexical space· of anyURI is finite-length character sequences which, when the algorithm defined in Section 5.4 of [XML Linking Language] is applied to them, result in strings which are legal URIs according to [RFC 2396], as amended by [RFC 2732]. Note: Spaces are, in principle, allowed in the ·lexical space· of anyURI, however, their use is highly discouraged (unless they are encoded by %20).
20
+
The ·lexical space· of anyURI is finite-length character sequences which, when the algorithm defined in Section 5.4 of [XML Linking Language] is applied to them, result in strings which are legal URIs according to [RFC 2396], as amended by [RFC 2732]. Note: Spaces are, in principle, allowed in the ·lexical space· of anyURI, however, their use is highly discouraged (unless they are encoded by %20).
The lexical space of dateTimeStamp consists of strings which are in the ·lexical space· of dateTime and which also match the regular expression '.*(Z|(+|-)[0-9][0-9]:[0-9][0-9])'
62
+
The lexical space of dateTimeStamp consists of strings which are in the ·lexical space· of dateTime and which also match the regular expression `.*(Z|(+|-)[0-9][0-9]:[0-9][0-9])`
Copy file name to clipboardExpand all lines: docs/explore-and-author/graph-exploration/building-a-customized-user-interface/node-shapes/index.md
+18Lines changed: 18 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -212,6 +212,24 @@ The query needs to be an ASK query and can include the following placeholders, w
212
212
Used Path: `shui:askIfRemovableQuery`
213
213
214
214
215
+
### Query: Is Editable Resource
216
+
217
+
218
+
This query is executed to check if users get the controls to edit resources (described with the node shape).
219
+
220
+
The query needs to be an ASK query and can include the following placeholders, which will be substituted before execution:
221
+
222
+
-`{{shuiResource}}` - refers to the resource which is rendered in the node shape where this property shape is used (maybe a sub-shape)
223
+
-`{{shuiGraph}}` - the IRI of the current working graph
224
+
-`{{shuiAccount}}` - the IRI of the active user account
225
+
-`{{shuiAccountName}}` - the user name/ID of the active user account
226
+
-`{{shuiMainResource}}` - refers to the main resource rendered in the start node shape of the currently displayed node shape tree (only relevant in case of sub-shape usage)
Copy file name to clipboardExpand all lines: docs/explore-and-author/graph-exploration/building-a-customized-user-interface/property-shapes/index.md
+11-9Lines changed: 11 additions & 9 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -110,21 +110,23 @@ Used Path: `shacl:path`
110
110
### Query: Path Builder
111
111
112
112
113
-
Use this property to define a dynamic set of target resources or literals using a custom SPARQL query. This allows for advanced selection logic, including filtering, transitive relationships, or specific path sequences as well as the definition of a resultset order.
113
+
Use this property to define a dynamic set of target resources or literals with a custom SPARQL query. This allows advanced selection logic, including filtering, transitive relationships, specific path sequences, and result-set ordering.
114
114
115
-
The values bound to the first variable in the query's projection will be treated as directly connected via the `sh:path` specified in this property shape. This enables simple backward-chaining inference. Note that the infererred connections are not (yet) included in SHACL validation.
115
+
The values bound to the first variable in the query's projection are treated as directly connected via the `sh:path` specified in this property shape. This enables simple backward-chaining inference. Note that the inferred connections are not (yet) included in SHACL validation.
116
116
117
-
The following placeholder can be used in the query text of the SPARQL query:
117
+
The following placeholders can be used in the SPARQL query text:
118
118
119
119
-`{{shuiGraph}}` - the currently used graph
120
-
-`{{shuiResource}}` - refers to the resource which is rendered in the node shape where this property shape is used (maybe a sub-shape)
121
-
-`{{shuiAccount}}` - the account IRI of the active user, this includes the username (use a SUBSTR() function if you need the name only)
122
-
-`{{shuiAccountName}}` - the user name/ID of the active user account
123
-
-`{{shuiMainResource}}` - refers to the main resource rendered in the start node shape of the currently displayed node shape tree (only relevant in case of sub-shape usage)
120
+
-`{{shuiResource}}` - refers to the resource rendered in the node shape where this property shape is used (including sub-shapes)
121
+
-`{{shuiAccount}}` - the account IRI of the active user, including the username (use a SUBSTR() function if you need the name only)
122
+
-`{{shuiAccountName}}` - the username/ID of the active user account
123
+
-`{{shuiMainResource}}` - refers to the main resource rendered in the start node shape of the currently displayed node shape tree (only relevant for sub-shape usage)
124
+
125
+
For proper usage, include `?graph` or `?_graph` in the projection, bound to the IRI of the graph where the relation statement is stored or the context in which it was inferred.
124
126
125
-
Note that for a proper usage of this feature, you additionally need to have the projection variables `?graph` or `?_graph` (the graph IRI where the relation statement is saved resp. in the context of which it was inferred) in your query.
127
+
Link changing variables: If you bind the magic variables `?_linkGraph`/`?linkGraph` or `?_linkWorkspace`/`?linkWorkspace`, they override the default link behavior for generated context/workspace parts of links. Use the IRI of the target graph or the ID of the target workspace. The values apply to `?resource` or, if not present, the first variable in the projection.
126
128
127
-
If the connected property value is a resource, the variables in the projection of this query will be used to populate the columns in the complex widget and the advanced editor.
129
+
If the connected property value is a resource, the variables in the projection are used to populate the columns in the complex widget and the advanced editor.
0 commit comments