xml-dev - RE: Bad use of XML ?

[Eldar Musayev <eldarm@microsoft.com>]

So, what's the problem? It's not custom XML, it's XML application,
MS Media Player uses this application, and it's not quite general
data, but data very specific to this particular application. They
are not supposed to be subject for automated transfer in B2B
multi-tier systems, right? That's what makes XML attractive in the 
first place. You have simple text format for your custom data
and don't care if W3 approved your use of it or not (with _HTML_ it was
different).
Schemas, schemas registration etc. has their place, 
but not here. Or would you prefer Media Player to save these data in
proprietary binary format? :-)

Best wishes, Eldar Musayev

 > -----Original Message-----
 > From: ashvil@i3connect.com [mailto:ashvil@i3connect.com]
 > Sent: Friday, March 31, 2000 11:15 AM
 > To: xml-dev@xml.org
 > Subject: Bad use of XML ? 
 > 
 > 
 > The new MS Media Player 7 uses XML for skins.
 > http://msdn.microsoft.com/workshop/imedia/windowsmedia/wmpski
 > ns.asp#wmpskins
 > _creating
 > 
 > Sample Theme file
 > <THEME>
 >    <VIEW
 >       clippingColor = "#CCCC00"
 >       backgroundImage = "background.bmp"
 >       titleBar = "false">
 > 
 >       <BUTTONGROUP
 >          mappingImage = "map.bmp"
 >          hoverImage = "hover.bmp">
 > 
 >       <PLAYELEMENT
 >          mappingColor = "#00FF00" />
 > 
 >       <STOPELEMENT
 >          mappingColor = "#FF0000" />
 > 
 >       </BUTTONGROUP>
 > 
 >    </VIEW>
 > </THEME>
 > 
 > There are two ways of looking at this
 > 1. This is Bad and will encourage every one to come up with 
 > their own flavor
 > of XML. XHTML should have been used to describe Skins and 
 > any other UI
 > standards.
 > If Skins require more than what XHTML currently provides, then that
 > functionality needs to be added as an XHTML module. etc...
 > 
 > 2. This is good. It allows developers to focus on the task 
 > of creating the
 > Theme using simple tags (and not having to learn XHTML). 
 > XSLT could then be
 > used to convert this into XHTML. etc...
 > 
 > Counter point to 2.
 > If the focus is to hide the developers from XHTML, then a 
 > visual XHTML tool
 > could be used to generate XHTML directly. etc...
 > 
 > ....
 > 
 > What do other list members think of everyone generating 
 > their own XML file
 > format to represent common data, in this case the data is 
 > visual data. Or is
 > this a small issue due to tools like XSLT ?
 > 
 > Thx,
 > Ashvil
 > 
 > 
 > 
 > 
 > 
 > 
 > 
 > 
 > *************************************************************
 > **************
 > This is xml-dev, the mailing list for XML developers.
 > To unsubscribe, mailto:majordomo@xml.org&BODY=unsubscribe%20xml-dev
 > List archives are available at http://xml.org/archives/xml-dev/
 > *************************************************************
 > **************
 > 

***************************************************************************
This is xml-dev, the mailing list for XML developers.
To unsubscribe, mailto:majordomo@xml.org&BODY=unsubscribe%20xml-dev
List archives are available at http://xml.org/archives/xml-dev/
***************************************************************************