Difference between revisions of "Schedule"
Jump to navigation
Jump to search
Megankatsumi (talk | contribs) m (Text replacement - "=Bylaw" to "=5087-2:Bylaw") |
Megankatsumi (talk | contribs) m (Text replacement - "5087-2:Bylaw" to "ISO5087-2:Bylaw") |
||
| Line 29: | Line 29: | ||
|Property=ProperPartOf | |Property=ProperPartOf | ||
|Restriction=exactly 1 | |Restriction=exactly 1 | ||
| − | |Value= | + | |Value=ISO5087-2:Bylaw |
}} | }} | ||
}} | }} | ||
{{Supplementary Figures}} | {{Supplementary Figures}} | ||
Latest revision as of 18:37, 17 December 2022
Pattern
This class has been associated with the following pattern:
Subclass Of
Description
An English description of the definition (what distinguishes this sense of the term?).
A Schedule is attached to the Bylaw and is part of the Bylaw. It has the following properties:
- schema:identifier: Unique identifier/number for the schedule. It is an xsd:string.
- schema:name: title or name of the schedule, if any. It is an xsd:string.
- schema:description: an introductory description of the Schedule. It is an xsd:string.
- hasClause: links to all clauses contained in the Schedule.
- 5087-1:properPartOf: The Bylaw this Schedule is part of.
Class Diagram Description
Required by Use Case(s)
(why is this specialized definition needed?)
CDM References
What other classes or properties reference this term?
Interface Specification References
This class has been associated with the following interface specification items:
Sources
Sources considered when developing the class:
Status
Pending Approval
Has Subclass(es)
Annotations
| Annotation | Value |
|---|
Manchester Syntax Specification
| Property | Restriction | Value |
|---|---|---|
| Schema:identifier | exactly 1 | xsd:string |
| Schema:name | exactly 1 | xsd:string |
| Schema:description | exactly 1 | xsd:string |
| HasClause | only | Clause |
| ProperPartOf | exactly 1 | ISO5087-2:Bylaw |
Supplementary Figures
| Figure | Caption |
|---|