Skip to Content
Last modified by Artur on 2025/09/10 11:19
From version 2.3
edited by Helena
on 2025/06/26 14:13
Change comment: There is no comment for this version
To version 2.2
edited by Helena
on 2025/06/26 14:10
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -134,17 +134,21 @@
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
140 140  
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 +
141 141  Attributes:
143 +
142 142  id?, version?, agencyID?
143 143  
144 144  Content:
147 +
145 145  {Empty}
146 146  
147 147  Attribute Documentation:
151 +
148 148  |**Name**|**Type**|**Documentation**
149 149  |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.
150 150  |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.
... ... @@ -153,16 +153,20 @@
153 153  **StatusMessageType: **StatusMessageType carries the text of error messages and/or warnings in response to queries or requests.
154 154  
155 155  Attributes:
160 +
156 156  status
157 157  
158 158  Content:
164 +
159 159  MessageText*
160 160  
161 161  Attribute Documentation:
168 +
162 162  |**Name**|**Type**|**Documentation**
163 163  |status|StatusType|The status attribute carries the status of the query or request.
164 164  
165 165  Element Documentation:
173 +
166 166  |**Name**|**Type**|**Documentation**
167 167  |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.
168 168  
... ... @@ -169,9 +169,11 @@
169 169  **SubmitRegistrationsRequestType: **SubmitRegistrationsRequestType defines the payload of a request message used to submit addtions, updates, or deletions of data/metadata set registrations.
170 170  
171 171  Content:
180 +
172 172  RegistrationRequest+
173 173  
174 174  Element Documentation:
184 +
175 175  |**Name**|**Type**|**Documentation**
176 176  |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.
177 177  
... ... @@ -178,16 +178,20 @@
178 178  **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.
179 179  
180 180  Attributes:
191 +
181 181  action
182 182  
183 183  Content:
195 +
184 184  Registration
185 185  
186 186  Attribute Documentation:
199 +
187 187  |**Name**|**Type**|**Documentation**
188 188  |action|com:ActionType|The action attribute indicates whether this is an addition, a modification, or a deletion of a registration.
189 189  
190 190  Element Documentation:
204 +
191 191  |**Name**|**Type**|**Documentation**
192 192  |Registration|RegistrationType|Registration contains the details of the data/metadata set registration to be added, updated, or deleted.
193 193  
... ... @@ -194,9 +194,11 @@
194 194  **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.
195 195  
196 196  Content:
211 +
197 197  RegistrationStatus+
198 198  
199 199  Element Documentation:
215 +
200 200  |**Name**|**Type**|**Documentation**
201 201  |RegistrationStatus|RegistrationStatusTy pe|RegistrationStatus provided the status details for the submitted registration. It echoes the original submission and provides status information about the request.
202 202  
... ... @@ -203,9 +203,11 @@
203 203  **RegistrationStatusType: **RegistrationStatusType describes the structure of a registration status.
204 204  
205 205  Content:
222 +
206 206  Registration, StatusMessage
207 207  
208 208  Element Documentation:
226 +
209 209  |**Name**|**Type**|**Documentation**
210 210  |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.
211 211  |StatusMessage|StatusMessageType|StatusMessage provides that status for the registration request, and if necessary, any error or warning information.
... ... @@ -213,16 +213,20 @@
213 213  **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.
214 214  
215 215  Attributes:
234 +
216 216  returnConstraints?
217 217  
218 218  Content:
238 +
219 219  QueryType, (All | ProvisionAgreement | DataProvider | Dataflow | Metadataflow), ReferencePeriod?, (DataKeySet | MetadataKeySet | CubeRegion | MetadataTargetRegion)*
220 220  
221 221  Attribute Documentation:
242 +
222 222  |**Name**|**Type**|**Documentation**
223 223  |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.
224 224  
225 225  Element Documentation:
247 +
226 226  |**Name**|**Type**|**Documentation**
227 227  |QueryType|QueryTypeType|QueryType defines the type of sets (data, metadata, or both) that are being queried for.
228 228  |All|com:EmptyType|All indicates that all registrations meeting the other criteria of the query should be returned.
... ... @@ -239,9 +239,11 @@
239 239  **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.
240 240  
241 241  Content:
264 +
242 242  StatusMessage, QueryResult*
243 243  
244 244  Element Documentation:
268 +
245 245  |**Name**|**Type**|**Documentation**
246 246  |StatusMessage|StatusMessageType|StatusMessage provides that status for the registration query request, and if necessary, any error or warning information.
247 247  |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.
... ... @@ -249,16 +249,20 @@
249 249  **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.
250 250  
251 251  Attributes:
276 +
252 252  timeSeriesMatch
253 253  
254 254  Content:
280 +
255 255  (DataResult | MetadataResult)
256 256  
257 257  Attribute Documentation:
284 +
258 258  |**Name**|**Type**|**Documentation**
259 259  |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.
260 260  
261 261  Element Documentation:
289 +
262 262  |**Name**|**Type**|**Documentation**
263 263  |DataResult|ResultType|
264 264  |MetadataResult|ResultType|
... ... @@ -266,9 +266,11 @@
266 266  **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.
267 267  
268 268  Content:
297 +
269 269  Registration, ContentConstraint*
270 270  
271 271  Element Documentation:
301 +
272 272  |**Name**|**Type**|**Documentation**
273 273  |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.
274 274  |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.
... ... @@ -276,17 +276,21 @@
276 276  **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.
277 277  
278 278  Attributes:
309 +
279 279  action?, externalDependencies?
280 280  
281 281  Content:
313 +
282 282  (StructureLocation | str:Structures), SubmittedStructure*
283 283  
284 284  Attribute Documentation:
317 +
285 285  |**Name**|**Type**|**Documentation**
286 286  |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.
287 287  |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.
288 288  
289 289  Element Documentation:
323 +
290 290  |**Name**|**Type**|**Documentation**
291 291  |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.
292 292  |str:Structures|str:StructuresType|Structures allows for the inline definition of structural components for submission.
... ... @@ -295,17 +295,21 @@
295 295  **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.
296 296  
297 297  Attributes:
332 +
298 298  action?, externalDependencies?
299 299  
300 300  Content:
336 +
301 301  MaintainableObject
302 302  
303 303  Attribute Documentation:
340 +
304 304  |**Name**|**Type**|**Documentation**
305 305  |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.
306 306  |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.
307 307  
308 308  Element Documentation:
346 +
309 309  |**Name**|**Type**|**Documentation**
310 310  |MaintainableObject|com: MaintainableReferenc eType|
311 311  
... ... @@ -312,9 +312,11 @@
312 312  **SubmitStructureResponseType: **SubmitStructureResponseType describes the structure of a response to a structure submission. For each submitted structure, a Result will be returned.
313 313  
314 314  Content:
353 +
315 315  SubmissionResult+
316 316  
317 317  Element Documentation:
357 +
318 318  |**Name**|**Type**|**Documentation**
319 319  |SubmissionResult|SubmissionResultType|SubmissionResult provides a status for each submitted structural object.
320 320  
... ... @@ -321,9 +321,11 @@
321 321  **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.
322 322  
323 323  Content:
364 +
324 324  SubmittedStructure, StatusMessage
325 325  
326 326  Element Documentation:
368 +
327 327  |**Name**|**Type**|**Documentation**
328 328  |SubmittedStructure|SubmittedStructureTy pe|SubmittedStructure provides a reference to the submitted structural object and echoes back the action requested for it.
329 329  |StatusMessage|StatusMessageType|StatusMessage provides that status for the submission of the structural object, and if necessary, any error or warning information.
... ... @@ -331,9 +331,11 @@
331 331  **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.
332 332  
333 333  Content:
376 +
334 334  SubscriptionRequest+
335 335  
336 336  Element Documentation:
380 +
337 337  |**Name**|**Type**|**Documentation**
338 338  |SubscriptionRequest|SubscriptionRequestT ype|
339 339  
... ... @@ -340,6 +340,7 @@
340 340  **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.
341 341  
342 342  Content:
387 +
343 343  Organisation, RegistryURN?, NotificationMailTo*, NotificationHTTP*, SubscriberAssignedID?, ValidityPeriod, EventSelector
344 344  
345 345  Element Documentation:
... ... @@ -356,16 +356,20 @@
356 356  **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.
357 357  
358 358  Attributes:
404 +
359 359  action
360 360  
361 361  Content:
408 +
362 362  Subscription
363 363  
364 364  Attribute Documentation:
412 +
365 365  |**Name**|**Type**|**Documentation**
366 366  |action|com:ActionType|The action attribute indicates whether this is an addition, a modification, or a deletion of a subscription.
367 367  
368 368  Element Documentation:
417 +
369 369  |**Name**|**Type**|**Documentation**
370 370  |Subscription|SubscriptionType|Subscription contains the details of the subscription to be added, updated, or deleted.
371 371  
... ... @@ -372,9 +372,11 @@
372 372  **SubmitSubscriptionsResponseType: **SubmitSubscriptionsResponseType describes the structure of the response to a new subscription submission. A status is provided for each subscription in the request.
373 373  
374 374  Content:
424 +
375 375  SubscriptionStatus+
376 376  
377 377  Element Documentation:
428 +
378 378  |**Name**|**Type**|**Documentation**
379 379  |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.
380 380  
... ... @@ -381,9 +381,11 @@
381 381  **SubscriptionStatusType: **SubscriptionStatusType describes the structure a status for a single subscription request.
382 382  
383 383  Content:
435 +
384 384  SubscriptionURN?, SubscriberAssignedID?, StatusMessage
385 385  
386 386  Element Documentation:
439 +
387 387  |**Name**|**Type**|**Documentation**
388 388  |SubscriptionURN|xs:anyURI|SubscriptionURN contains the registry generated URN for the subscription, and will be returned for any successfully created, updated, or deleted subscription.
389 389  |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.
... ... @@ -392,9 +392,11 @@
392 392  **QuerySubscriptionRequestType: **QuerySubscriptionRequestType describes the structure of a query for subscriptions. Subscriptions for a given organisation may be retrieved.
393 393  
394 394  Content:
448 +
395 395  Organisation
396 396  
397 397  Element Documentation:
452 +
398 398  |**Name**|**Type**|**Documentation**
399 399  |Organisation|com: OrganisationReferenc eType|Organisation provides a reference to the data consumer for which the subscription details should be returned.
400 400  
... ... @@ -401,9 +401,11 @@
401 401  **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.
402 402  
403 403  Content:
459 +
404 404  StatusMessage, Subscription*
405 405  
406 406  Element Documentation:
463 +
407 407  |**Name**|**Type**|**Documentation**
408 408  |StatusMessage|StatusMessageType|StatusMessage provides that status for the query subscription request, and if necessary, any error or warning information.
409 409  |Subscription|SubscriptionType|Subscription contains the details of a subscription for the organisation. This may occur multiple times for each subscription.
... ... @@ -411,9 +411,11 @@
411 411  **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.
412 412  
413 413  Content:
471 +
414 414  EventTime, (ObjectURN | RegistrationID), SubscriptionURN, EventAction, (StructuralEvent | RegistrationEvent)?
415 415  
416 416  Element Documentation:
475 +
417 417  |**Name**|**Type**|**Documentation**
418 418  |EventTime|xs:dateTime|EventTime specifies the time of the triggering event.
419 419  |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.
... ... @@ -426,16 +426,19 @@
426 426  **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.
427 427  
428 428  Derivation:
429 -* xs:anySimpleType (restriction)
430 -** xs:anyURI (extension)
431 -*** NotificationURLType
432 432  
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 +
433 433  Attributes:
494 +
434 434  isSOAP?
435 435  
436 436  Content:
437 437  
438 438  Attribute Documentation:
500 +
439 439  |**Name**|**Type**|**Documentation**
440 440  |isSOAP (default: false)|xs:boolean|The isSOAP attribute, if true, indicates the provided URL expects the notification to be sent in a SOAP message.
441 441  
... ... @@ -442,9 +442,11 @@
442 442  **ValidityPeriodType: **ValidityPeriodType specifies inclusive start and end-dates for the subscription period.
443 443  
444 444  Content:
507 +
445 445  StartDate, EndDate
446 446  
447 447  Element Documentation:
511 +
448 448  |**Name**|**Type**|**Documentation**
449 449  |StartDate|xs:date|StartDate is an inclusive start date for the subscription.
450 450  |EndDate|xs:date|EndDate is an inclusive end date for the subscription.
... ... @@ -452,9 +452,11 @@
452 452  **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.
453 453  
454 454  Content:
519 +
455 455  (StructuralRepositoryEvents | DataRegistrationEvents | MetadataRegistrationEvents)[1..3]
456 456  
457 457  Element Documentation:
523 +
458 458  |**Name**|**Type**|**Documentation**
459 459  |StructuralRepository Events|StructuralRepository EventsType|StructuralRepositoryEvents details structural events for the subscription.
460 460  |DataRegistrationEven ts|DataRegistrationEven tsType|DataRegistrationEvents details the data registration events for the subscription.
... ... @@ -463,16 +463,20 @@
463 463  **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.
464 464  
465 465  Attributes:
532 +
466 466  TYPE?
467 467  
468 468  Content:
536 +
469 469  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)+)
470 470  
471 471  Attribute Documentation:
540 +
472 472  |**Name**|**Type**|**Documentation**
473 473  |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.
474 474  
475 475  Element Documentation:
545 +
476 476  |**Name**|**Type**|**Documentation**
477 477  |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.
478 478  |AllEvents|com:EmptyType|AllEvents creates a subscription to structural events for all structural objects maintained by the agencies referenced.
... ... @@ -504,9 +504,11 @@
504 504  **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.
505 505  
506 506  Content:
577 +
507 507  (All | URN | ID)
508 508  
509 509  Element Documentation:
581 +
510 510  |**Name**|**Type**|**Documentation**
511 511  |All|com:EmptyType|All subscribes to the events all instances of the containing object meeting the other criteria specified.
512 512  |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.
... ... @@ -515,9 +515,11 @@
515 515  **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.
516 516  
517 517  Content:
590 +
518 518  (All | URN | (ID, Version))
519 519  
520 520  Element Documentation:
594 +
521 521  |**Name**|**Type**|**Documentation**
522 522  |All|com:EmptyType|All subscribes to the events all instances of the containing object meeting the other criteria specified.
523 523  |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.
... ... @@ -527,16 +527,20 @@
527 527  **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.
528 528  
529 529  Attributes:
604 +
530 530  TYPE?
531 531  
532 532  Content:
608 +
533 533  (AllEvents | (RegistrationID | ProvisionAgreement | DataProvider | DataflowReference | KeyFamilyReference | Category)+)
534 534  
535 535  Attribute Documentation:
612 +
536 536  |**Name**|**Type**|**Documentation**
537 537  |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.
538 538  
539 539  Element Documentation:
617 +
540 540  |**Name**|**Type**|**Documentation**
541 541  |AllEvents|com:EmptyType|AllEvents subscribes to all data registration events in the repository.
542 542  |RegistrationID|com:IDType|RegistrationID subscribes to all the data registration events for the unique registration referenced.
... ... @@ -549,16 +549,20 @@
549 549  **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.
550 550  
551 551  Attributes:
630 +
552 552  TYPE?
553 553  
554 554  Content:
634 +
555 555  (AllEvents | (RegistrationID | ProvisionAgreement | DataProvider | MetadataflowReference | MetadataStructureDefinitionReference | Category)+)
556 556  
557 557  Attribute Documentation:
638 +
558 558  |**Name**|**Type**|**Documentation**
559 559  |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.
560 560  
561 561  Element Documentation:
643 +
562 562  |**Name**|**Type**|**Documentation**
563 563  |AllEvents|com:EmptyType|AllEvents subscribes to all metadata registration events in the repository.
564 564  |RegistrationID|com:IDType|RegistrationID subscribes to all the metadata registration events for the unique registration referenced.
... ... @@ -571,9 +571,11 @@
571 571  **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.
572 572  
573 573  Content:
656 +
574 574  (URN | Ref)
575 575  
576 576  Element Documentation:
660 +
577 577  |**Name**|**Type**|**Documentation**
578 578  |URN|xs:anyURI|URN provides an explicit reference to a single object.
579 579  |Ref|MaintainableQueryTyp e|Ref provides a reference to potentially many object through the use of possible wild-carded reference fields.