Johannes Gijsbers wrote:
[I tried to send this yesterday, but apparently it didn't show up.]
Hey Lenya developers,
I'm currently working on a module that would allow xCal events to be
associated with a document. In a sense, these xCal events are metadata
on that document. However, it's not possible to represent xCal data in
the metadata format that Lenya uses (nor do I think it should be).
Would you mind giving a quick summary why this shouldn't be possible?
Maybe it would make sense to support xCal?
My current thinking would be to add a '.xcal' file in the repository for
every document that has xCal data associated with it. So a typical
directory would look like this:
/pubs/default/content/authoring/tutorial:
index_en
index_en.meta
index_en.xcal
That would require to tweak the repository layer, it doesn't really
conform to the Lenya architecture.
(Obviously indexes generally won't have xCal events associated with
them, but you get the point.)
Now my questions are: does this make sense in the Lenya architecture?
Does it seem like the best way to implement it? If so, could you give me
some pointers on the implementation?
If the meta data can't be expressed using the Lenya meta data, I'd see
two approaches:
1) embed the data in the document using a namespace
2) add a second document (which contains the xCal data) for each content
document and use a meta data element (preferrably by declaring a
custom element set) to store the UUID of the xCal document
The second option seems cleaner to me.
But it would require to override the publishing usecase etc. and add the
code to handle the xCal documents.
-- Andreas
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
