 |
Page History
...
ID | Requirement | Source | Release | ||||
|---|---|---|---|---|---|---|---|
MDS-1 | The Metadata Service MUST support the notion of data elements. |
| |||||
MDS-2 | The Metadata Service MUST allow the recording of data elements. |
| |||||
MDS-3 | The Metadata Service MUST allow new data element assertions to be made. |
| |||||
MDS-4 | The Metadata Service MUST allow for data elements to be updated. |
| |||||
MDS-5 | The Metadata Service MUST allow for data elements to be versioned. |
| |||||
MDS-6 | The Metadata Service SHOULD allow for data element business rules to be validated. |
| |||||
MDS-7 | The Metadata Service MUST allow for data elements to be retired. |
| |||||
MDS-8 | The Metadata Service MUST allow for data elements to be deleted/rolled back. |
| |||||
MDS-9 | The Metadata Service MUST support the discovery of reusable data element content. |
| |||||
MDS-10 | The Metadata Service SHOULD support the notion of data element usage information. |
| |||||
MDS-11 | The Metadata Service MUST support metadata to be queried by data element. |
| |||||
MDS-12 | The Metadata Service SHOULD support metadata to be queried by data element in a federated manner. |
| |||||
MDS-13 | The Metadata Service MUST support the comparison of data elements |
| |||||
MDS-14 | The Metadata Service SHOULD support the creation of a new data element from an existing data element. |
| |||||
MDS-15 | The Metadata Service MUST support the discovery of related models by data element. |
| |||||
MDS-16 | The Metadata Service SHOULD support the discover related metadata items by data element. |
| |||||
MDS-17 | The Metadata Service SHOULD support the discovery of related services by data element. |
| |||||
MDS-18 | The Metadata Service SHOULD support the discovery of related data element rules. |
| |||||
MDS-19 | The Metadata Service SHOULD support the discovery of forms related by data element. |
| |||||
MDS-101 | Value Domain |
| MDS-1 | The Metadata Service MUST support the notion of data elementsvalue domains. |
| ||
MDS-2 102 | The Metadata Service MUST allow the recording of data elementsvalue domains. |
| |||||
MDS-3 103 | The Metadata Service MUST allow new data element value domain assertions to be made. |
| |||||
MDS-4 104 | The Metadata Service MUST allow for data elements value domains to be updated. |
| |||||
MDS-5 105 | The Metadata Service MUST allow for data elements value domains to be versioned. |
| |||||
MDS-6 106 | The Metadata Service SHOULD allow for data element value domain business rules to be validated. |
| |||||
MDS-7 107 | The Metadata Service MUST allow for data elements value domains to be retired. |
| |||||
MDS-8 108 | The Metadata Service MUST allow for data elements value domains to be deleted/rolled back. |
| |||||
MDS-9 109 | The Metadata Service MUST support the discovery of reusable data element value domain content. |
| |||||
MDS-10 110 | The Metadata Service SHOULD support the notion of data element value domain usage information. |
| |||||
MDS-11 111 | The Metadata Service MUST support metadata to be queried by data elementvalue domain. |
| |||||
MDS-12 112 | The Metadata Service SHOULD support metadata to be queried by data element value domain in a federated manner. |
| |||||
MDS-13 113 | The Metadata Service MUST support the comparison of data elements value domains |
| |||||
MDS-14 114 | The Metadata Service SHOULD support the creation of a new data element value domain from an existing data element. |
| |||||
MDS-15 115 | The Metadata Service MUST support the discovery of related models by data elementvalue domain. |
| |||||
MDS-16 116 | The Metadata Service SHOULD support the discover related metadata items by data elementvalue domain. |
| |||||
MDS-17 117 | The Metadata Service SHOULD support the discovery of related services by data elementvalue domain. |
| |||||
MDS-18 118 | The Metadata Service SHOULD support the discovery of related data element value domain rules. |
| |||||
MDS-19 119 | The Metadata Service SHOULD support the discovery of forms related by data elementvalue domain. |
| |||||
MDS-120 | Create subset/constrain The Metadata Service SHOULD support the ability to create a value domain through subsetting/constraining. |
|
| ||||
MDS-120 121 | The Metadata Service SHOULD allow value domains to be extended through the creation of Extend (create new from existing) . |
|
| ||||
MDS-120 130 | The Metadata Service SHOULD support semantic transformations that would be explicitly based on value domain mapping, Semantic transformations (Explicitly based on mapping e.g. to the same Value Meaning) value meaning. |
| |||||
MDS-120 131 | The Metadata Service MAY support syntactic transformations that would transform source value domain representation to target value domain representation. Syntactic transformations ( Source representation to Target representation) |
| |||||
MDS-201 Data Element Concept |
| MDS-1 | The Metadata Service MUST support the notion of data elementselement concepts. |
| |||
MDS-2 202 | The Metadata Service MUST allow the recording of data elementselement concepts. |
| |||||
MDS-3 203 | The Metadata Service MUST allow new data element concept assertions to be made. |
| |||||
MDS-4 204 | The Metadata Service MUST allow for data elements element concepts to be updated. |
| |||||
MDS-5 205 | The Metadata Service MUST allow for data elements element concepts to be versioned. |
| |||||
MDS-6 206 | The Metadata Service SHOULD allow for data element concept business rules to be validated. |
| |||||
MDS-7 207 | The Metadata Service MUST allow for data elements element concepts to be retired. |
| |||||
MDS-8 208 | The Metadata Service MUST allow for data elements element concepts to be deleted/rolled back. |
| |||||
MDS-9 209 | The Metadata Service MUST support the discovery of reusable data element concept content. |
| |||||
MDS-10 210 | The Metadata Service SHOULD support the notion of data element concept usage information. |
| |||||
MDS-11 211 | The Metadata Service MUST support metadata to be queried by data element concept. |
| |||||
MDS-12 212 | The Metadata Service SHOULD support metadata to be queried by data element concept in a federated manner. |
| |||||
MDS-13 213 | The Metadata Service MUST support the comparison of data elements element concepts |
| |||||
MDS-14 214 | The Metadata Service SHOULD support the creation of a new data element concept from an existing data element concept. |
| |||||
MDS-15 215 | The Metadata Service MUST support the discovery of related models by data element concept. |
| |||||
MDS-16 216 | The Metadata Service SHOULD support the discover related metadata items by data element concept. |
| |||||
MDS-17 217 | The Metadata Service SHOULD support the discovery of related services by data element concept. |
| |||||
MDS-18 218 | The Metadata Service SHOULD support the discovery of related data element concept rules. |
| |||||
MDS-19 219 | The Metadata Service SHOULD support the discovery of forms related by data element concept. |
| |||||
MDS-220 | Discover The Metadata Service MUST support the discovery of related data elements by data element concept. |
| |||||
MDS-222 221 | The Metadata Service SHOULD support the discovery of Discover related value sets by data element concept. |
| |||||
MDS-223 230 | The Metadata Service SHOULD support the creation of a Create data element from an existing data element concept and value domain. |
| |||||
MDS-224 231 | The Metadata Service SHOULD support the creation of a Create new data element concept from an existing data element concept. |
|
Registry-Registry Service
...
