W3C home > Mailing lists > Public > public-mobileok-checker@w3.org > June 2007

Re: Namespaces in messages.properties.xml

From: Sean Owen <srowen@google.com>
Date: Tue, 26 Jun 2007 00:25:45 -0400
Message-ID: <e920a71c0706252125o3d3cfb99p1abbc57fe8d4e8a4@mail.gmail.com>
To: "Roland Gülle" <roland@7val.com>
Cc: "Laura Holmes" <holmes@google.com>, public-mobileok-checker@w3.org
Yeah it works -- the only reason we thought it wasn't quite right is
it doesn't seem proper to use the moki namespace on this document? I
tend to think of a namespace as more or less mapping to a DOCTYPE, if
you know what I mean, that one namespace defines the elements in one
kind of document. This isn't necessarily true -- it's merely a
namespace -- and if in fact this kind of usage is totally normal,
well, let's go for it. But it seems a little odd.

We could define a second namespace. Is that overkill?

Let me finally ask this to the experts: the reason this seems to be an
issue in the XSL is that we make the default namespace for the XSL
stylesheet the moki one. Do we have to do this? I understand that then
we have to qualify a bunch of other stuff as "moki:..."; is there any
way around that?

At the moment it seems like it's a question of whether re-using the
moki namespace is much of a sin. As this is a W3C product, seems like
we should take extra care to get it right.

Sean


On 6/26/07, Roland Gülle <roland@7val.com> wrote:
>
> Hi Laura,
>
> > I've been working on refining the caching test and I have a
> > question about the error messages we're reporting and how that
> > whole thing functions. Basically, after the CachingTest.xsl (or any
> > test for that matter) successfully identifies an error, it looks to
> > messages.properties.xml to find the corresponding message to print
> > out. However, the function "moki:msgI18n" in the functions.xsl file
> > kept failing to recognize the ID I had supplied in the messages
> > file for the specified error. It kept reporting that the message id
> > was not defined. I hacked the messages file a bit by inserting
> > xmlns=" http://www.w3.org/2007/05/moki under the "messages" tag and
> > now it seems to work.
> Great!
> Use messages.properties.<LANGUAGE>.xml to generate language specific
> messages.
>
> > My question is: what should the namespace for messages file be?
> > Should we continue to use this one or make up a different namespace
> > for the messages file? Or should we be doing something different
> > entirely?
> xpath-default-namespace="http://www.w3.org/2007/05/moki" sets the
> default namespace, so I used this namespace to keep the XPath in the
> msgI18n function easy as possible.
> If a new namespace is needed, we can change the function.
>
> Cheers,
>   Roland
>
>
>
Received on Tuesday, 26 June 2007 04:26:01 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 8 January 2008 14:13:03 GMT