![]() |
![]() | ![]() | ![]() | Altova Mailing List Archives>Archive Index >xmlschema-dev Archive Home >Recent entries >Thread Prev - RE: chairs' summary of XML Schema User Experiences workshop [Thread Next] Re: chairs' summary of XML Schema User Experiences workshopTo: paul.downey@--.--- Date: 7/14/2005 2:07:00 PM On Thu, Jul 14, 2005 at 10:30:58AM +0100, paul.downey@b... 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@v... | Rpmfind RPM search engine http://rpmfind.net/ http://veillard.com/ | From cmsmcq@a... Thu Jul 14 19:18:45 2005 Received: from lisa.w3.org ([128.30 | ![]() | ![]() | ![]() |
| Company | Legal | Press | Partners | Careers | Sitemap | Contact Us | Altova Blog | |||||
|
