RE: Using Dublin Core as meta data for XSLT stylesheet

Hi,

> -----Original Message-----
> From: owner-xsl-list@xxxxxxxxxxxxxxxxxxxxxx
> [mailto:owner-xsl-list@xxxxxxxxxxxxxxxxxxxxxx]On Behalf Of G. Ken Holman
> Sent: Thursday, February 06, 2003 9:16 AM
> At 2003-02-06 08:29 -0800, Robert Koberg wrote:
> >You might want to look at RDF and Dublin Core.
>
> That was in the article I found by Uche.
>
> >Simple DC: http://dublincore.org/documents/2002/07/31/dcmes-xml/
>
> Thanks, Rob ... that looks like a definitive set of guidelines.
>
> >There is a document (I can't find right now) about expressing qualified DC in
> >RDF/XML.
> >What would you want out of a CMS? (very curious! - we use RDF/DC in our CMS
> >along with additional site/folder/page/content specific metadata - not
> >released
> >yet...)
>
> It struck me that if I were to catalogue my stylesheets having already gone
> through the effort of adding structured information, wouldn't it be nice if
> it were automatically detected and incorporated into whatever management
> system I happened to be using?
>
> Which I'm not yet ... I'm just using my file system and CVS ... but I
> thought it would be a logical question if it were already being done.  You
> know: invest a bit now so that in the future if it could be taken advantage
> of then it would already be done.

Well, we kind of do it for XSL.  We keep a master site/project config that
mimics the hierarchy of the entire site - a virtual representation of the
current state of the site. So XSLs can be located by their identifier. The IDs
on the XSL files are used in the LSB tool in a URIResolver so the file can be
found during the transformations Template caching/building. By nesting the the
files/folders I can build relative paths to every item (virtual or not). These
IDs also correspopnd to meta data in a separate file that is used in the tool
mainly for UI purposes.

There is a standards based effort that does something like this with more strict
URIs. I found it too late and not using it for LSB. RDDL is here:
http://www.rddl.org/
also XMLCatalogs:
http://www.oasis-open.org/committees/entity/spec-2001-08-06.html

Since my tool is based on the conccept of a storyboard - meaning you can change
things around easily, generate and test for usability, I find using a more
simple UID to be much easier. The site/project config can be transformed to a
RDDL type thing when the URIs have been thought out. During development Cool
URI's *DO* Change:
http://www.w3.org/Provider/Style/URI.html


>
> >Are interested in qualified DC or simple DC?
>
> I confess to not know the difference ... I just looked at the list of
> elements and picked what looked interesting to me.  Would you recommend one
> over the other?

Well simple DC makes it much easier to build forms :). But seriously, it depends
on how serious you want to get with your metadata. If you want/need more fine
grained metadata (not just dc:date, but dc:date.created and dc:date.modified,
etc) that you might want to look at qualified DC. Using RDF makes it a bit more
complicated but not unmanageable to write by hand. Forms are another story
(thank &diety; for the MSXML SOM)

I have an old printout for a document, "Expressing Qualified Dublin Core in
RDF/XML." The URL is:
http://dublincore.org/documents/2000/04/14/dcq-rdf-xml/ but it is no longer
there. Hmmm...

There is another page that talks about qualifiers on the dublincore.org site but
it has a background image saying it is obsolete. I don't see any up-to-date
reference. I really don't know what is up with qualifiers.

best,
-Rob


>
> ................ Ken
>
>
> --
> Upcoming hands-on in-depth   Europe:         February 17-21, 2003
> XSLT/XPath and/or XSL-FO     North America:      June 16-20, 2003
>
> G. Ken Holman                mailto:gkholman@xxxxxxxxxxxxxxxxxxxx
> Crane Softwrights Ltd.         http://www.CraneSoftwrights.com/s/
> Box 266, Kars, Ontario CANADA K0A-2E0   +1(613)489-0999 (F:-0995)
> ISBN 0-13-065196-6                      Definitive XSLT and XPath
> ISBN 0-13-140374-5                              Definitive XSL-FO
> ISBN 1-894049-08-X  Practical Transformation Using XSLT and XPath
> ISBN 1-894049-10-1              Practical Formatting Using XSL-FO
> Male Breast Cancer Awareness http://www.CraneSoftwrights.com/s/bc


 XSL-List info and archive:  http://www.mulberrytech.com/xsl/xsl-list