Single Registry Interface Proposal (ZIP)

[David RR Webber <Gnosis_@compuserve.com>]

The attached is the first draft and example DTD's.

The idea is to create a simple single pair of DTDs
for Requests to the Registry and Responses back.

People can then use this pair to implement whatever
use cases and extended function sets that they
desire.

This is the culmination so far of working on the OASIS
Registry interface and creating an aligned interface
for ebXML.  The ebXML interface is significantly 
simpler than the OASIS.  But it follows the same
information model, which is really cool (since it means
OASIS and ebXML Registries can be interoperable,
and it also means people wanting extended functionality
can potentially setup to an OASIS registry).

Apologies for getting this out late, I've had to fight a
heavy head cold the last two days; no fun.

I will bring 20+ printed copies to Tokyo for those
attending to review.

As we are coming out post-PoC we should be able
to apply lessons learned to the single interface model
here, and make a simple and consistent way to
access Registry.  I've already borrowed heavily from
the earlier work leading up to the PoC - thanks for
everyone's efforts on providing those materials.

My sense is my first draft here needs work to 
polish and get the story consistent and easy to
understand.  My goal was primarily to get the
DTD's as exactly close as I could and clean
and error free.

I look forward to everyones input to these ideas
so far.

Thanks, DW.

RRinterfaceDTDs.ZIP