OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help

office-comment message

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

Subject: Re: [office-comment] Section 1.5 - implementations SHOULD use thenamespace prefixes given.

On Mon, 2004-10-25 at 09:03, David Faure wrote:
> On Monday 25 October 2004 16:53, Michael Brauer - Sun Germany - ham02 - Hamburg wrote:
> > David,
> > 
> > do you know an application that actually could be able to support the 
> > OASIS Open Office format, but does not support namespaces?
> Yes - KOffice :-)
> We currently look for "office:styles" etc., not for "the element named prefix:styles
> where prefix was associated with urn:oasis:names:tc:openoffice:xmlns:office:1.0",
> as proper namespace support would mandate.
> This is due to the lack of namespace support in Qt's DOM implementation.
> And I believe that doing it by hand in KOffice itself would make the reading much slower.
> So I would actually like it very much if the specification could request that
> the given prefixes are used by everyone.
> I also assumed that many hand-made scripts relied on the current prefixes,
> but I have no proof of that.

I appreciate this implementation difficulty (I assume Qt DOM is purely
1.0, then), but I really think it's a bad idea to abuse the namespace
REC by mandating prefixes.  A suggestion of prefix is OK, but not a
mandate.  Namespaces are far from perfect, but if we claim to use them,
we should use them rightly.  Otherwise just leave off using namespaces
entiry.  After all, how likely is anyone to embed OOXML within other
vocabularies?  We could stipulate that extension and foreign elements
*within* OOXML should be in namespaces, and that simply means that
implementations that do not support namespaces will not support
extensions, which is probably a fair compromise.

I also agree with Michael that disallowing people from using the default
namespace will result in needless space bloat across the board.  I'd
certainly prefer my OOXML application to use 

<styles xmlns="urn:oasis:names:tc:openoffice:xmlns:office:1.0">...

rather than


Uche Ogbuji                                    Fourthought, Inc.
http://uche.ogbuji.net    http://4Suite.org    http://fourthought.com
A hands-on introduction to ISO Schematron - http://www-106.ibm.com/developerworks/edu/x-dw-xschematron-i.html
Schematron abstract patterns - http://www.ibm.com/developerworks/xml/library/x-stron.html
Wrestling HTML (using Python) - http://www.xml.com/pub/a/2004/09/08/pyxml.html
Enterprise data goes high fashion - http://www.adtmag.com/article.asp?id=10061
Principles of XML design: Considering container elements - http://www-106.ibm.com/developerworks/xml/library/x-contain.html
Hacking XML Hacks - http://www-106.ibm.com/developerworks/xml/library/x-think26.html
A survey of XML standards - http://www-106.ibm.com/developerworks/xml/library/x-stand4/

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