W3C home > Mailing lists > Public > xmlschema-dev@w3.org > July 2005

Re: chairs' summary of XML Schema User Experiences workshop

From: Daniel Veillard <daniel@veillard.com>
Date: Thu, 14 Jul 2005 12:07:11 +0200
To: paul.downey@bt.com
Cc: mcham@microsoft.com, cmsmcq@acm.org, xmlschema-dev@w3.org
Message-ID: <20050714100711.GE29991@daniel.veillard.com>

On Thu, Jul 14, 2005 at 10:30:58AM +0100, paul.downey@bt.com wrote:
> There was interest that the Working Group should spend more time processing
> errata and test cases, but concerns were raised at which companies would actually
> 'put bums on seats', providing resource to continue to debug 1.0 instead of 
> working on 1.1.

  My take on this, I may be off base, but here it is.

  You have a resource problem over what is a specialist and hard job,
it's not surprizing. On the other hand the way that job is done is really
confined to a subgroup with little interaction with the end users (which
is also a very specialized group, but larger). Yes the process outlined in

  http://www.w3.org/XML/2004/xml-schema-test-suite/XMLSchemaTS-Process.html

feels like it should be open and lively as described, but watching the
mailing list archive, it seems nothing is happening there basically

  http://lists.w3.org/Archives/Public/public-xml-schema-testsuite/

right ? 

  Open the process, you have scarce resources, the people working on this
will be very specialized and a small group anyway, the problem you have 
is not that corp A and corp B disagree on whether test1234 is right or not,
the problem is that nobody is reporting the errors for test1234, or if 
such an error is reported nobody seems to answer. You seems not able to 
get a lot of corporate to sponsor dedicated staff time to work on it, so
tap in a lighter more open contribution model. If you can get to the point
where any implementor can post a message to the list and get feedback from
either another implementor or someone from the working group within 24
hours, then you will get the basis to make it a useful tool for all parties
and the progresses toward a more complete and debugged testsuite are likely
to follow. 
  Basically making it a list based maintenance instead of a commity
  based maintainance project may change the status quo, at least it
  is worth trying.

  my 2 euro cents,

Daniel

-- 
Daniel Veillard      | libxml Gnome XML XSLT toolkit  http://xmlsoft.org/
daniel@veillard.com  | Rpmfind RPM search engine http://rpmfind.net/
http://veillard.com/ | 
Received on Thursday, 14 July 2005 10:07:07 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 11 January 2011 00:14:50 GMT