I can see where the confusion would exist for you in this case.
When I have such a situation here _and_ the parent resource is not included (for example, an instruction sheet for a form, which is separate from the form)
I have been doing the following:
For the instructions: Requires [form] <the instructions do not make as much sense without said form>
for the form: References [instructions] <since one *can* use the resource without the instructions>
I'm still stumped though, when I have a policy that then includes the full form as an attachment (to attach to your example, I have a number of other items that get attached in full to these policies and procedures). I do not want to ignore the attachment. At this time, I do not always have access to the original item that is used in the attachment. (sometimes it might be a policy or memo from another agency that is not available in their public domain). I have not yet spoken to the Director, or his secretary to see if they want to include the original. We are still setting up a new, much more powerful, system using an enterprise portal. Thus, we have a number of users that are in the "wait and see what this thing is going to do" stage.
Kelly Ann Green
KMS Content Analyst
Virginia Retirement System
-----Original Message-----
From: General DCMI discussion list [mailto:[log in to unmask]]On
Behalf Of Paul Stainthorp
Sent: Tuesday, July 20, 2004 7:19 AM
To: [log in to unmask]
Subject: Re: Qualified DC metadata HasPart and References question
I've been struggling with this one myself: there seems to be some overlap (or perhaps a grey area where none is wholly appropriate), between the three qualifiers:
(1) Requires
"The described resource requires the referenced resource to support its function, delivery, or coherence of content".
(2) hasPart
"The described resource includes the referenced resource either physically or logically".
(3) References
"The described resource references, cites, or otherwise points to the referenced resource".
All three could logically be used to describe (for example, as we are attempting to do) a resource which is a user guide (set of access instructions, help sheet, password list, whatever) for the parent resource. I don't know the answer though! I'd be very interested in finding out how other people have coped with describing more "fuzzy" relationships.
Paul Stainthorp
University of Lincoln
UK
-----Original Message-----
From: General DCMI discussion list [mailto:[log in to unmask]]On Behalf Of Kelly A Green
Sent: 19 July 2004 16:03
To: [log in to unmask]
Subject: Qualified DC metadata HasPart and References question
I'm trying to figure out how to identify a relation wherein a document contains another document (as an attachment) in its entirety.
HasPart does not seem to really fit, as it indicates an excerpt.
In addition, I rarely have the attachment as a document in its own right. It is often an item issued by another organization.
However, References does not truly apply either.
Has anyone else dealt with this issue?
I would really appreciate any guidance.
Kelly Ann Green
KMS Content Analyst
Virginia Retirement System
[log in to unmask]
[Kelly A Green]
|