XML.orgXML.org
FOCUS AREAS |XML-DEV |XML.org DAILY NEWSLINK |REGISTRY |RESOURCES |ABOUT
OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index]
Re: [xml-dev] What techniques do you employ to ensure that your datais precisely and unambiguously specified?

Roger--

It should be obvious that your examples don't contradict what Michael said.  How do you know that, if the W3C should manage to come up with a shorter (but just as adequate;  and how do you measure that?) specification for XML Schema 1.1, more people wouldn't read it?  

On Sep 24, 2012, at 3:08 PM, Costello, Roger L. wrote:

> Michael Kay wrote:
> 
>> Being too careful can make things worse, because the longer and more 
>> formal the spec, the fewer people will read it.
> 
> Apparently the W3C does not agree.  Consider:
> 
>      - The XML Schema 1.1 specification is 380 pages
>         and  is formally written.
> 
>      - The XSLT 3.0 specification is 530 pages
>        and  is formally written.
> 
> 
> /Roger
> 



[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index]


News | XML in Industry | Calendar | XML Registry
Marketplace | Resources | MyXML.org | Sponsors | Privacy Statement

Copyright 1993-2007 XML.org. This site is hosted by OASIS