[XML-DEV Mailing List Archive Home] [By Thread] [By Date] [Recent Entries] [Reply To This Message]

Re: RE: Difference between "normalize" and "canonicalize"?

  • From: Richard Salz <rsalz@u...>
  • To: "Costello, Roger L." <costello@m...>
  • Date: Wed, 25 Feb 2009 20:40:30 -0500

Re:  RE: Difference between "normalize" and "canonicalize"?
> 1. Why is the Schema non-normative? 

The minute you write something more than once, especially when two 
different "languages" are used, there is an exceedingly high probability 
that the two items will not be completely equivalent. It's therefore good 
practice to say pick one and say "where they conflict, *this one* wins." 
As in baseball, where "tie goes to the runner."

In standards, it's common to call the lesser thing informative, or 
non-normative.

> 2. What does it mean for the Schema to be non-normative? 

As you said, where they conflict, the prose wins.

> 4. Why are there discrepancies? When will they be resolved? 

I think discrepencies are inherent in the nature of the work.  I'd expect 
conflict resolution to be handled by editorial updates to the specs, 
should the WG be willing to do so. Note that since the schema is 
non-normative, such changes are therefore purely editorial and could be 
handled just through errata or other update mechanism.  In other words, 
this wouldn't be "XSD v 1.2."  Since the schema is only intended to be 
informational, there's probably not a lot of incentive to fix bugs in it.

> 5. When will the Schema become normative? 

Hopefully never.  "Man with two watches never knows what time it is."  Why 
do you think you want that to happen?

> 6. Can someone, outside the W3C, create a normative Schema for XSLT? 

What does it mean to define the normative schema for xslt?  If (when) you 
found a difference between the w3c prose and somebody's xslt which would 
you think is wrong?  The answer is probably "it depends." If my open 
source software provided a different schema for xslt, folks would probably 
fix it. If it was Microsoft, folks would probably live with it (viz., 
browsers and html).

> 7. Or, is creating a Schema for XSLT exclusively within the 
> jurisdiction of the W3C XSLT working group?

That would be the obviously place to start.

        /r$

--
Visiting Member, IBM Academy
STSM, DataPower Chief Programmer
WebSphere DataPower SOA Appliances
http://www.ibm.com/software/integration/datapower/



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


PURCHASE STYLUS STUDIO ONLINE TODAY!

Purchasing Stylus Studio from our online shop is Easy, Secure and Value Priced!

Buy Stylus Studio Now

Download The World's Best XML IDE!

Accelerate XML development with our award-winning XML IDE - Download a free trial today!

Don't miss another message! Subscribe to this list today.
Email
First Name
Last Name
Company
Subscribe in XML format
RSS 2.0
Atom 0.3
 

Stylus Studio has published XML-DEV in RSS and ATOM formats, enabling users to easily subcribe to the list from their preferred news reader application.


Stylus Studio Sponsored Links are added links designed to provide related and additional information to the visitors of this website. they were not included by the author in the initial post. To view the content without the Sponsor Links please click here.

Site Map | Privacy Policy | Terms of Use | Trademarks
Free Stylus Studio XML Training:
W3C Member
Stylus Studio® and DataDirect XQuery ™are products from DataDirect Technologies, is a registered trademark of Progress Software Corporation, in the U.S. and other countries. © 2004-2013 All Rights Reserved.