Michael Wechner wrote:
[...]
I'd start with option (2). Concepts like resource type inheritance and
overriding resource types in publications could be discussed,
do you see any negative side-effects with this?
Actually I don't know what it would look like. At the moment, "overriding"
a resource type would just mean to declare an additional resource type
like "default/xhtml" and maybe reference the schema and samples of the xhtml
module, so there's no real inheritance. But you could declare additional
formats which are served by the default publication's sitemap. Maybe
this isn't such a bad idea.
but I'd
rather see the resource type as a black box and apply an additional
transformation inside the publication (e.g., as you already mentioned,
using meta data).
well, it's seems to me that this will be a never-ending story, but
it's more of guts feeling and maybe one can limit it.
The concept described above is probably a quite clean solution.
It allows a clear separation between resource type presentation formats
and publication logic. But it requires to declare an additional
resource type.
-- Andreas
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
