Liddy,
>>> Liddy Nevile <[log in to unmask]> 10/06/03 12:31:01 >>>
good idea but the problem with that,. as I understand it, is that
people wanting the resource want to know about the metadata sometimes
(eg for accessibility reasons) and so they would not want it to be
hidden away - if the proposal for dc:admin is for that to be with the
other metadata, that's fine, but we have always had ours separate ...
(cos it's metametadata!)
I haven't been involved in DC-AC, but it doesn't appear to prescribe
whether its elements should be embedded or separate. In one project I
did use one DC-AC element embedded alongside "ordinary" metadata
(following our Application Profile using RDF/XML). I guess it would
depend on the conventions implementors followed...
Presumably you can use DC-AC elements separate and/or embedded, eg:
Separate metadata record database:
dcac:identifer = 1
dcac:location = http://server/record1.xml
dcterms:created = 1998-01-01
dcterms:modified = 2003-01-01
---
dcac:identifer = 2
dcac:location = http://server/record2.xml
dcterms:created = 1998-01-01
---
Actual metadata record (record1.xml):
<record>
<dc:title>Title</dc:title>
<dc:identifier>http://resource</dc:identifier>
<dcac:identifier>1</dcac:identifier>
<dcac:conformsTo>Conformance Standard</dcac:conformsTo>
</record>
Douglas
|