Altova Mailing List Archives>Archive Index >xmlschema-dev Archive Home >Recent entries >Thread Prev - Re: [xml-dev] Two Questions - on XML Schema [Thread Next] SV: [xml-dev] Two Questions - on XML SchemaTo: "Michael Kay" <mike@--------.--->, "Rick Jelliffe" <rjelliffe@-------.---.-->, <noah_mendelsohn@--.---.---> Date: 3/10/2006 10:45:00 AM -----Oprindelig meddelelse----- Fra: xmlschema-dev-request@w... [mailto:xmlschema-dev-request@w...]P=E5 vegne af Michael Kay Sendt: 9. marts 2006 16:45 Til: Bryan Rasmussen; 'Rick Jelliffe'; noah_mendelsohn@u... Cc: xmlschema-dev@w... Emne: RE: [xml-dev] Two Questions - on XML Schema >Using two different languages with very different conceptual approaches = to >detecting and reporting validation errors is OK as a pragmatic way of = coping >with today's realities, but it's hard to believe that we can't come up = with >something better. This seems like a reasonable statement, but then it seems just as = reasonable to say that one wants to bind different conceptual approaches together. = There are some arguments on both sides where language design is concerned. >> Dropping syntax is also a benefit. >It's not exactly a benefit to the many people who are already using = that >syntax. I suppose not, do we have any stats on: 1. How many people actually use it 2. How many people have complained about the syntax 3. How many processors implement it correctly I for one know I never use xsd:unique cause it bugs me syntactically. I = seem to remember having seen it mentioned in various naming and design rules = as being disallowed, so that might be an example of community opinion on = it. Cheers, Bryan Rasmussen From rjelliffe@a... Fri Mar 10 08:56:04 2006 Received: from maggie.w3.org ([193.51.20 | ||||||
| Company | Legal | Press | Partners | Careers | Sitemap | Contact Us | Altova Blog | Mobile | Full Site | |||
|
