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 ?
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" ??
Sylvain
-- Sylvain Wallez Anyware Technologies http://www.apache.org/~sylvain http://www.anyware-tech.com { XML, Java, Cocoon, OpenSource }*{ Training, Consulting, Projects } Orixo, the opensource XML business alliance - http://www.orixo.com
