The way I see it, Rikki's comments are like this:
Camp 1:
People who want to use DC for resource discovery
Camp 2:
People who want to use DC for resource cataloging
I don't see that the two issues are mutually exclusive. One project I'm
involved with has added two extra fields onto the DC set - using an
"AGLS" prefix to indicate that the data is fully specifiied in another
meta data scheme.
When it comes to the Plain DC/Qualified DC... I don't see that there's
any real problem. As long as we can avoid merging fields (which would,
to my mind, just add another "general purpose" field onto the 15 that
already exist), then both camps can use the same grounds without too
many problems.
When it comes to freetext/prescribed list, I don't see that there's any
real problem. A "smart" discovery interface could pick, from a starting
result set, the "prescribed lists" that the returned resources refer to.
Similar to the way the Nordic Metadata project's metadata editor lets
you specify the vocabulary you're using - the next step is to list the
"level 1" words from that vocabulary. To see an example of
"level1/level2" vocabularies, check out
http://www.business.gov.au/general.html, perform a search using just one
of the terms from "Industry" or "Topic", then elect to refine your
search.
Anyhow... I'm sure you've heard enough from me for the day :)
-Alex
|