Joe,
Actually DRIve is using the XMLG registry that supports the V2.0
spec's right now.
This may be a vendor issue of course - since URLs are stored
'as is' and not as relative URLs, (where the server address is
a parameter). This can cause issues when moving content
across servers - but we'd need clarification of the restriction.
Thanks, DW.
=============================================================
Message text written by Chiusano Joseph
>
Regarding "Persistent locations in registries (DRIve)":
Since DRIve (http://www.disa.org/drive/index.html) is an ebXML 1.0 (RS
and RIM) implementation, I believe this would simply come back to our
Registry specifications. 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<
