-
Notifications
You must be signed in to change notification settings - Fork 2
Iso19135 protocols
der edited this page Nov 9, 2012
·
2 revisions
Procedures are described as a workflow and not designed for automation.
- addition - add an item to a register (starts as notValid until the separate approval process completes then valid)
- clarification - update which does not materially affect the meaning of the item
- supersession - an update which does affect the semantics, results in new item and old one is marked as superseded and linked to the replacement
- retirement - no longer useful and marked as retired but retained in the registry
The process of approval is recorded separately from the item itself (RE_ProposalManagementInformation) which goes through pending, tentative and final states.
In ebXML a submitted-but-not-approved item is visible in the registry but with status showing it is not yet approved. In ISO 19135 such an item (status notValid) is not normally visible to public user.
If a request is rejected then there is separate appeals process.
For UKL the approval process will be separated but the registry itself but the registry may need to support reporting of approval progress?