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

RE: Re: CNet Perma Frosts

• To: 'Michael Good' <musicxml@y...>, "'xml-dev@l...'" <xml-dev@l...>
• Subject: RE: Re: CNet Perma Frosts
• From: "Bullard, Claude L (Len)" <len.bullard@i...>
• Date: Fri, 10 Sep 2004 14:42:13 -0500

A beta of my favorite music editor, Guitar Pro, is there.  Cool.
Music got me into markup.  Nice to see it thriving.

Again, XML does not care.  Namespaces make it care.  There 
should be a policy for the use of force.  Asserted:

a) In mission critical applications that must interoperate 
for the public good, it is better that force be applied top down 
to ensure systems interoperate.  Innovative responses must 
conform to public policy.

b) In systems where innovation is realistically possible and 
there are no real time or near real time requirements for 
interoperation that compromise the public good, force should 
come bottom up from the community of users and vendors.

That the author of the article cannot tell a true history 
of XML or distinguish among the requirements for use of 
force means we still have a long way to go educating 
developers, users, and media pundits about the best 
policies for the lifecycles of markup applications.

len


From: Michael Good [mailto:musicxml@y...]

> Once again, it is the XML Tower of Babble!

And one of the examples in the CNet article, music notation, is not true.
While
there are indeed many music notation XML projects on the Web, all of the
implementations in real products are using MusicXML. This includes the two
market leaders, Finale and Sibelius. And now Finale can read and write
MusicXML
on Macintosh OS X as well as Windows. 

More information on MusicXML is available at:

  http://www.musicxml.org/xml.html

• Prev by Date: Re: CNet Perma Frosts
• Next by Date: derivation by restriction and the use attribute
• Previous by thread: restriction design, inherit processContents="lax" for my namespace
• Next by thread: derivation by restriction and the use attribute
• Index(es):
  • Date
  • Thread