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.

Hi Uche, all,

Uche Ogbuji wrote:
> 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:
>>>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

I agree. Actually, the reason why the OASIS Open Office schema (as well 
as the OpenOffice.org schema) makes use of namespaces is that it 
includes attributes from other vocabularies, like SVG and XLink. That 
means that even if the new or "own" elements and attributes of the Open 
Office schema would not use namespaces, the schema still would require them.


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