-
Notifications
You must be signed in to change notification settings - Fork 7
Clarify 0.FDO/Attribute and ExtendsProfile rules #44
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
base: dev
Are you sure you want to change the base?
Changes from 1 commit
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -161,20 +161,24 @@ <h3 id="profiles">FDO Profiles</h3> | |
| <tr> | ||
| <td><a><em>0.FDO/Attribute</em></a> | ||
| </td> | ||
| <td><em><a><em>0.FDO/Attribute</em></a></em> defines the set of | ||
| <a>attribute definitions</a> that MUST be instantiated in any <a>FDO</a> instantiating this <a>profile</a>. | ||
| <td><a><em>0.FDO/Attribute</em></a> defines <a>attribute definitions</a> | ||
| that MUST be instantiated in any <a>FDO</a> instantiating this <a>profile</a> (via 0.FDO/Profile). | ||
| The value of this <a>attribute</a> is a PID of the <a>attribute definition</a>. | ||
|
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Please use |
||
| It can be repeated to add multiple <a>attribute definitions</a>. | ||
| The cardinality of the <a>attribute definitions</a> MUST be respected in the <a>FDOs</a>. | ||
| When not using <a>profile extension</a>, <a><em>0.FDO/Attribute</em></a> MUST be defined with at least the attributes from the <a>root profile</a>. | ||
| Other <a>attribute definitionss</a> can be added by adding more <a><em>0.FDO/Attribute</em></a> <a>tuples</a> with the <a>PID</a> of the desired <a>attribute definition</a>. | ||
| When not using <a>profile extension</a>, <a><em>0.FDO/Attribute</em></a> MUST be defined | ||
| with at least the attributes the <a>root profile</a> specifies. | ||
|
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Please use |
||
| </td> | ||
| <td>0..*</td> | ||
| </tr> | ||
| <tr> | ||
| <td><a><em>0.FDO/ExtendsProfile</em></a></td> | ||
| <td>If this <a>profile</a> is an extension of another <a>profile</a>, this <a>attribute</a> specifies the | ||
| <a>PID</a> of the parent profile (see <a href="#r4_11">[R4-11]</a>). | ||
| All <a>profiles</a> MUST either extend from <a><em>0.FDO/Root</em></a>, another profile that recursively extends | ||
| from <a><em>0.FDO/Root</em></a>, or specify the mandatory attributes from <a><em>0.FDO/Root</em></a> using <a><em>0.FDO/Attribute</em></a>. | ||
| <td>This <a>attribute</a> specifies the PID of another <a>profile</a>. | ||
| A <a>profile</a> containing this attribute, will implicitly require all attributes | ||
|
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Please use |
||
| of the referenced <a>profile</a> (see <a href="#r4_11">[R4-11]</a>). | ||
|
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. please change the reference to |
||
| In order to ensure all FDOs using this <a>profile</a> have the minimum set of attributes (as specified by 0.FDO/Root), | ||
|
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Please use |
||
| a FDO MUST either extend directly or indirectly from <a><em>0.FDO/Root</em></a>. | ||
|
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more.
I think you mean the profiles and and not the FDOs using it, right? |
||
| Alternatively, it may specify these minimum attributes directly using <a><em>0.FDO/Attribute</em></a>. | ||
| </td> | ||
| <td>0..*</td> | ||
| </tr> | ||
|
|
@@ -272,4 +276,4 @@ <h3 id="profiles">FDO Profiles</h3> | |
| <td>Indicates a path to the data (also called: <a>bit-sequence</a>) of the <a>FDO</a>.</td> | ||
| <td>1..*</td> | ||
| </tr> | ||
| </table> | ||
| </table> | ||
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Strictly speaking, the attributes are not defined in the profile (i.e., with 0.FDO/Attribute), but in their own FDO Record. Possible solution: use "specify"