Changes for page Part VI. Registry Namespace
Last modified by Artur on 2025/09/10 11:19
Summary
-
Page properties (1 modified, 0 added, 0 removed)
Details
- Page properties
-
- Content
-
... ... @@ -134,21 +134,17 @@ 134 134 **MaintainableQueryType: **MaintainableQueryType describes the structure of a query for a maintainable object. 135 135 136 136 Derivation: 137 +* IdentifiableQueryType (extension) 138 +** VersionableQueryType (extension) 139 +*** MaintainableQueryType 137 137 138 -IdentifiableQueryType (extension) 139 - [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] VersionableQueryType (extension) 140 - [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] MaintainableQueryType 141 - 142 142 Attributes: 143 - 144 144 id?, version?, agencyID? 145 145 146 146 Content: 147 - 148 148 {Empty} 149 149 150 150 Attribute Documentation: 151 - 152 152 |**Name**|**Type**|**Documentation** 153 153 |id (default: %)|IDQueryType|The id attribute is used to query for an object based on its identifier. This is either an explicit value, or completely wild cared with the "%" value. 154 154 |version (default: *)|VersionQueryType|The version attribute is used to query for an object based on its version. This can be and explicit value, wild-carded ("%"), or late-bound ("*"). A wild carded version will match any version of the object where as a late-bound version will only match the latest version. ... ... @@ -157,20 +157,16 @@ 157 157 **StatusMessageType: **StatusMessageType carries the text of error messages and/or warnings in response to queries or requests. 158 158 159 159 Attributes: 160 - 161 161 status 162 162 163 163 Content: 164 - 165 165 MessageText* 166 166 167 167 Attribute Documentation: 168 - 169 169 |**Name**|**Type**|**Documentation** 170 170 |status|StatusType|The status attribute carries the status of the query or request. 171 171 172 172 Element Documentation: 173 - 174 174 |**Name**|**Type**|**Documentation** 175 175 |MessageText|com: StatusMessageType|MessageText contains the text of the error and/or warning message. It can occur multiple times to communicate message for multiple warnings or errors. 176 176 ... ... @@ -177,11 +177,9 @@ 177 177 **SubmitRegistrationsRequestType: **SubmitRegistrationsRequestType defines the payload of a request message used to submit addtions, updates, or deletions of data/metadata set registrations. 178 178 179 179 Content: 180 - 181 181 RegistrationRequest+ 182 182 183 183 Element Documentation: 184 - 185 185 |**Name**|**Type**|**Documentation** 186 186 |RegistrationRequest|RegistrationRequestT ype|RegistrationRequest provides the details of a requested registration and the action to take on it. A reference to a provision agreement that exists in the registry must be provide along with a simple and/or queryable data source. The id should only be provided when updating or deleting a registration. 187 187 ... ... @@ -188,20 +188,16 @@ 188 188 **RegistrationRequestType: **RegistrationRequestType describes the structure of a single registration request. It contains the details of a registation and an action field to indicate the action to be taken on the contained registration. 189 189 190 190 Attributes: 191 - 192 192 action 193 193 194 194 Content: 195 - 196 196 Registration 197 197 198 198 Attribute Documentation: 199 - 200 200 |**Name**|**Type**|**Documentation** 201 201 |action|com:ActionType|The action attribute indicates whether this is an addition, a modification, or a deletion of a registration. 202 202 203 203 Element Documentation: 204 - 205 205 |**Name**|**Type**|**Documentation** 206 206 |Registration|RegistrationType|Registration contains the details of the data/metadata set registration to be added, updated, or deleted. 207 207 ... ... @@ -208,11 +208,9 @@ 208 208 **SubmitRegistrationsResponseType: **SubmitRegistrationsResponseType describes the structure of a registration response. For each submitted registration in the request, a registration status is provided. The status elements should be provided in the same order as the submitted registrations, although each status will echo the request to ensure accurate processing of the responses. 209 209 210 210 Content: 211 - 212 212 RegistrationStatus+ 213 213 214 214 Element Documentation: 215 - 216 216 |**Name**|**Type**|**Documentation** 217 217 |RegistrationStatus|RegistrationStatusTy pe|RegistrationStatus provided the status details for the submitted registration. It echoes the original submission and provides status information about the request. 218 218 ... ... @@ -219,11 +219,9 @@ 219 219 **RegistrationStatusType: **RegistrationStatusType describes the structure of a registration status. 220 220 221 221 Content: 222 - 223 223 Registration, StatusMessage 224 224 225 225 Element Documentation: 226 - 227 227 |**Name**|**Type**|**Documentation** 228 228 |Registration|RegistrationType|Registration, at the very least echoes the submitted registration. It the request was to create a new registration and it was successful, an id must be supplied. 229 229 |StatusMessage|StatusMessageType|StatusMessage provides that status for the registration request, and if necessary, any error or warning information. ... ... @@ -231,20 +231,16 @@ 231 231 **QueryRegistrationRequestType: **QueryRegistrationRequestType describes the structure of a registration query request. The type of query (data, reference metadata, or both) must be specified. It is possible to query for registrations for a particular provision agreement, data provider, or structure usage, or to query for all registrations in the registry. In addition the search can be refined by providing constraints in the form of explicit time periods, constraint regions, and key sets. When constraint regions and key sets are provided they will be effectively processed by first matching all data for the included keys and regions (all available data if there are none) and then removing any data matching the excluded keys or regions. 232 232 233 233 Attributes: 234 - 235 235 returnConstraints? 236 236 237 237 Content: 238 - 239 239 QueryType, (All | ProvisionAgreement | DataProvider | Dataflow | Metadataflow), ReferencePeriod?, (DataKeySet | MetadataKeySet | CubeRegion | MetadataTargetRegion)* 240 240 241 241 Attribute Documentation: 242 - 243 243 |**Name**|**Type**|**Documentation** 244 244 |returnConstraints (default: false)|xs:boolean|The returnConstraints attribute determines whether information about the constraints on the data or metadata sets returned should also be sent the results. 245 245 246 246 Element Documentation: 247 - 248 248 |**Name**|**Type**|**Documentation** 249 249 |QueryType|QueryTypeType|QueryType defines the type of sets (data, metadata, or both) that are being queried for. 250 250 |All|com:EmptyType|All indicates that all registrations meeting the other criteria of the query should be returned. ... ... @@ -261,11 +261,9 @@ 261 261 **QueryRegistrationResponseType: **QueryRegistrationResponseType describes the structure of a registration query response. It provides a status for the request, and if successful, the resulting data and/or metadata results. 262 262 263 263 Content: 264 - 265 265 StatusMessage, QueryResult* 266 266 267 267 Element Documentation: 268 - 269 269 |**Name**|**Type**|**Documentation** 270 270 |StatusMessage|StatusMessageType|StatusMessage provides that status for the registration query request, and if necessary, any error or warning information. 271 271 |QueryResult|QueryResultType|QueryResult contains a result for a successful registration query. It can occur multiple times, for each registration the meets the conditions specified in the query. ... ... @@ -273,20 +273,16 @@ 273 273 **QueryResultType: **QueryResultType describes the structure of a query result for a single data source. Either a data result or metadata result is detailed, depending on the data source. 274 274 275 275 Attributes: 276 - 277 277 timeSeriesMatch 278 278 279 279 Content: 280 - 281 281 (DataResult | MetadataResult) 282 282 283 283 Attribute Documentation: 284 - 285 285 |**Name**|**Type**|**Documentation** 286 286 |timeSeriesMatch|xs:boolean|The timeSeriesMatch attribute is true when the result is an exact match with the key found in the registry - that is, when the registered data source provides a matching key. It is set to false when the data source is registered with cube-region constraints, or in any other circumstance when it cannot be established that the sought-for keys have been exactly matched. This is always true when the resulting data source is the source of a metadata set. 287 287 288 288 Element Documentation: 289 - 290 290 |**Name**|**Type**|**Documentation** 291 291 |DataResult|ResultType| 292 292 |MetadataResult|ResultType| ... ... @@ -294,11 +294,9 @@ 294 294 **ResultType: **ResultType contains the details about a data or metadata source, through the complete registration information. In addition, a reference to the content constraints for the data source may be provided, if the query requested this information. 295 295 296 296 Content: 297 - 298 298 Registration, ContentConstraint* 299 299 300 300 Element Documentation: 301 - 302 302 |**Name**|**Type**|**Documentation** 303 303 |Registration|RegistrationType|Registration provides the details of a matching registration. In addition to the data source and provision agreement information, the id of the registration must also be provided. 304 304 |ContentConstraint|com: ContentConstraintRef erenceType|ContentConstraint provides a reference to a content constraint in the registry for the resulting data source (or possibly constraints base on the registration provision agreement, data provider, structure usage, or structure). The reference is provided for by a URN and/or a complete set of reference fields. ... ... @@ -306,21 +306,17 @@ 306 306 **SubmitStructureRequestType: **SubmitStructureRequestType describes the structure of a structure submission. Structural components are provided either in-line or referenced via a SDMX-ML Structure message external to the registry. A default action and external reference resolution action are all provided for each of the contained components, but can be overridden on a per component basis. 307 307 308 308 Attributes: 309 - 310 310 action?, externalDependencies? 311 311 312 312 Content: 313 - 314 314 (StructureLocation | str:Structures), SubmittedStructure* 315 315 316 316 Attribute Documentation: 317 - 318 318 |**Name**|**Type**|**Documentation** 319 319 |action (default: Append)|com:ActionType|The action attribute indicates the default action (append-add, replace-update, delete, or no action-informational) to be taken on all structural components in either the external SDMX-ML Structure message or the in-line components. The default action is Append. The Replace action is not applicable to final structures in the repository, and will produce an error condition, as these can be versioned but not modified. To submit a later version of a structural object, the object should include the incremented version number. 320 320 |externalDependencies (default: false)|xs:boolean|The externalDependencies attribute indicates the default resolution of external dependencies. This should be set to true if the repository is expected to use external reference URLs in the structural components to retrieve any externally referenced objects that is used by a non-external object. 321 321 322 322 Element Documentation: 323 - 324 324 |**Name**|**Type**|**Documentation** 325 325 |StructureLocation|xs:anyURI|StructureLocation provides the location of a SDMX-ML Structure message, external to the repository that can be retrieved by the repository submission service. 326 326 |str:Structures|str:StructuresType|Structures allows for the inline definition of structural components for submission. ... ... @@ -329,21 +329,17 @@ 329 329 **SubmittedStructureType: **SubmittedStructureType generally references a submitted structural object. When used in a submit structure request, its purpose is to override the default action or external dependency resolution behavior. If neither of these indicators are set, then it will be ignored. In a submit structure response, it is used to reference a submitted object for the purpose of providing a status for the submission. In this case, the action attribute should be populated in order to echo the requested action. 330 330 331 331 Attributes: 332 - 333 333 action?, externalDependencies? 334 334 335 335 Content: 336 - 337 337 MaintainableObject 338 338 339 339 Attribute Documentation: 340 - 341 341 |**Name**|**Type**|**Documentation** 342 342 |action|com:ActionType|The action attribute will indicate the action to be taken on the referenced structural object. This should be provided when this structure is used in a submit structure response. 343 343 |externalDependencies|xs:boolean|The externalDependencies attribute should be set to true if the repository is expected to use external reference URLs in the structural components to retrieve objects on which the referenced object has dependencies. (Thus, if a key family referenced here is being submitted to the repository, and the structure message has URLs which point to the locations of the codelists it uses, then this attribute should be set to true). This should not be provided when this structure is used in a submit structure response. 344 344 345 345 Element Documentation: 346 - 347 347 |**Name**|**Type**|**Documentation** 348 348 |MaintainableObject|com: MaintainableReferenc eType| 349 349 ... ... @@ -350,11 +350,9 @@ 350 350 **SubmitStructureResponseType: **SubmitStructureResponseType describes the structure of a response to a structure submission. For each submitted structure, a Result will be returned. 351 351 352 352 Content: 353 - 354 354 SubmissionResult+ 355 355 356 356 Element Documentation: 357 - 358 358 |**Name**|**Type**|**Documentation** 359 359 |SubmissionResult|SubmissionResultType|SubmissionResult provides a status for each submitted structural object. 360 360 ... ... @@ -361,11 +361,9 @@ 361 361 **SubmissionResultType: **SubmissionResultType provides the status of the structural object submission request. It will identify the object submitted, report back the action requested, and convey the status and any error messages which are relevant to the submission. 362 362 363 363 Content: 364 - 365 365 SubmittedStructure, StatusMessage 366 366 367 367 Element Documentation: 368 - 369 369 |**Name**|**Type**|**Documentation** 370 370 |SubmittedStructure|SubmittedStructureTy pe|SubmittedStructure provides a reference to the submitted structural object and echoes back the action requested for it. 371 371 |StatusMessage|StatusMessageType|StatusMessage provides that status for the submission of the structural object, and if necessary, any error or warning information. ... ... @@ -373,11 +373,9 @@ 373 373 **SubmitSubscriptionsRequestType: **SubmitSubscriptionsRequestType defines the payload of a request message used to submit addtions, updates, or deletions of subscriptions. Subscriptions are submitted to the registry to subscribe to registration and change events for specific registry resources. 374 374 375 375 Content: 376 - 377 377 SubscriptionRequest+ 378 378 379 379 Element Documentation: 380 - 381 381 |**Name**|**Type**|**Documentation** 382 382 |SubscriptionRequest|SubscriptionRequestT ype| 383 383 ... ... @@ -384,7 +384,6 @@ 384 384 **SubscriptionType: **SubscriptionType describes the details of a subscription to a registration or change event for registry resources. When it occurs as the content of a response message, the registry URN must be provide, unless the response is a failure notification for the creation of a new subscription. 385 385 386 386 Content: 387 - 388 388 Organisation, RegistryURN?, NotificationMailTo*, NotificationHTTP*, SubscriberAssignedID?, ValidityPeriod, EventSelector 389 389 390 390 Element Documentation: ... ... @@ -401,20 +401,16 @@ 401 401 **SubscriptionRequestType: **SubscriptionRequestType describes the structure of a single subscription request. It contains subscription details and an action field to indicate the action to be taken on the contained subscription. Note that if the action is update or delete, then the registry supplied URN for the subscription must be included. 402 402 403 403 Attributes: 404 - 405 405 action 406 406 407 407 Content: 408 - 409 409 Subscription 410 410 411 411 Attribute Documentation: 412 - 413 413 |**Name**|**Type**|**Documentation** 414 414 |action|com:ActionType|The action attribute indicates whether this is an addition, a modification, or a deletion of a subscription. 415 415 416 416 Element Documentation: 417 - 418 418 |**Name**|**Type**|**Documentation** 419 419 |Subscription|SubscriptionType|Subscription contains the details of the subscription to be added, updated, or deleted. 420 420 ... ... @@ -421,11 +421,9 @@ 421 421 **SubmitSubscriptionsResponseType: **SubmitSubscriptionsResponseType describes the structure of the response to a new subscription submission. A status is provided for each subscription in the request. 422 422 423 423 Content: 424 - 425 425 SubscriptionStatus+ 426 426 427 427 Element Documentation: 428 - 429 429 |**Name**|**Type**|**Documentation** 430 430 |SubscriptionStatus|SubscriptionStatusTy pe|SubscriptionStatus contains information which describes the success or failure of a subscription request, providing any error messages in the event of failure. The statuses should occur in the same order as the requests when responding to a message with multiple subscription requests. If a subscriber-assigned identification for the subscription is provided, it will be returned to allow for accurate matching of the responses to the requests. A registry assigned URN will be returned for any successfully created, updated, or deleted subscription. 431 431 ... ... @@ -432,11 +432,9 @@ 432 432 **SubscriptionStatusType: **SubscriptionStatusType describes the structure a status for a single subscription request. 433 433 434 434 Content: 435 - 436 436 SubscriptionURN?, SubscriberAssignedID?, StatusMessage 437 437 438 438 Element Documentation: 439 - 440 440 |**Name**|**Type**|**Documentation** 441 441 |SubscriptionURN|xs:anyURI|SubscriptionURN contains the registry generated URN for the subscription, and will be returned for any successfully created, updated, or deleted subscription. 442 442 |SubscriberAssignedID|com:IDType|SubscriberAssignedID is the id assigned by the subscriber to the subscription. If it existed in the subscription request, it will be returned. ... ... @@ -445,11 +445,9 @@ 445 445 **QuerySubscriptionRequestType: **QuerySubscriptionRequestType describes the structure of a query for subscriptions. Subscriptions for a given organisation may be retrieved. 446 446 447 447 Content: 448 - 449 449 Organisation 450 450 451 451 Element Documentation: 452 - 453 453 |**Name**|**Type**|**Documentation** 454 454 |Organisation|com: OrganisationReferenc eType|Organisation provides a reference to the data consumer for which the subscription details should be returned. 455 455 ... ... @@ -456,11 +456,9 @@ 456 456 **QuerySubscriptionResponseType: **QuerySubscriptionResponseType describes the structure of a subscription query response. A status will describe the success or failure of the request (and provide error or warning messages if necessary). If the query was successful, details of all of the organisation's subscriptions will be provided. 457 457 458 458 Content: 459 - 460 460 StatusMessage, Subscription* 461 461 462 462 Element Documentation: 463 - 464 464 |**Name**|**Type**|**Documentation** 465 465 |StatusMessage|StatusMessageType|StatusMessage provides that status for the query subscription request, and if necessary, any error or warning information. 466 466 |Subscription|SubscriptionType|Subscription contains the details of a subscription for the organisation. This may occur multiple times for each subscription. ... ... @@ -468,11 +468,9 @@ 468 468 **NotifyRegistryEventType: **NotifyRegistryEventType describes the structure a registry notification, in response to a subscription to a registry event. At a minimum, the event time, a reference to the change object, a reference to the underlying subscription triggering the notification, and the action that took place on the object are sent. In addition, the full details of the object may be provided at the discretion of the registry. In the event that the details are not sent, it will be possible to query for the details of the changed object using the reference provided. 469 469 470 470 Content: 471 - 472 472 EventTime, (ObjectURN | RegistrationID), SubscriptionURN, EventAction, (StructuralEvent | RegistrationEvent)? 473 473 474 474 Element Documentation: 475 - 476 476 |**Name**|**Type**|**Documentation** 477 477 |EventTime|xs:dateTime|EventTime specifies the time of the triggering event. 478 478 |ObjectURN|xs:anyURI|ObjectURN provides the URN of the object on which the event occurred, unless the event is related to a registration, in which case the RegistrationID element should be used. ... ... @@ -485,19 +485,16 @@ 485 485 **NotificationURLType: **NotificationURLType describes the structure of an http or email address. The content holds the addresses while an attribute indicates whether or not is expects the contents in a SOAP message. 486 486 487 487 Derivation: 429 +* xs:anySimpleType (restriction) 430 +** xs:anyURI (extension) 431 +*** NotificationURLType 488 488 489 -xs:anySimpleType (restriction) 490 - [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] xs:anyURI (extension) 491 - [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] NotificationURLType 492 - 493 493 Attributes: 494 - 495 495 isSOAP? 496 496 497 497 Content: 498 498 499 499 Attribute Documentation: 500 - 501 501 |**Name**|**Type**|**Documentation** 502 502 |isSOAP (default: false)|xs:boolean|The isSOAP attribute, if true, indicates the provided URL expects the notification to be sent in a SOAP message. 503 503 ... ... @@ -504,11 +504,9 @@ 504 504 **ValidityPeriodType: **ValidityPeriodType specifies inclusive start and end-dates for the subscription period. 505 505 506 506 Content: 507 - 508 508 StartDate, EndDate 509 509 510 510 Element Documentation: 511 - 512 512 |**Name**|**Type**|**Documentation** 513 513 |StartDate|xs:date|StartDate is an inclusive start date for the subscription. 514 514 |EndDate|xs:date|EndDate is an inclusive end date for the subscription. ... ... @@ -516,11 +516,9 @@ 516 516 **EventSelectorType: **EventSelectorType describes the details of the events for a subscription. It allows subscribers to specify registry and repository events for which they wish to receive notifications. 517 517 518 518 Content: 519 - 520 520 (StructuralRepositoryEvents | DataRegistrationEvents | MetadataRegistrationEvents)[1..3] 521 521 522 522 Element Documentation: 523 - 524 524 |**Name**|**Type**|**Documentation** 525 525 |StructuralRepository Events|StructuralRepository EventsType|StructuralRepositoryEvents details structural events for the subscription. 526 526 |DataRegistrationEven ts|DataRegistrationEven tsType|DataRegistrationEvents details the data registration events for the subscription. ... ... @@ -529,20 +529,16 @@ 529 529 **StructuralRepositoryEventsType: **StructuralRepositoryEventsType details the structural events for the subscription. At least one maintenance agency must be specified, although it may be given a wildcard value (meaning the subscription is for the structural events of all agencies). This can also be a list of agencies to allow the subscription to subscribe the events of more than one agency. It should be noted that when doing so, all of the subsequent objects are assumed to apply to every agency in the list. The subscription is then refined by detailing the structural objects maintained by the agency for which the subscription should apply. It is possible to explicitly select all object events, all objects of given types, or to individually list out specific objects. Note that for any object, it is also possible to provide an explicit URN to reference a distinct object. In this case, the reference to maintenance agency described above is ignored. Although it is not required, if specific objects are being referenced by explicit URNs, it is good practice to list the agencies. 530 530 531 531 Attributes: 532 - 533 533 TYPE? 534 534 535 535 Content: 536 - 537 537 AgencyID+, (AllEvents | (AgencyScheme | DataConsmerScheme | DataProviderScheme | OrganisationUnitScheme | Dataflow | Metadataflow | CategoryScheme | Categorisation | Codelist | HierarchicalCodelist | ConceptScheme | MetadataStructureDefinition | KeyFamily | StructureSet | ReportingTaxonomy | Process | AttachmentConstraint | ContentConstraint | ProvisionAgreement | TransformationScheme | NameAliasScheme | NamePersonalisationScheme | RulesetScheme | UserDefinedOperatorScheme)+) 538 538 539 539 Attribute Documentation: 540 - 541 541 |**Name**|**Type**|**Documentation** 542 542 |TYPE (fixed: STRUCTURE)|xs:string|TYPE is a fixed attribute that is used to ensure only of each event selector may be provided, when it is referenced in a uniqueness constraint. 543 543 544 544 Element Documentation: 545 - 546 546 |**Name**|**Type**|**Documentation** 547 547 |AgencyID|NestedIDQueryType|AgencyID specifies a maintenance agency for the object or objects indicated in the other fields. This can be either a specific ID, or a single wildcard character ("%"). A wild card character can be used to select all agencies, allowing a subscription to all events for particular object types. This can occur multiple times to list a of group of maintenance agencies, creating event subscriptions for all of the subsequent objects for each agency in the group. Note that if multiple agencies are supplied, then the wildcard character should not be used for any of them. 548 548 |AllEvents|com:EmptyType|AllEvents creates a subscription to structural events for all structural objects maintained by the agencies referenced. ... ... @@ -574,11 +574,9 @@ 574 574 **IdentifiableObjectEventType: **IdentifiableObjectEventType describes the structure of a reference to an identifiable object's events. Either all instances of the object matching the inherited criteria, a specific instance, or specific instances of the object may be selected. 575 575 576 576 Content: 577 - 578 578 (All | URN | ID) 579 579 580 580 Element Documentation: 581 - 582 582 |**Name**|**Type**|**Documentation** 583 583 |All|com:EmptyType|All subscribes to the events all instances of the containing object meeting the other criteria specified. 584 584 |URN|xs:anyURI|URN subscribes to the events of the specific instance of the object type referenced by this URN. Note that when this field is used, the agency information inherited from the structural repository event container is ignored. ... ... @@ -587,11 +587,9 @@ 587 587 **VersionableObjectEventType: **VersionableObjectEventType describes the structure of a reference to a versionable object's events. Either all instances of the object matching the inherited criteria, a specific instance, or specific instances of the object may be selected. 588 588 589 589 Content: 590 - 591 591 (All | URN | (ID, Version)) 592 592 593 593 Element Documentation: 594 - 595 595 |**Name**|**Type**|**Documentation** 596 596 |All|com:EmptyType|All subscribes to the events all instances of the containing object meeting the other criteria specified. 597 597 |URN|xs:anyURI|URN subscribes to the events of the specific instance of the object type referenced by this URN. Note that when this field is used, the agency information inherited from the structural repository event container is ignored. ... ... @@ -601,20 +601,16 @@ 601 601 **DataRegistrationEventsType: **DataRegistrationEventsType details the data registration events for the subscription. It is possible to subscribe to all data registration events in the repository, or specific events for; single registrations, provision agreements, data providers, data flows, key families, and categories that categorize data flows or key families. 602 602 603 603 Attributes: 604 - 605 605 TYPE? 606 606 607 607 Content: 608 - 609 609 (AllEvents | (RegistrationID | ProvisionAgreement | DataProvider | DataflowReference | KeyFamilyReference | Category)+) 610 610 611 611 Attribute Documentation: 612 - 613 613 |**Name**|**Type**|**Documentation** 614 614 |TYPE (fixed: DATA)|xs:string|TYPE is a fixed attribute that is used to ensure only of each event selector may be provided, when it is referenced in a uniqueness constraint. 615 615 616 616 Element Documentation: 617 - 618 618 |**Name**|**Type**|**Documentation** 619 619 |AllEvents|com:EmptyType|AllEvents subscribes to all data registration events in the repository. 620 620 |RegistrationID|com:IDType|RegistrationID subscribes to all the data registration events for the unique registration referenced. ... ... @@ -627,20 +627,16 @@ 627 627 **MetadataRegistrationEventsType: **MetadataRegistrationEventsType details the metadata registration events for the subscription. It is possible to subscribe to all metadata registration events in the repository, or specific events for; single registrations, provision agreements, data providers, metadata flows, metadata structure definitions, and categories that categorize metadata flows or metadata structure definitions. 628 628 629 629 Attributes: 630 - 631 631 TYPE? 632 632 633 633 Content: 634 - 635 635 (AllEvents | (RegistrationID | ProvisionAgreement | DataProvider | MetadataflowReference | MetadataStructureDefinitionReference | Category)+) 636 636 637 637 Attribute Documentation: 638 - 639 639 |**Name**|**Type**|**Documentation** 640 640 |TYPE (fixed: METADATA)|xs:string|TYPE is a fixed attribute that is used to ensure only of each event selector may be provided, when it is referenced in a uniqueness constraint. 641 641 642 642 Element Documentation: 643 - 644 644 |**Name**|**Type**|**Documentation** 645 645 |AllEvents|com:EmptyType|AllEvents subscribes to all metadata registration events in the repository. 646 646 |RegistrationID|com:IDType|RegistrationID subscribes to all the metadata registration events for the unique registration referenced. ... ... @@ -653,11 +653,9 @@ 653 653 **MaintainableEventType: **MaintainableEventType provides a reference to a maintainable object's event with either the URN of the specific object, or a set of potentially wild-carded reference fields. 654 654 655 655 Content: 656 - 657 657 (URN | Ref) 658 658 659 659 Element Documentation: 660 - 661 661 |**Name**|**Type**|**Documentation** 662 662 |URN|xs:anyURI|URN provides an explicit reference to a single object. 663 663 |Ref|MaintainableQueryTyp e|Ref provides a reference to potentially many object through the use of possible wild-carded reference fields.