<Joe>
It's not clear to me what the exact question is - it may be related to the
"URI for RegistryObject" question that was already answered. Is there any
more information that we can/should have?
</Joe>
<Nicholas>
That question was mine, addressed to Alan Kotok at his presentation of the
DRIve registry. He indicated that this registry did not contain a
repository, and that any URLs pointing to artifacts (referred to in a
database record) simply pointed elsewhere.
...
</Nicholas>
Specs define lifecycle of RegistryObjects and who, when, how, ...can create,
update, remove, ... If this is a particular case of modeling (using)
ExternalLink URIs (content that is not managed by the Registry), then RIM
2.33 / Section 7.11.2 / Lines 813-816 says:
<snip>
Each ExternalLink instance must have an externalURI attribute defined. The
externalURI attribute provides a URI to the external resource pointed to by
this ExternalLink instance. If the URI is a URL then a registry must
validate the URL to be resolvable at the time of submission before accepting
an ExternalLink submission to the registry
</snip>
IMO, this is enough; managing content under the externalURI shouldn't be the
responsibility of the Registry.
Nikola
