Martin, this is an excellent start.
I'm thinking about negative tests. In conversation you have said that
MUST NOT statements should be specific about where and when the error is
raised. If we go that far, why don't we specify an error code as well.
This will further improve interoperability.
In some of the WGs I've worked in, people asked for error codes when the
spec got close to finished. We may as well start thinking about this early.
Ashok
Martin Chapman wrote:
>These have no official standing (yet) but might be of help.
>
>Martin.
>
>_________________________________________________________________
>Martin Chapman
>Consulting Member of Technical Staff
>Oracle
>P: +353 87 687 6654
>e:
>
>
>------------------------------------------------------------------------
>
>---------------------------------------------------------------------
>To unsubscribe from this mail list, you must leave the OASIS TC that
>generates this mail. You may a link to this group and all your TCs in OASIS
>at:
>https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php
>
--
All the best, Ashok
