Home. 
.

transparent

transparent

transparent

Altova Mailing List Archives


SV: [xml-dev] Two Questions - on XML Schema

From: "Bryan Rasmussen" <BRS@----.-->
To: "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


transparent
Print
Mail
Like It
Disclaimer
.

These Archives are provided for informational purposes only and have been generated directly from the Altova mailing list archive system and are comprised of the lists set forth on www.altova.com/list/index.html. Therefore, Altova does not warrant or guarantee the accuracy, reliability, completeness, usefulness, non-infringement of intellectual property rights, or quality of any content on the Altova Mailing List Archive(s), regardless of who originates that content. You expressly understand and agree that you bear all risks associated with using or relying on that content. Altova will not be liable or responsible in any way for any content posted including, but not limited to, any errors or omissions in content, or for any losses or damage of any kind incurred as a result of the use of or reliance on any content. This disclaimer and limitation on liability is in addition to the disclaimers and limitations contained in the Website Terms of Use and elsewhere on the site.

.
.

transparent

transparent