Further info about XKMS and Soap/1.2/1.1

Hi,

Looking at the disposition of comments for the XMLP [1], they
had requested us to make Soap 1.2 the required version over
Soap 1.1 [1]:

--
"Use of SOAP 1.2 is REQUIRED by implementers of this specification. For
near term compatibility with existing tools and infrastructure, SOAP 1.1
MAY be used"
--

This requested only took into account part-2 and it was accepted.
The changes were done. However, even if the commentor didn't ask
it explicitly, this also required a change of wording in part 1,
par. 353. Those changes were not done there, so part 1 says that Soap
1.1 is required and that Soap 1.2 is recommended, while part 2 says that
Soap 1.2 is required and that Soap 1.1 may be used.

Because of this omission, both parts say different things and have
become inconsistent and this has to be fixed.

I've asked for a list of Soap 1.2 current products and evaluation of
the deployment. This can give more technical arguments whether it's
appropriate now to move to 1.2. Also, if any developer in the list
has any known technical or other objections for moving to Soap 1.2,
you should let the WG know by mailing the list.

While talking about this issue, someone suggested that if there's really
an issue for moving on to Soap 1.2, we could change the language that 
says "required, recommended" and instead propose two levels of 
conformance, one to Soap 1.1 and another to Soap 1.2 and reflect this
in our exit criteria.

In all cases, we should fix the inconsistency between part-1 and part-2.

As I'm confident we'll resolve this issue in time, I'm going ahead with the
request to move to CR.

Let's see what's the status of the current XKMS implementations so
that we can take a decision next Wed.

Cheers!

-jose

Received on Friday, 6 February 2004 12:16:08 UTC