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] OpenDocument 1.2v7-02: 1.3 Namespaces


Dennis E. Hamilton wrote:
> In Document OpenDocument-v1.2-v7-02.odt
> Section 1.3 Namespaces
> There needs to be an indication that the listed prefixes are those used in
> QNames for those namespaces solely for purposes of definiteness in the
> specification.  It is the namespaces that are normative, the prefixes are
> non-normative and used for clarity in the exposition (I would say).
> 	-	-	-	-	-	-	-	-	-
> -
> I feel foolish that I have not commented on this, which has been unchanged
> since 1.0.  I thought I saw this handled, but it must have been in some
> other XML-based specification.  I'm certain that people must ask about it.

What you say is true from a purely XML perspective.

For those not aware of it, prefixes, are merely a convenience and from 
an XML perspective, they can be changed at will.

An XML parser reads the namespace declaration and then associates 
whatever prefix has been defined as the prefix for that document. Some 
are quite customary, such as "svg."

That doesn't necessarily answer the question for the ODF standard. Our 
language appears to have been unfortunate in several cases. I have 
omitted all the references that simply say: use XML namespaces as those 
follow the normal rule.

1.3 Namespaces

> Table 1 lists the namespaces that are defined by the OpenDocument 
> schema and their default prefixes.
OK, default prefixes, that works.

3.2 General:

> Metadata elements drawn directly from the Dublin Core work use its 
> namespace prefix.
"use its"

15.9 Data Styles

> The elements and attributes that are used to represent data styles are 
> contained in the namespace 
> urn:oasis:names:tc:opendocument:xmlns:datastyle:1.0. The prefix 
> |number| denotes the data styles namespace.
"denotes the data styles"

16.2.1 Simple Formatting Properties

> In this specification, the namespace prefix |fo| is used for XSL 
> formatting properties.
"is used for"

18.16 chart:class

> The chart type is represented by a name in the chart namespace (URN: 
> urn:oasis:names:tc:opendocument:xmlns:chart:1.0). 
OK, I threw this one in to show how we have used namespaces consistent 
with the XML Namespace spec.

18.630.1 script:event-name

For values of the script:event-name we say:

> The namespace prefix used in this specification is “dom”.
"used in this specification"

It is possible to say that we simply were unclear as to whether "used in 
this specification," "is used for," "denotes the data styles," "uses 
its," were statements meant to require the use of particular prefixes or 
that it was simply poor expression our part.

I suspect, but don't know, that applications already support the 
standard definition of XML Namespaces, that is that the prefixes are 
non-normative. So being clear that we are simply using our declared 
defaults and that doesn't bar anyone else from using other prefixes 
would have no impact.

However, I would like to hear from the implementation side of the house 
before putting too much stock in that assumption.

Hope you are having a great weekend!

>  - Dennis
> Dennis E. Hamilton
> ------------------
> NuovoDoc: Design for Document System Interoperability 
> mailto:Dennis.Hamilton@acm.org | gsm:+1-206.779.9430 
> http://NuovoDoc.com http://ODMA.info/dev/ http://nfoWorks.org 

Patrick Durusau
Chair, V1 - US TAG to JTC 1/SC 34
Convener, JTC 1/SC 34/WG 3 (Topic Maps)
Editor, OpenDocument Format TC (OASIS), Project Editor ISO/IEC 26300
Co-Editor, ISO/IEC 13250-1, 13250-5 (Topic Maps)

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