OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

ws-rx message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


Subject: RE: RE: [ws-rx] Mistake in wsp namespace in wsrmp and wsmc


We cancelled our last ballot for errors in the specification that were more minor than an incorrect namespace. Now the Policy CR we are referencing will be out of date by the time RM is up for a member approval ballot. With these two obvious errors I think we risk not passing a member approval ballot for the specifications.

Regretfully I have to change my vote on the current ballot to no.

-----Original Message-----
From: Marc Goodner [mailto:mgoodner@microsoft.com]
Sent: Wednesday, March 14, 2007 8:05 AM
To: Anish Karmarkar; tom@coastin.com
Cc: wsrx; Mary McRae
Subject: RE: [ws-rx] Mistake in wsp namespace in wsrmp and wsmc

This should be fixed before we submit this for a standards approval ballot. It should not be saved for a later errata.

-----Original Message-----
From: Anish Karmarkar [mailto:Anish.Karmarkar@oracle.com]
Sent: Tuesday, March 13, 2007 5:03 PM
To: tom@coastin.com
Cc: wsrx; Mary McRae
Subject: Re: [ws-rx] Mistake in wsp namespace in wsrmp and wsmc

I agree that this can be fixed as an "errata". I'm sure this won't be
the only typo or bug that we'll have to fix.

-Anish
--

Tom Rutt wrote:
> Tom Rutt wrote:
>> both the docs wsrmp and wsmc under cs ballot have a mistake in the
>> namespace for
>> wsp.
> However,  the schema does not use the wsp namespace, and it is used
> only in exemplars of use of the assertion.
>
> Since this is an obvious bug, with an obvious fix, and it is not used
> normatively, I feel it could
> be handled via an errata.
>
> Tom
>>
>> ERROR:   http://www.w3.org/TR/2007/CR-ws-policy-20070228
>> CORRECT: http://www.w3.org/ns/ws-policy
>>
>> Hopefully, if Mary can be present on our call on Thursday, and we can
>> have 2/3 members prsent, we could
>> have a real time CS ballot to fix this error.
>>
>> My colleague Toshi Nishimura discovered this error recently
>>
>
>


[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]