Mercurial > repos > shellac > sam_consensus_v3
comparison env/lib/python3.9/site-packages/cwltool/schemas/v1.1/salad/schema_salad/metaschema/field_name.yml @ 0:4f3585e2f14b draft default tip
"planemo upload commit 60cee0fc7c0cda8592644e1aad72851dec82c959"
author | shellac |
---|---|
date | Mon, 22 Mar 2021 18:12:50 +0000 |
parents | |
children |
comparison
equal
deleted
inserted
replaced
-1:000000000000 | 0:4f3585e2f14b |
---|---|
1 - | | |
2 ## Field name resolution | |
3 | |
4 The document schema declares the vocabulary of known field names. During | |
5 preprocessing traversal, field name in the document which are not part of | |
6 the schema vocabulary must be resolved to absolute URIs. Under "strict" | |
7 validation, it is an error for a document to include fields which are not | |
8 part of the vocabulary and not resolvable to absolute URIs. Fields names | |
9 which are not part of the vocabulary are resolved using the following | |
10 rules: | |
11 | |
12 * If an field name URI begins with a namespace prefix declared in the | |
13 document context (`@context`) followed by a colon `:`, the prefix and | |
14 colon must be replaced by the namespace declared in `@context`. | |
15 | |
16 * If there is a vocabulary term which maps to the URI of a resolved | |
17 field, the field name must be replace with the vocabulary term. | |
18 | |
19 * If a field name URI is an absolute URI consisting of a scheme and path | |
20 and is not part of the vocabulary, no processing occurs. | |
21 | |
22 Field name resolution is not relative. It must not be affected by the | |
23 base URI. | |
24 | |
25 ### Field name resolution example | |
26 | |
27 Given the following schema: | |
28 | |
29 ``` | |
30 - $include: field_name_schema.yml | |
31 - | | |
32 ``` | |
33 | |
34 Process the following example: | |
35 | |
36 ``` | |
37 - $include: field_name_src.yml | |
38 - | | |
39 ``` | |
40 | |
41 This becomes: | |
42 | |
43 ``` | |
44 - $include: field_name_proc.yml | |
45 - | | |
46 ``` |