I have used Ian Davis' FRBR Core schema, which uses a consistent
property naming convention based on role nouns. I like this convention
a lot, and strongly recommend it for IFLA's own registration.
DC uses the role noun convention a lot, e.g. dc:creator,
dc:contributor, dc:title, dc:description etc. Ian Davis' frbr does the
same thing, e.g. frbr:embodiment, frbr:realization etc.
Role nouns for property names are clear, simple, consistent, concise,
and map well into other software/modeling environments
e.g. object-oriented code, UML class diagrams or entity-relationship
models.
But whatever you choose in the end, make sure it follows a consistent
convention -- inconsistent naming is a massive headache.
Cheers,
Alistair.
On Wed, Dec 03, 2008 at 09:58:35AM +0000, Gordon Dunsire wrote:
> Karen, Alistair and others
>
> Concerning 3):
>
> The FRBR relationships will be registered as RDFS properties, as inversed pairs, when the namespace is formally established; in the NSDL sandbox, this corresponds to the <FRBR relationships> vocabulary, not the <FRBR relationships as concepts> vocabulary.
>
> So, provisionally (important!),
>
> ex:C frbr:isEmbodiedIn ex:D
>
> and conversely,
>
> ex:D frbr:isEmbodimentOf ex:C
>
> which is a lot more readable and unambiguous.
>
> Cheers
>
> Gordon
>
> Gordon Dunsire
> Depute Director
> Centre for Digital Library Research
> University of Strathclyde
>
> The University of Strathclyde is a charitable body, registered in Scotland, with registration number SC015263
> ________________________________________
> From: List for discussion on Resource Description and Access (RDA) [[log in to unmask]] On Behalf Of Karen Coyle [[log in to unmask]]
> Sent: 02 December 2008 23:31
> To: [log in to unmask]
> Subject: [DC-RDA] Scenario 5
>
> I read through scenario 5 as well as I could (I didn't go through all
> of the code, of course.). I don't have many comments, but it did give
> me some ideas for some new scenarios to test out some things. See
> below.
>
> First, the comments:
> 1) the scenario lists "place of production" and "publisher". This
> may be music bibliography practice, but I would have expected "... of
> production" and "producer" or "of publication" and "publisher."
> 2) the scenario lists copyright date; I suspect this is being used
> as the date of publication in the bibliographic record, and therefore
> that field should be included in the scenario.
> 3) I found the order of the FRBR Group 1 statements backwards to how
> I think of them, e.g.:
> "ex:C frbr:embodiment ex:D"
> means that D is the embodiment of C. or perhaps C is embodied by D.
> How does one determine the direction? Is it clear in the
> registered FRBR relationships? (also, I'm assuming that we're using
> the group listed as "FRBR relationships as concepts" - right,
> Alistair?)
>
> 4) persons are getting coded with language indicators:
> ex:I rdf:type frbr:Person ;
> rdfs:label "Jerome Kessler"@en ;
>
> I've always thought it was very difficult to assign languages to
> names. Do we want to do this? There was a whole committee that was
> supposed to figure out languages for authority record fields (Diane,
> you and I were on that, weren't we?). It fell apart for various
> reasons, not the least of which that there may not be an answer. At
> the same time, the authority files are filled with language variations
> on names (e.g. "Touen, Makū" for Mark Twain (jp?)). I'm just not sure
> what to do about this, but it rang some bells for me.
> [Aside: when people want to assign languages to titles, etc., I always
> pull out my various examples: Book in English with title: "Marie
> Antoinette" - English or French? Same book in French. ? or my favorite
> bad restaurant name: "Pasta Cuisine" - Italian? French? or
> all-American?)
>
> As for new scenarios, here are three that I'm planning to add:
>
> 1. Manifestation that is part of a series; the catalog also has a
> record for the series.
> 2. Manifestation that is part of a series; the catalog does not have
> (and doesn't want to have) a record for the series
> 3. Manifestation that is an expression of a work, but there is no
> information about the work (I'll do one that is a translation of a
> work for which you have no catalog entry and no info)
>
> As an avowed non-cataloger, I will welcome appropriate modifications
> to my scenarios when I get them done.
> Thanks,
> kc
>
> --
> -- ---
> Karen Coyle / Digital Library Consultant
> [log in to unmask] http://www.kcoyle.net
> ph.: 510-540-7596 skype: kcoylenet
> mo.: 510-435-8234
> ------------------------------------
--
Alistair Miles
Senior Computing Officer
Image Bioinformatics Research Group
Department of Zoology
The Tinbergen Building
University of Oxford
South Parks Road
Oxford
OX1 3PS
United Kingdom
Web: http://purl.org/net/aliman
Email: [log in to unmask]
Tel: +44 (0)1865 281993
|