RDA/RDF examples to be validated #200
Comments
|
The only thing here that I see that is not conformant is that the instance of Expression requires a value of the property rdae:P20311 (appellation of expression) or one of its rdfs:subProperties. Otherwise, this looks like it is conformant. |
|
thanks for your help |
|
Thanks for sharing this. |
|
I completely agree with you. In this project we process a unimarc to RDA conversion for ABES and we choose not to modify the value used in Unimarc notices. With the idea that a second process directly on the rdf graph would clean the string values (remove "ISBN" for example) or resolve string values into links. Thanks for your comment. In your example you give a rdfs:label to each resource, which is a good idea, at least for a visualisation of the graph. |
|
That is exactly why we added rdfs:label. It is emphatically not meant to replace any of the RDA properties. |
|
I don't think this is good practice. A nomen is a string label linked to its referent entity. As such, a nomen itself cannot have a different string label; that is why there is no 'appellation of nomen' in RDA. You cannot work around this by using a non-RDA property like rdfs:label without breaking the model. Instead, you can treat the value of rdfs:label as another nomen string for the same entity. It is not necessary to mint a second nomen to do this; you can use the nomen string directly, as a value of rdan:P80113 "is equivalent to". The Toolkit has the instruction 'Record this element as a value of Nomen: nomen string or as an instance of a Nomen'. In this case, the datatype element should be used because its range is a literal (nomen) string: For Lian's example: ex:n3_2 # Nomen no. 2 = ISBN van manifestatie no. 3 This approach is extensible to include other variants of the 'same' ISBN, such as with hyphens. It is essentially a specific case of a nomen cluster; see the discussion at uwlib-cams/MARC2RDA#340 Note that it is clearer to use datatype and object properties, |
|
I see your point. The decision to use rdfs:label was a general one, but the implications for the Nomen entity were clearly not thought through well enough. I guess we will have to review the decision. |
|
I publish a new example of a notice. Any comment or remark are welcome ============Classes@Prefix rdac: http://rdaregistry.info/Elements/c/ . ============RDA Entity@Prefix rdax: http://rdaregistry.info/Elements/x/ ; ============Work@Prefix rdaw: http://rdaregistry.info/Elements/w/ . ============Expression@Prefix rdae: http://rdaregistry.info/Elements/e/ . ============Manifestation@Prefix rdam: http://rdaregistry.info/Elements/m/ . ============Agent@Prefix rdaa: http://rdaregistry.info/Elements/a/ . ============Place@Prefix rdap: http://rdaregistry.info/Elements/p/ . ============Timespan@Prefix rdat: http://rdaregistry.info/Elements/t/ . ============Nomen@Prefix rdan: http://rdaregistry.info/Elements/n/ . ============Autres@Prefix xsd: http://www.w3.org/2001/XMLSchema . ============Workhttps://www.sudoc.fr/003448738/work/1 a rdac:C10001 ; # is a work ============Expressionhttps://www.sudoc.fr/003448738/expression/1 a rdac:C10006 ; # is an expression ============Manifestionhttps://www.sudoc.fr/003448738/manifestation a rdac:C10007 ; # is a manifestation ============NomenDefining nomen 1 -- Access Point Workhttps://www.sudoc.fr/003448738/work/1/nomen/1 a rdac:C10012 ; # is a nomen Defining nomen 2 -- Titre Workhttps://www.sudoc.fr/003448738/work/1/nomen/2 a rdac:C10012 ; # is a nomen Defining nomen 3 -- Titre Expressionhttps://www.sudoc.fr/003448738/work/1/nomen/3 a rdac:C10012 ; # is a nomen Defining nomen 4 -- Acess point Expressionhttps://www.sudoc.fr/003448738/work/1/nomen/4 a rdac:C10012 ; # is a nomen Defining nomen 5 -- Titre Manifestationhttps://www.sudoc.fr/003448738/work/1/nomen/5 a rdac:C10012 ; # is a nomen Defining nomen 6 -- Acess point Manifesttionhttps://www.sudoc.fr/003448738/work/1/nomen/6 a rdac:C10012 ; # is a nomen Defining nomen 7 -- Identifier Manif (ID notice)https://www.sudoc.fr/003448738/manifestation/nomen/7 a rdac:C10012 ; # is a nomen Defining nomen 8 -- Identifier Manif (ISBN)https://www.sudoc.fr/003448738/manifestation/nomen/8 a rdac:C10012 ; # is a nomen Defining nomen 9 -- URI id autre (ark BnF) Manifhttps://www.sudoc.fr/003448738/manifestation/nomen/9 rdac:C10012 ; # is a nomen Defining nomen 10 -- id EAN Manifhttps://www.sudoc.fr/003448738/manifestation/nomen/10 a rdac:C10012 ; # is a nomen |
|
it is a conversion of an unimarc notice - we made the choice not to convert the values, which explain the string for place for example. |
delahousse
changed the title
|
So we have a common frame of reference, I am reproducing the UNIMARC for this resource from the BnF: 000 nam 22 450 |
|
yes, thanks to have publish the original unimarc notice |
|
For the moment, I will exclude a discussion of the Nomens from my analysis. Manifestation: The minimum description of manifestation requires an appellation and a value for rdam:P30139 expression manifested for at least one of the expressions embodied in the manifestation. I see that you are using rdamo:P30266 related expression of manifestation. You should instead use rdamo:P30139. The UNIMARC notice uses field 210, which does not differentiate between producers, publishers, or distributors in $a, $c or $d. For conversion purposes you might want to use the RDA elements rdamd:P30279 place of manifestation, rdamd:P30329 creator agent of manifestation, and rdamd:P30278 date of manifestation. For the phrase "Impr. en Italie" in $e of the 210, that is a place of manufacture, so you can use rdamd:P30087 place of manufacture as your property. The "manifestation statement" properties:
are intended to be used to transcribe data as it is found on the manifestation. Since it is difficult to reconstruct from a UNIMARC notice how publication information appeared on the manifestation, I would recommend not using the "manifestation statement" elements if doing a conversion from UNIMARC to RDA. For "rdamd:P30233 "ill. en noir et en coul"^^xsd:string ; # has details of layout", the 215 $c is defined in UNIMARC as other physical details. For a book, this often meant stating whether the manifestation embodied content that were illustrations. For other carriers, it could be describing physical characteristics of he manifestation. In other words, trying to map this field to a specific RDA element can be difficult. For this specific case, I would recommend using rdamd:P30453 illustrative content. But for future conversions, you may want to be conservative and use rdamd:P30137 note on manifestation for data coded in 215 $c. I also see the UNIMARC notice is coding for the RDA media type in 182 $c (182 .. $6 02 $c n $2 rdamedia). They are using the code that is available from the MARC21 standard; see https://www.loc.gov/standards/valuelist/rdamedia.html. Code "n" corresponds to the term "unmediated" from the RDA Media Type vocabulary encoding scheme (see https://www.rdaregistry.info/termList/RDAMediaType/ for the list of terms). You may wish to include this in your conversion. You could do the triple as: rdam:P30002 http://rdaregistry.info/termList/RDAMediaType/1007 instead of doing it as a literal. |
|
Expression For the values of rdaed:P20006 and rdaed:P20001, you may want to consider using an IRI. The source of the code in 101 $a is ISO 639-2. The Library of Congress Linked Data service has created IRIs for each of the 3 letter codes. See http://id.loc.gov/vocabulary/iso639-2. The source of the code for 181 $c is indicated in $2 and is "rdacontent", which comes from https://www.loc.gov/standards/valuelist/rdacontent.html, which itself is derived from the RDA Content Type vocabulary encoding scheme (http://rdaregistry.info/termList/RDAContentType). The code "txt" in rdacontent is equivalent to the concept http://rdaregistry.info/termList/RDAContentType/1020. rdae:P20006 http://id.loc.gov/vocabulary/iso639-2/fre ; # has language of expression |
|
I have no comments about the values of the Work properties. |
|
Nomens: For the manifestation, you have these Nomens associated with it: The description of the nomens are Defining nomen 5 -- Titre Manifestation Defining nomen 6 -- Access point Manifesttion Defining nomen 7 -- Identifier Manif (ID notice) Defining nomen 8 -- Identifier Manif (ISBN) Defining nomen 9 -- URI id autre (ark BnF) Manif Defining nomen 10 -- id EAN Manif Let's first talk about nomens 7 and 9, which you provide as values of rdamo:P30004 has identifier for manifestation. These are not actually identifiers for your manifestation, they are identifiers for resources that are describing your manifestation. See the definition of UNIMARC 001 and 003. UNIMARC field 001 is a local identifier; field 003 is a persistent identifier, i.e. an IRI. RDA provides the relationship rdam:P30462 is manifestation described with metadata by, to relate the manifestation to a resource that is describing it. For your SUDOC local identifier you could do the following: https://www.sudoc.fr/003448738/manifestation rdamd:P30462 "003448738"^^xsd:string . # is manifestation described with metadata by If you wanted to indicate this is a SUDOC system number, you would need to reify the triple. Once it is reified, any of the RDA work elements may be used to describe the metadata statement. For my example I am using RDF reification, although other methods could also produce the same results: https://www.sudoc.fr/003448738/manifestation rdamd:P30462 "003448738"^^xsd:string . # is manifestation described with metadata by For the persistent identifier for the BnF, I would prefer to have the value be an IRI: For the value of nomen 6, you are providing 3 different nomen strings, but this is incorrect. A nomen must have one and only one nomen string associated with it. From what I can tell, it looks like you want to have the access point in the form of: Title of manifestation. General material designation**. Statement of responsibility. This should be given as one nomen string: Nomens 5, 8, and 10 look good to me. I would like to stress that unless you are wanting to provide more information about a nomen, it can just be provided as a literal value. So for title of manifestation and access point for manifestation, you could do the following: rdamd:P30134 "La mer et la vie : chronique de la mer des origines au XXe siècle"^^xsd:string ; # has title of manifestation **there is no equivalent for General material designation in RDA because GMD mixed elements of content and carrier together. The GMD may be used in an access point, but if your notices have the carrier type coded in field 183, you may want to use that instead in constructing your access point. |
|
The comments I provided about multiple nomen strings for nomen 6 would also apply to nomens 1 and 4. The comments about only providing a literal value instead of declaring a nomen also apply to nomens 1-4. |
|
I did not have time to come back to you but thanks a lot for all those very useful comments and your help. Will come back with a new version of the rda notice - best - jean |
|
#============Classes #============RDA Entity #============Work #============Expression #============Manifestation #============Agent #============Place #============Timespan #============Nomen #============Autres #============Work #============Expression #============Manifestion #============Nomen #Defining nomen 2 -- Titre Work #Defining nomen 3 -- Titre Expression #Defining nomen 4 -- Access point Expression #Defining nomen 5 -- Titre Manifestation #Defining nomen 6 -- Acess point Manifestation #Defining nomen 7 -- Identifier Manif (ID notice) #Defining nomen 8 -- Identifier Manif (ISBN) #Defining nomen 10 -- id EAN Manif |
|
I publish this new version of the RDA notice, taking into account your feedback (thanks) |
Hello,
I started to write RDA/RDF just for the purpose of the first training of the team. We will build on during the alignment process of UNIMARC / RDA.
I choose to use object properties when relating RDA entities to each other.
example after review by Damian Iseminger
@Prefix rdac: http://rdaregistry.info/Elements/c/ .
@Prefix rdaa: http://rdaregistry.info/Elements/a/ .
@Prefix rdaao: http://rdaregistry.info/Elements/a/object/ .
@Prefix rdae: http://rdaregistry.info/Elements/e/ .
@Prefix rdam: http://rdaregistry.info/Elements/m/ .
@Prefix rdan: http://rdaregistry.info/Elements/n/ .
@Prefix rdawo: http://rdaregistry.info/Elements/w/object/ .
@Prefix rdaeo: http://rdaregistry.info/Elements/e/object/ .
@Prefix rdaed: http://rdaregistry.info/Elements/e/datatype/ .
@Prefix rdamo: http://rdaregistry.info/Elements/m/object/ .
@Prefix rdamd: http://rdaregistry.info/Elements/m/datatype/ .
@Prefix xsd: http://www.w3.org/2001/XMLSchema# .
Defining the Work (abstract concept of the book)
http://example.org/works/001 a rdae:C10001 ; # Work
rdawo:P10436 http://example.org/person/1 ; # has author person
rdawo:P10078 http://example.org/works/001/expression/1; # has expression of work
rdawo:P10223 http://example.org/works/001/nomen/1. # has preferred title of work
Defining a Nomen of the work
http://example.org/works/001/nomen/1 a rdac:C10012;
rdan:P80068 "To Kill a Mockingbird" . # has nomen string
Defining the Expression (specific expression of the work)
http://example.org/works/001/expression/1 a rdae:C10006 ; # Expression
rdaeo:P20059 http://example.org/works/001/expression/1/manifestation/1; #has manifestation of expression
rdaeo:P20311 http://example.org/works/001/expression/1/nomen/1; #has appellation of expression
rdaed:P20006 "English" . # has language of expression
Defining a Nomen for expression identification
http://example.org/works/001/expression/1/nomen/1 a rdac:C10012;
rdan:P80068 "To Kill a Mockingbird" . # has nomen string
Defining the Manifestation (physical publication)
http://example.org/works/001/expression/1/manifestation/1 a rdam:C10007 ; # Manifestation
rdamo:P30083 http://example.org/corporate/1 ; # has publisher agent
rdamo:P30004 http://example.org/works/001/expression/1/manifestation/1/nomen/1; #has identifier for manifestation
rdamd:P30011 "1960"^^xsd:gYear . # has date of publication
Defining a Nomen for manifestation identification
http://example.org/works/001/expression/1/manifestation/1/nomen/1 a rdac:C10012;
rdan:P80068 "ISBN-123-456-789" . # has nomen string
Defining the Person (Harper Lee)
http://example.org/person/1 a rdaa:C10004 ; # Person
rdaao:P50117 http://example.org/agents/HarperLee/nomen/1. # has preferred name of person
Defining a Nomen of Harper Lee
http://example.org/agents/HarperLee/nomen/1 a rdac:C10012;
rdan:P80068 "Harper Lee" . # has nomen string
Defining the corporate body J. B. Lippincott & Co.
http://example.org/corporate/1 a rdac:C10005;
rdaao:P50041 http://example.org/corporate/1/nomen/1. # has preferred name of corporate body
Defining a Nomen of J. B. Lippincott & Co.
http://example.org/corporate/1/nomen/1 a rdac:C10012;
rdan:P80068 "J. B. Lippincott & Co." . # has nomen string
The text was updated successfully, but these errors were encountered: