Paul Miller writes:
> On Tue, 6 Aug 1996, Jon Knight wrote:
>
> Hmm... I don't see any way to do this that gives valid HTML and also
> reads sensibly to the viewer.
> <META NAME = "DC.date"
> TYPE = "creation"
> SCHEME = "ISO31"
> CONTENT = "1996-06-17">
> <LINK REL = SCHEMA.dc HREF =
> "http://purl.org/metadata/dublin_core_elements#date">
> <LINK REL = SCHEMA.iso31 REFERENCE =
> "ISO 31-1:1992 Quantities & units -- Part 1: space & time">
>From various discussions with persons in the parser, robot and
validator camps, there does not seem to be a good way of embedding the
elements and attributed outlined in the DC workshops in HTML 2.0 and
be easily understood by the user. What Paul has outlined is a logical
and simple extension to HTML 2.0 for encoding this information.
Name-space overload is minimized and it's fairly clean and straight
forward. Validation is an obvious concern, but with local extensions
occuring right and left from various browser implementors, HTML is
still a moving target and validation will continually be problematic.
These are not ad hoc extensions... I'd like to agree upon an encoding
framework (the above gets my vote) and begin to focus on metadata
registry issues, deployment, etc.
eric j. miller <URL:http://purl.oclc.org/net/eric>
[log in to unmask] OCLC, Online Computer Library Center, Inc.
[log in to unmask] Dept. of Geography, The Ohio State University
|