 |
 |
Back when this was discussed our intention for this relators list was that it would be a subset of our larger relator list at: http://lcweb.loc.gov/marc/relators/re0002r1.html That list actually standardizes the codes associated with relator terms, but the thought was to use those relator terms that are cross-domain in nature. There are many terms in the larger list that are very specific to a certain application. So in our offer to maintain it, it would remain a subset of the larger list and any changes in the larger list would be incorporated in the subset. The process currently is that someone may apply for a new term (which is now fairly infrequent). We check and see if it's covered adequately by another term (i.e. in the case that it becomes a reference to another term because it means the same thing). If it deserves its own relator term we assign it a code and announce it to MARC users. We rarely if ever change (i.e. deprecate) anything on the list. So if these terms are used as element refinements for CCP, then I would see the following happening: We could maintain the subset list with definitions (these would be generally the same as those in our established list, although there could be cases where we generalize them a bit, as we have done in what Eric Miller made available) DCMI would register each as an allowable element refinement with links to the LC definitions If new ones are needed, the larger MARC relator list should be consulted and we could migrate a term to the subset. If there isn't one available, then it could be suggested as a new term to the MARC list. At the same time it would go as a new qualifier to the Usage Board and if approved included in the subset list. What about this approach? Rebecca On Fri, 15 Jun 2001, Thomas Baker wrote: > On Wed, 13 Jun 2001, Rebecca S. Guenther wrote: > > Back when we started working on this issue, the idea was to take a subset > > of the Relators list that was for general applications and define them as > > element refinements for CCP. At the same time we went through those and > > determined which elements they refined. That wasn't too complicated, since > > all of them on the list appropriately refined Creator and Contributor and > > as I recall only 1 or 2 refined Publisher. LC was willing to put this > > subset up and maintain it. > > > > I'm not sure if this adds anything to the discussion, but I think this is > > a way to go. Then I guess I would agree with the statement below. > > I have attached (below) an XML/RDF schema that Eric prepared for those > proposed MARC Relator terms (the original is still at > http://dublincore.org/2000/03/13-marcrel). In accordance with our > decision to move out of the directory tree of the DCMI registry all > XML/RDF schema files that have not been approved by the Usage Board, > this would presumably be moved elsewhere -- or we would decide that the > DC namespace URIs, which will probably end up starting with > http://purl.org/dc, resolve to something other than this directory > tree. > > The model we are discussing implies that LC would make such a schema > available for us to point to and would maintain it over time. What > kind of statement would we as UB be making about those terms -- for > example, would we acknowledge the terms individually or as a whole > namespace? Could LC add terms or otherwise maintain that list without > seeking approval for every change, and would added terms automatically > be considered "recommended by DCMI UB"? Would LC need to acknowledge > the same sort of namespace policy we are discussing for DCMI (eg, > deprecating terms is okay, but they should never be removed; adding > terms is okay; changing definitions is okay within limits...)? > > Tom > > ----------- > <?xml version="1.0"?> > > <!-- > RDF Schema declaration for the LOC Marc Relator Terms for the DCES > 2000/03/13 > comments, etc. to eric miller, [log in to unmask] > --> > > <rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" > xmlns:rdfs="http://www.w3.org/2000/01/rdf-schema#" > xmlns:dc="http://dublincore.org/2000/03/13-dces#" > xmlns:eor="http://dublincore.org/2000/03/13-eor#"> > > <eor:Schema rdf:about="http://dublincore.org/2000/03/13-marcrel"> > <!-- dumb down rule... use rdf:value for a simple default name --> > <rdf:value>The Library of Congress MARC Relator Terms for the Dublin Core</rdf:value> > <dc:title>The Library of Congress MARC Relator Terms for the Dublin Core</dc:title> > <dc:creator>The Library of Congress</dc:creator> > <dc:description>MARC Relator Terms</dc:description> > <dc:language>English</dc:language> > <dc:date>2000-03-13</dc:date> > </eor:Schema> > > <rdf:Property rdf:ID = "adaptor"> > <rdfs:label>Adaptor</rdfs:label> > <rdfs:comment>An agent who reworks a resource usually for a > different medium</rdfs:comment> > <rdfs:subPropertyOf rdf:resource = "http://dublincore.org/2000/03/13-dces#creator" /> > <rdfs:subPropertyOf rdf:resource = "http://dublincore.org/2000/03/13-dces#contributor" /> > <rdfs:isDefinedBy rdf:resource = "http://dublincore.org/2000/03/13-marcrel" /> > </rdf:Property> > > <rdf:Property rdf:ID = "distributor"> > <rdfs:label>Distributor</rdfs:label> > <rdfs:comment>An agent or agency that has exclusive or shared marketing > rights for an item.</rdfs:comment> > <rdfs:subPropertyOf rdf:resource = "http://dublincore.org/2000/03/13-dces#publisher" /> > <rdfs:isDefinedBy rdf:resource = "http://dublincore.org/2000/03/13-marcrel" /> > </rdf:Property> > > <rdf:Property rdf:ID = "editor"> > <rdfs:label>Editor</rdfs:label> > <rdfs:comment>An agent who prepares for publication a work not primarily > his/her own, such as by elucidating text, adding introductory or > other critical matter, or technically directing an editorial staff. </rdfs:comment> > <rdfs:subPropertyOf rdf:resource = "http://dublincore.org/2000/03/13-dces#creator" /> > <rdfs:subPropertyOf rdf:resource = "http://dublincore.org/2000/03/13-dces#contributor" /> > <rdfs:isDefinedBy rdf:resource = "http://dublincore.org/2000/03/13-marcrel" /> > </rdf:Property> > > <rdf:Property rdf:ID = "performer"> > <rdfs:label>Performer</rdfs:label> > <rdfs:comment>An agent who exhibits musical or acting skills in a musical > or dramatic presentation or entertainment.</rdfs:comment> > <rdfs:subPropertyOf rdf:resource = "http://dublincore.org/2000/03/13-dces#creator" /> > <rdfs:subPropertyOf rdf:resource = "http://dublincore.org/2000/03/13-dces#contributor" /> > <rdfs:isDefinedBy rdf:resource = "http://dublincore.org/2000/03/13-marcrel" /> > </rdf:Property> > > <rdf:Property rdf:ID = "sponsor"> > <rdfs:label>Sponsor</rdfs:label> > <rdfs:comment>An agent that issued a contract or under the > auspices of which a work has been written, printed, published, etc.</rdfs:comment> > <rdfs:subPropertyOf rdf:resource = "http://dublincore.org/2000/03/13-dces#contributor" /> > <rdfs:isDefinedBy rdf:resource = "http://dublincore.org/2000/03/13-marcrel" /> > </rdf:Property> > > <rdf:Property rdf:ID = "translator"> > <rdfs:label>Translator</rdfs:label> > <rdfs:comment>An agent who renders a text from one language into another, > or from an older form of a language into the modern form.</rdfs:comment> > <rdfs:subPropertyOf rdf:resource = "http://dublincore.org/2000/03/13-dces#contributor" /> > <rdfs:isDefinedBy rdf:resource = "http://dublincore.org/2000/03/13-marcrel" /> > </rdf:Property> > > </rdf:RDF> > > _______________________________________________________________________________ > Dr. Thomas Baker [log in to unmask] > GMD Library > Schloss Birlinghoven +49-2241-14-2352 > 53754 Sankt Augustin, Germany fax +49-2241-14-2619 >