[EMAIL PROTECTED] schrieb:
On 3/24/08, Andreas Hartmann <[EMAIL PROTECTED]> wrote:
 IMO the concept of resource type formats has proven very useful and
 convenient. Maybe it makes sense to introduce implicit formats which
 don't depend on a particular resource type but work with all documents?
 A first candidate might be the "metadata" format:
   lenya-document:…,pub=…,area=…,lang=…?format=metadata
 would return the XML format of the LenyaMetaDataGenerator.

 WDYT?
 -- Andreas

The lenya-document protocol seems to provide some of the functionality
of Lenya-1.3's content: protocol with its three "formats": DATA, INFO,
and META.
- DATA is the Resource.
- INFO is the XML version of a Resource.  The output is identical to
DATA if the Resource contains XML.  This format is useful to retrieve
internal information of binary files.
- While the first two formats handle specific Revisions, META returns
XML for the entire Resource including all Translations and Revisions.

In 2.0, formats were introduced as presentation options of a document (to be displayed as a stand-alone version or to be embedded in a complex page etc.). Each resource type can declare an arbitrary set of formats. Examples are

- xhtml
- teaser
- rss
- xslfo
- ...

The concept has been used for some "unusual" applications, e.g. there are format conventions for the sitetree icon and for the Lucene index document. Maybe it makes sense to add another convention for the metadata.


When using the term "metadata", are you referring to internal
information or to lenya:meta information from Resources' XML?

In 2.0, the meta data are stored outside the document. You can define arbitrary element sets. The core includes the Dublin Core elements and terms and some meta data for internal use (resource type name, source extension etc.). Some resource types (e.g. "resource" for binary files) add their own specific meta data.

-- Andreas


--
Andreas Hartmann, CTO
BeCompany GmbH
http://www.becompany.ch
Tel.: +41 (0) 43 818 57 01


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to