Doug,
I believe the specifications, which contain the consensus agreements of the
workgroup, should take precedence over the schema.
IMO, the schema should "implement" the spec without modification. If the
schema is "wrong" an "errata" for the schema should be issued.
Dick Brooks
Systrends, Inc
7855 South River Parkway, Suite 111
Tempe, Arizona 85284
Web: www.systrends.com <http://www.systrends.com>
Phone:480.756.6777,Mobile:205-790-1542,eFax:240-352-0714
-----Original Message-----
From: Doug Bunting [mailto:]
Sent: Tuesday, February 12, 2002 5:38 PM
To: ebXML
Subject: [ebxml-msg] Issue 56: Specification / Schema conflict
resolution
We need to choose a "winner" when (as will inevitably happen) the words of
the
specification disagree with the separate schema instance. My suggestions
make
clear choices rather than leaving things open. Further, we need to choose a
winner our programs can implement without conflicting with a normative
deliverable from our group. We provide a schema that arriving messages will
be checked against before the application even hears about it. Therefore,
it
will win and that must be reflected in our documentation.
thanx,
doug
----------------------------------------------------------------
To subscribe or unsubscribe from this elist use the subscription
manager: <http://lists.oasis-open.org/ob/adm.pl>
