Changes for page 12 Constraints

Summary

• Page properties (1 modified, 0 added, 0 removed)

Details

Page properties

Content

...	...	@@ -4,16 +4,14 @@
4	4
5	5	== 12.1 Scope ==
6	6
7		-The scope of this section is to describe the support in the metamodel for specifying both the access to and the content of a [[data source>>doc:sdmx:Glossary 2\.1.Data source.WebHome]]. The information may be stored in
	7	+The scope of this section is to describe the support in the metamodel for specifying both the access to and the content of a data source. The information may be stored in a resource such as a registry for use by applications wishing to locate data and metadata which are available via the Internet. The //Constraint// is also used to specify a subset of a Codelist which may be used as a partial Codelist, relevant in the context of the artefact to which the //Constraint// is attached e.g., DataStructureDefinition, Dataflow, ProvisionAgreement, MetadataStructureDefinition, Metadataflow, MetadataProvisionAgreement.
8	8
9		-a resource such as a registry for use by applications wishing to locate data and metadata which are available via the Internet. The //[[Constraint>>doc:sdmx:Glossary 2\.1.Constraint.WebHome]]// is also used to specify a subset of a [[Codelist>>doc:sdmx:Glossary 2\.1.Code list.WebHome]] which may be used as a partial [[Codelist>>doc:sdmx:Glossary 2\.1.Code list.WebHome]], relevant in the context of the [[artefact>>doc:sdmx:Glossary 2\.1.Artefact.WebHome]] to which the //[[Constraint>>doc:sdmx:Glossary 2\.1.Constraint.WebHome]]// is attached e.g., DataStructureDefinition, [[Dataflow>>doc:sdmx:Glossary 2\.1.Dataflow.WebHome]], ProvisionAgreement, MetadataStructureDefinition, [[Metadataflow>>doc:sdmx:Glossary 2\.1.Metadataflow.WebHome]], MetadataProvisionAgreement.
	9	+Note that in this metamodel the term data provider refers to both data and metadata providers.
10	10
11		-Note that in this metamodel the term [[data provider>>doc:sdmx:Glossary 2\.1.Data provider.WebHome]] refers to both data and metadata providers.
	11	+The Dataflow and Metadataflow, themselves may be specified as containing only a subset of all the possible keys that could be derived from a DataStructureDefinition or MetadataStructureDefinition. Respectively, further subsets may be defined within a ProvisionAgreement and MetadataProvisionAgreement.
12	12
13		-The [[Dataflow>>doc:sdmx:Glossary 2\.1.Dataflow.WebHome]] and [[Metadataflow>>doc:sdmx:Glossary 2\.1.Metadataflow.WebHome]], themselves may be specified as containing only a subset of all the possible keys that could be derived from a DataStructureDefinition or MetadataStructureDefinition. Respectively, further subsets may be defined within a ProvisionAgreement and MetadataProvisionAgreement.
	13	+These specifications are called //Constraint// in this model.
14	14
15		-These specifications are called //[[Constraint>>doc:sdmx:Glossary 2\.1.Constraint.WebHome]]// in this model.
16		-
17	17	== 12.2 Inheritance ==
18	18
19	19	=== 12.2.1 Class Diagram of Constrainable Artefacts - Inheritance ===
...	...	@@ -26,18 +26,18 @@
26	26
27	27	==== 12.2.2.1 Narrative ====
28	28
29		-Any [[artefact>>doc:sdmx:Glossary 2\.1.Artefact.WebHome]] that inherits from the //ConstrainableArtefact// interface can have [[constraints>>doc:sdmx:Glossary 2\.1.Constraint.WebHome]] defined. The [[artefacts>>doc:sdmx:Glossary 2\.1.Artefact.WebHome]] that can have [[constraint>>doc:sdmx:Glossary 2\.1.Constraint.WebHome]] metadata attached are:
	27	+Any artefact that inherits from the //ConstrainableArtefact// interface can have constraints defined. The artefacts that can have constraint metadata attached are:
30	30
31		-[[Dataflow>>doc:sdmx:Glossary 2\.1.Dataflow.WebHome]]
	29	+Dataflow
32	32	ProvisionAgreement
33	33	DataProvider
34	34	DataStructureDefinition
35		-[[Metadataflow>>doc:sdmx:Glossary 2\.1.Metadataflow.WebHome]]
	33	+Metadataflow
36	36	MetaDataProvider
37	37	MetadataProvisionAgreement
38	38	MetadataStructureDefinition
39	39
40		-Note that, because the //[[Constraint>>doc:sdmx:Glossary 2\.1.Constraint.WebHome]]// can specify a subset of the [[component>>doc:sdmx:Glossary 2\.1.Component.WebHome]] values implied by a specific //Structure// (such as a specific DataStructureDefinition or specific MetadataStructureDefinition), the //ConstrainableArtefact//s must be associated with a specific //Structure//. Therefore, whilst the //[[Constraint>>doc:sdmx:Glossary 2\.1.Constraint.WebHome]]// itself may not be linked directly to a DataStructureDefinition or MetadataStructureDefinition, the [[artefact>>doc:sdmx:Glossary 2\.1.Artefact.WebHome]] that it is constraining will be linked to a DataStructureDefinition or MetadataStructureDefinition. A DataProvider and MetadataProvider indirectly refernece DSDs and MSDs through their associated Data and Metadata [[Provision Agreements>>doc:sdmx:Glossary 2\.1.Provision agreement.WebHome]] as such these [[Constraints>>doc:sdmx:Glossary 2\.1.Constraint.WebHome]] are restricted to Cube Regions and are applicable only to the DSDs / MSDs which contain the Componets being restricted.
	38	+Note that, because the //Constraint// can specify a subset of the component values implied by a specific //Structure// (such as a specific DataStructureDefinition or specific MetadataStructureDefinition), the //ConstrainableArtefact//s must be associated with a specific //Structure//. Therefore, whilst the //Constraint// itself may not be linked directly to a DataStructureDefinition or MetadataStructureDefinition, the artefact that it is constraining will be linked to a DataStructureDefinition or MetadataStructureDefinition. A DataProvider and MetadataProvider indirectly refernece DSDs and MSDs through their associated Data and Metadata Provision Agreements as such these Constraints are restricted to Cube Regions and are applicable only to the DSDs / MSDs which contain the Componets being restricted.
41	41
42	42	== 12.3 Constraints ==
43	43