forrest-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Glen Tulukin" <>
Subject Re: search engine friendly skins
Date Tue, 21 Dec 2004 15:07:26 GMT
Sounds good as long as we can associate a flexible meta data with document.
I agree that cocoon xmap is better than document().

A question. To make my use case complete... I know that we can aggregate. Do
you design any capabilities of forking. Let's go back to my jpg example. I
need to produce two additional documents that have distinct list of
locations and distinct list of authors respectively -- I go through each
document (i.e. jpg) get "location" and "author" (meta data associated with
each jpg), generate html for each jpg and add location to locations doc and
add author to authors doc. Yes, I know that I can put location or author to
the session or I can use Xalan's redirect() but I guess it's probably not
the best approach.
I want to avoid additional aggregate processes -- one for locations and one
for authors.


"Ross Gardler" <> wrote in message
> David Crossley wrote:
> > Ross Gardler wrote:
> >
> >>Glen Tulukin wrote:
> >>
> >>
> >>>Do not think about meta data as merely html/head/title or
> >>>html/meta/keywords -- there might be other data associated with a
> >>>Look at advanced jpg properties (date, location, equipment make, camera
> >>>model, author, etc.). It's more than title and keywords. I can put
> >>>camera_model to the <div> as a hidden element and than extract from
> >>>div,
> >>>but this will be awkward. To have a separate meta-data element is
> >>
> >>Yes, I agree and this is why my personal solution would be to have a
> >>separate meta-data document to enable efficient processing of this
> >>important data. However, this seems to go beyond your own use case and
> >>that XHTML meta elemets would be sufficient. I assumed this since you
> >>start in the document DTD using the the XHTML meta-data element.
> >>
> >>If we need a separate record of meta-data in a more flexible format than
> >>the HTML meta element allows then we should really use a separate
> >>document. The processing you propose in site2html.xsl will remain the
> >>same, or at least very similar since we can use te XSL document(...)
> >>function to import the meta-data document when one exists.
> >
> >
> > It would be better to use Cocoon sitemap aggregation powers
> > rather than document() function. With the latter method, when
> > the metadata documents change the Cocoon cache will be avoided.
> Yes, good point.
> Ross

View raw message