Paul Miller wrote:
> Presumably, the DC. prefix model suggested by many for the Dublin Core
> could be called into service here, giving you
>
> ...
> <META NAME="DC.creator"
> ...
>
> and
>
> ...
> <META NAME="ADS.creator"
>
> where 'ADS' refers to a specific Archaeology Data Service profile that
> would, of course, be fully defined on the ADS website...
>
> There are issues here of registry, as with SCHEME names, in order to avoid
> 'ADS' being 'Archaeology Data Service' AND 'Alberta Dustbin Systems' or
> the Getty's Art & Architecture Thesaurus scheme being coded as both 'AAT'
> and 'A&AT'...
Quite to the contrary! Recall tha the DC.xxx proposal involved
binding DC to a URL. So the local name "ADS" would be clearly
bound to a global pointer to one organization or the other. No registry
is needed. Or to look at it another way: the registry is
the web.
---------------
excerpt from
http://www.w3.org/pub/WWW/Search/9605-Indexing-Workshop/ReportOutcomes/S6Group2.html
A Proposed Convention for Embedding Metadata
in HTML.
Reported by Stuart Weibel ([log in to unmask])
June 2, 1996
3. LINKAGE TO THE REFERENCE DESCRIPTION
OF A SCHEMA
It is judged useful to provide a means for linking to the reference
definition of a schema as well. The proposed convention for doing so is
as follows:
<LINK REL = SCHEMA.schema_identifier HREF="URL">
Thus, the reference description of one metadata scheme, the Dublin
Core Metadata Element Set, would be referenced in the LINK HREF as
follows:
<LINK REL = SCHEMA.dc HREF = "http://purl.org/metadata/dublin_core">
---------------
See also "Goal: Self-describing information" in:
http://www.w3.org/pub/WWW/DesignIssues/Metadata.html
--
Dan Connolly, W3C Architecture Domain Lead
<[log in to unmask]> +1 512 310-2971
http://www.w3.org/People/Connolly/
PGP:EDF8 A8E4 F3BB 0F3C FD1B 7BE0 716C FF21
|