Andreas Hartmann wrote:
Michael Wechner wrote:
Hi
I think we should introduce a namespace for the config file
publication.xconf
That makes my alarm bells ringing ...
ATM this file is a configuration file, it should only be accessed
by the PublicationImpl class. Using it for other purposes, e.g.
for processing in pipelines, would require an explicit contract
("publication definition language").
I'm generally +1 for namespaces, but if we add a namespace (which
IMO suggests that the document is meant to be processed), we should
add a schema as well to declare the contract and ensure backwards
compatibility.
I want to aggregate it with publication.xml and in the long run merge
parts of it
in order to show the configuration which is often important to know
(e.g. modules wise, ...)
by having a quick look (just as one wants to know which Lenya and Coocon
version the publication is based on)
Also as said having a namespace is also about DOM2 compatibility and I
am not the one who
said this originally on this mailing list. You might want to re-read
your own threads ;-)
Michi
-- Andreas
--
Michael Wechner
Wyona - Open Source Content Management - Apache Lenya
http://www.wyona.com http://lenya.apache.org
[EMAIL PROTECTED] [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
