Hi Karen,
> This one is turning out to be very complex, and I'm feeling
> the need to start putting together some initial lists of
> elements. I did some analysis of the element list provided by
> JSC, and there are over 60 elements on their table that
> aren't associated with a FRBR entity. I'm thinking that
> perhaps we need, for the moment, to push aside the FRBR
> question, and identify elements and sub-elements without
> concerning ourselves about their FRBR role.
>
> Unless someone has a better idea.
>
> I'm willing to stick my neck out with a first list of
> elements, although it's hard to talk about them entirely out
> of context. I could try to organize them, or we could mark up
> the JSC list and publish that via Google Docs.
> --
Given that, as you say on
http://dublincore.org/dcmirdataskgroup/analysisTask1
===
# Each RDA element needs to be defined as a relation between two
entities. For example, a creator element is a relation between a
Resource and a Person (or Agent, generally).
# Each RDA element must specify to which class of resources the element
applies (the Domain of the property), and which class of resources the
element can have as values (the Range of the property).
===
I'm not sure really understand how it is possible to "push aside the
FRBR question". :-)
"Elements" express relationships between two resources, so for any
"element", the nature of that element is intimately bound up with the
nature of the resources between which it is expressing a relationship -
which I guess is what you mean by "it's hard to talk about them entirely
out of context".
Pete
---
Pete Johnston
Technical Researcher, Eduserv Foundation
Web: http://www.eduserv.org.uk/foundation/people/petejohnston/
Weblog: http://efoundations.typepad.com/efoundations/
Email: [log in to unmask]
Tel: +44 (0)1225 474323
|