Check out this document which contains a recent mapping of the new ISBD Area 0 
terms to the RDA terms for content and media types (ISBD does not have values 
for carrier types). The RDA/ONIX Framework (ROF) is the larger framework from 
which RDA got its content, media, and carrier types:



http://www.ifla.org/files/cataloguing/isbdrg/area-0-analysis.pdf



Equivalence in ISBD and RDA is determined by how they map to categories of 
something called a "base content category" in the bigger RDA/ONIX Framework. 
The base content category is derived from a unique combination of values for 
character, sensory mode, image dimensionality, and image movement. After the 
base content category is matched up, then one can look at the additional 
qualifiers.



In the RDA/ONIX Framework, "cartographic" and "computer" are actually 
form/genre qualifiers that are not part of the base content category, but are 
allowed attributes as form/genre (an open value set) in the RDA/ONIX Framework 
(see Recommendation #3 at http://www.loc.gov/marc/marbi/2007/5chair10.pdf).





---------------



Comparing ISBD and RDA:



ISBD: dataset (cartographic)

RDA: cartographic dataset



ISBD: dataset

RDA: computer dataset



---------------



Interestingly, in full 1:1 mapping of RDA to ISBD, sometimes RDA is shorter 
than ISBD:



Example:

ISBD: image (cartographic ; still ; 2-dimensional ; tactile)

RDA: cartographic tactile image



Considering ISBD's "image (cartographic ; still ; 2-dimensional ; tactile)", 
the attributes that are captured are these (in an order which is similar to the 
RDA/ONIX Framework's):

form, type (for the form/genre "cartographic"), motion, dimensionality, sensory 
specification.



---------------



For those interested in coming up with shorter labels for Content Type the key 
then is to map a Content Type term to combinations of the more basic RDA/ONIX 
Framework categories:



>From http://www.dlib.org/dlib/january07/dunsire/01dunsire.html:
"Basic higher-level content and carrier categories are constructed by taking a 
single primary value from one or more attributes of the content and carrier 
attribute sets respectively. ...  For example, the basic content category 
defined by <Character="image" + SensoryMode="sight" + 
ImageDimensionality="two-dimensional" + ImageMovement="moving"> is equivalent 
to code 06 of ONIX list 81, which has the descriptive label "moving images". 
The basic carrier category defined by <StorageMediumFormat="file server + 
HousingFormat="not applicable" + IntermediationTool="computer"> is equivalent 
to code DH of ONIX list 7, with the descriptive label "online resource"."



The framework allows for communities to devise their own labels. But in 
devising new labels, one has to map them correctly to the specific combination 
of values in the RDA/ONIX Framework.



---------------



As an interesting example of a different label, the equivalent to RDA's "spoken 
word" in ONIX is "performance - spoken word" (List 81, Code 02).

http://www.editeur.org/files/ONIX%20for%20books%20-%20code%20lists/ONIX_BookProduct_CodeLists_Issue_12.html



ONIX has the content type "Data" (List 81, Code 09).



Interestingly, a new content type appears in ONIX List 81, Code 12-- "Maps 
and/or other cartographic content", which would be allowed under the RDA/ONIX 
Framework form/genre attribute for Content Type. So RDA's "cartographic 
dataset" and ISBD's "dataset (cartographic)" might not then map to a single 
ONIX term, but to two separate ones.



"Dataset" (or "Data" or "Program") seems to be a Content Type that falls 
outside the scope of the regular Contents Types based on human perception. The 
FRBR "expression" in this case is digital content processed (perceived?) by a 
computer.



---------------



Other links:



ISBD Area 0 at http://www.ifla.org/files/cataloguing/isbd/area-0_2009.pdf



RDA/ONIX Framework - http://www.loc.gov/marc/marbi/2007/5chair10.pdf







Thomas Brenndorfer

Guelph Public Library



> -----Original Message-----

> From: Resource Description and Access / Resource Description and Access

> [mailto:RDA-L@LISTSERV.LAC-BAC.GC.CA] On Behalf Of Karen Coyle

> Sent: February 14, 2011 1:59 PM

> To: RDA-L@LISTSERV.LAC-BAC.GC.CA

> Subject: Re: [RDA-L] rdacontent terms - dataset

>

> I'm hoping that someone from the JSC can explain better, but it looks

> to me that a cartographic dataset has come particular characteristics.

> Section 3.19.7.3 of RDA says:

>

> 3.19.7.3 R ecording Digital Representation of

> Cartographic Data

> For digitally encoded cartographic data, record the following

> information if it can be readily ascertained and is considered

> important for identification or selection:

> ? data type (i.e., raster, vector, or point)

> ? object type (i.e., point, line, polygon, or pixel)

> ? number of objects used to represent spatial information.

>

> The definition in chapter 6 of RDA for computer dataset says:

>

> Content expressed through a digitally encoded dataset intended to be

> processed by a computer. Includes numeric data, environmental data,

> etc., used by applications software to calculate averages,

> correlations, etc., or to produce models, etc., but not normally

> displayed in its raw form. For data intended to be perceived visually

> in the form of notation, image, or three-dimensional form, see notated

> movement, notated music, still image, text, three-dimensional form,

> three-dimensional moving image and two-dimensional moving image. For

> data intended to be perceived in an audible form, see performed music,

> sounds, and spoken word. For cartographic data see cartographic

> dataset.

>

> ---

>

> I can't explain WHY this is the case, but at least there is evidence

> in RDA that the two were thought of differently.

>

> As for the possible use of dc:dataset, one thing to remember is that

> every RDA property is associated with a single FRBR entity. (Which is

> why there are things like "Extent(Manifesation)" and "Extend(Item)".

> None of the DC terms are bound to a FRBR entity, so they would be more

> general than an RDA property of similar semantics.

>

> kc

>

>

>

> Quoting Brunella Longo <brunella.lo...@yahoo.com>:

>

> > Is there any rationale for having two RDA content terms

> > ("cartographic dataset" and "computer dataset") instead of just the

> > simple DC 'dataset'?

> >

> > See

> >  - http://www.loc.gov/standards/valuelist/rdacontent.html

> >  - http://metadataregistry.org/search?term=dataset?

> >  - http://dublincore.org/usage/terms/history/#Dataset-003

> >  - http://openuplabs.tso.co.uk/datasets

> >

> >

> > Brunella Longo

> > 7 New College Court

> > London NW3 5EX

> > T +44 (0)20 72095014 (home) -  +44 (0) 75 49921488 (mobile)

> > http://www.brunellalongo.info (http://www.brunellalongo.it)

> >

> > [with apologies for cross posting]

> >

>

>

>

> --

> Karen Coyle

> kco...@kcoyle.net http://kcoyle.net

> ph: 1-510-540-7596

> m: 1-510-435-8234

> skype: kcoylenet

Reply via email to