On Monday, Sep 22, 2003, at 14:05 Europe/Rome, Sylvain Wallez wrote:
Stefano Mazzocchi wrote:
On Monday, Sep 22, 2003, at 00:38 Europe/Rome, Ugo Cei wrote:
Stefano Mazzocchi wrote:
On Sunday, Sep 21, 2003, at 18:46 Europe/Rome, Sylvain Wallez wrote:
So what about the following convention :
- http://apache.org/cocoon/block-id/pdf/1.0 for the pdf block _identifier_
- http://apache.org/cocoon/block/pdf/foo/1.0 for the "foo" namespace of the pdf block ?
I'm not enthusiastic about it, but I can't come up with anything better than this.
Does anybody else care about this? alternative ideas anyone?
Since the block id should be a resolvable URL, why not http://cocoon.apache.org/blocks/pdf/1.0 ?
This way, it's difficult to confuse it with the namespace and we don't need any rewrites on apache.org.
D'oh! you are so right. +1
what do others think?
Taking the above example, does this mean :
- http://cocoon.apache.org/blocks/pdf/1.0 for the block ID and
- http://apache.org/cocoon/blocks/pdf/foo/.1.0 for the "foo" namespace defined by the pdf block ?
Mmmh... it certainly avoids conflicts, but can be confusing and looks somewhat inconsistent : why apache.org/cocoon on one side and cocoon.apache.org on the other side ?
because all namespaces (and only those!) are located on apache.org/cocoon. I think this is very consistent.
Besides, it is rare that you use block-id *and* namespaces in the same document... and users never have to do that, only block developers in the block.xml file.
Remember : you moved namespaces from xml.apache.org/cocoon to apache.org/cocoon because of the promotion of Cocoon to top-level project. What if we decide in the future to rename the TLP from "cocoon" to e.g. "cms" ??
and what if we change the name of the project to "blaboon" because Sony decided to sue us for trademark infringment? [ for the movie or for the tivo-like thing]
or what if the apache nation changes leaders and they want royalties from their name and we are required to change the ASF main location?
good URI shouldn't change, but it's hard to avoid changing something that has a meaning associated to it... because that meaning drifts with time. This is why DOI, for example, uses numbers instead.
for example, TimBL explained that the use of 1999 in the XSLT namespace is because in a hundreds years from now, people might want to reuse the XSLT name to mean something completely different.
Forward thinking or egocentric naiveness?
cocoon.apache.org is not going anywhere from all the signals I can feel, so it seems solid enough to base this infrastucture upon.
-- Stefano.
