> From [log in to unmask] Wed May 7 19:45 MET 2003
> X-RAL-MFrom: <[log in to unmask]>
> X-RAL-Connect: <jupiter.hc-sc.gc.ca [198.103.237.7]>
> X-MIMETrack: Serialize by Router on SMTA00/HC-SC/GC/CA(Release 5.0.9a |January
> 7, 2002) at 05/07/2003 01:45:09 PM
> MIME-Version: 1.0
> Date: Wed, 7 May 2003 13:41:33 -0400
> From: Cecil Somerton <[log in to unmask]>
> Subject: Re: Expressing Qualified Dublin Core in HTML/XHTML meta elements
> To: [log in to unmask]
>
> Folks,
> For those of us who are still implementing DC in the HTML world, we
> may not be looking to build a metadata infrastructure per se, just
> encourage some basic resource discovery. A solid implementation in HTML or
> XHTML may be what is needed to encourage the uptake of the DC as a sound
> investment. Once proven there it may well engender a more sophisticated
> metadata infrastructure. I see a good point in that.
I agree: The main point in updating the DC in HTML recommendation
is to bring it in alignment with HTML4/XHTML1 -
The <link rel="schema.dc" href="http://purl.org/dc/elements/1.1/">
construction seems subtle in this respect.
A link type expressed via rel="schema.dc" in itself would/could be subject to a profile declaration.
Some of the built in link types (contents, copyright, alternate, chapter,
section, subsection, appendix, start, prev, next..) relate to dc-terms and
dc in html might say whether or not or how a dc-application should take
them into account.
Maybe also some comments on other link element attributes
[http://www.w3.org/TR/html4/struct/links.html#edef-LINK
are useful also (type for instance).
rs
>
> Cecil Somerton
> Metadata Coordinator/Coordinateur des métadonées
> IKMD Information Resources/Ressources en information, DSGI
> Telephone/Téléphone: (613) 957 2664
> Fax/Télécopieur: (613) 957-0292
>
>
|