Action from the SIG meeting to send information about partitioning of names:
Personal Names: MARC has three subfields for name, in the bibliographic USMARC: https://www.loc.gov/marc/bibliographic/bd100.html Which has a lot of name fields, but also a lot of related things to a name (such as date of a work in subfield f) And the equivalent in MODS, for the type of namePart: https://www.loc.gov/standards/mods/userguide/name.html#namepart given, family, date, and termsOfAddress In the Getty AAT vocabulary, we have the following types of names http://www.getty.edu/vow/AATHierarchy?find=&logic=AND¬e=&subjectid=300266386 Which include both type of the complete name (e.g. noms de guerres) and parts of names (middle name). And name related concepts generally http://www.getty.edu/vow/AATHierarchy?find=&logic=AND¬e=&page=1&subjectid=300404653 Which includes prefix/suffix/title and similar. Place Names: For places, we have looked at the FGDC endorsed standard: https://www.fgdc.gov/fgdc-news/fgdc-endorses-address-data-standard https://www.fgdc.gov/standards/projects/address-data Which is … comprehensive, to say the least. We then cherry-picked the bits that we thought most useful, given the level of data description that we need for cultural heritage purposes. Rob From: Crm-sig <[email protected]> on behalf of Martin Doerr <[email protected]> Date: Wednesday, November 21, 2018 at 11:11 PM To: "[email protected]" <[email protected]> Subject: Re: [Crm-sig] ISSUE: representing compound name strings Dear Richard, XML is even better. The distinction between XML tags and MARC subfield markers is not so substantial. An XML file is still a string. The question is about RDF, putting a compound into rdfs:Literal. So, again, is there a good practice with XML elements ???? Cheers, Martin On 11/21/2018 6:58 PM, Richard Light wrote: On 15/11/2018 21:28, Martin Doerr wrote: Dear All, I would expect that the library or archival community do have a good practice how to "squeeze" a compound name, such as : "His Majesty Dr. Snoopy Hickup Miller Jr", with respective separators, in a machine readable string, that could be used as custom datatype in an rdfs:Literal as one instance of Appellation, rather than defining all possible name constituents as individual rdf properties. Could be a MARC string? XML? TEI? This would be very helpful for our users. Martin, I'm pretty sure that the most recent attempt at doing this will be the subfield markers ($a, etc.) in MARC. which date from the era of punched cards. The requirement that all of the name appears in a single string will rule out anything that might have been done in XML (where you might typically use attributes or subelements) or TEI (which is, after all, simply an XML application). It's a nice idea, which follows the approach of encoding one 'compound' value as a single string, but I don't think we will find a ready-made standard for it. Richard Best, Martin -- Richard Light _______________________________________________ Crm-sig mailing list [email protected]<mailto:[email protected]> http://lists.ics.forth.gr/mailman/listinfo/crm-sig -- ------------------------------------ Dr. Martin Doerr Honorary Head of the Center for Cultural Informatics Information Systems Laboratory Institute of Computer Science Foundation for Research and Technology - Hellas (FORTH) N.Plastira 100, Vassilika Vouton, GR70013 Heraklion,Crete,Greece Vox:+30(2810)391625 Email: [email protected]<mailto:[email protected]> Web-site: http://www.ics.forth.gr/isl
