Title: Message
Shishir,
Thanks
for the details on ASN.1.
However, adding a notation alternative to XML
Schema and a protocol alternative to SOAP/HTTP to the set of UDDI Version 2
specifications at this point in time seems not to be appropriate to me. There
are other schema notations, such as RELAX NG, and other protocols, such as HTTP
w/o SOAP, we could also consider, but we always limited our scope to the most
common ones so far.
I'm
not saying that it is not useful to propose alternatives, but
since alternative schema notations and protocols should note change
UDDI's core, I'd rather like to see them added layered on top of the UDDI
specifications, for example, by starting with a technical
note.
Also,
since we are also in the process to finalize UDDI Version 3, any alternatives
should also work with this version. The issue with the mapping of W3C XML
Digital Signatures to ASN.1 that came up yesterday should be one of the first
items to be resolved in a Technical Note.
Regards,
Claus
-----Original Message-----
From: GARG
Shishir / FTR&D / US [mailto:]
Sent: Mittwoch, 5. M酺z 2003 02:55
To:
''
Cc: DUBUISSON Olivier FTRD/DTL/LAN;
'Rajul Gupta'; 'Paul Thorpe'; 'Bancroft Scott'; 'Alexandru Czimbor'; CAHUZAC
Maud / FTR&D / US
Subject: [uddi-spec] ASN.1 notation as an
alternative to XML Schema proposal
Hello folks,
As discussed briefly on today's call, here are the initial
documents to get the discussion going. The doc file contains a description of
what is in this proposal, along with a few examples to make the case
clear.
We are not necessarily aiming to make it to the V2 specification
(since it was just sent to the OASIS board for review), but we are not sure if
it should just become a Technical Note and be left at that.
Lets look for all the feedback we can get on this
proposal.
Regards,
Shishir GARG.
France Telecom R&D
650.875.1540
Attached: Overview doc + UDDI V2 converted schemas
