Re: [xml-dev] What should be open/free? (Was: Low-end Office 11 won't do user...

> Implicitly, it seems to me that by putting "our" data into a data container 
> which belongs to Microsoft (as it happens to be in this case) we are creating 
> what I (provocatively?) might term "jointly owned data". The data, held in 
> Microsoft format, has more value (to us, to our customers) than raw data.

ROTFL.  This is one of those crazy ideas that does not even require an 
additional word to rubbish.  Of course, I can imagine MSFT's having the Dali 
lightbulb go off over their heads and trying to slip this one onto their next 
EULA.  That would just make me laugh all the harder.



-- 
Uche Ogbuji                                    Fourthought, Inc.
http://uche.ogbuji.net    http://4Suite.org    http://fourthought.com
Gems From the [Python/XML] Archives - http://www.xml.com/pub/a/2003/04/09/py-xm
l.html
Introducing N-Triples - http://www-106.ibm.com/developerworks/xml/library/x-thi
nk17/index.html
Use internal references in XML vocabularies - http://www-106.ibm.com/developerw
orks/xml/library/x-tipvocab.html
EXSLT by example - http://www-106.ibm.com/developerworks/library/x-exslt.html
The worry about program wizards - http://www.adtmag.com/article.asp?id=7238
Use rdf:about and rdf:ID effectively in RDF/XML - http://www-106.ibm.com/develo
perworks/xml/library/x-tiprdfai.html