So something like:
<persName><roleName type=”royal”>His Majesty</roleName> <roleName type=”academic”>Dr.</roleName> <forename>Snoopy</forename> <addName type=”nickname”>Hickup</addName> <surname>Miller</surname> <genName>Jr</genName></persName>
But one would need guidelines, esp. for the type attribute. In TEI everything can be done, and in several ways...
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
So, again, is there a good practice with XML elements ????
On 11/21/2018 6:58 PM, Richard Light wrote:
On 15/11/2018 21:28, Martin Doerr
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.
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.
Crm-sig mailing list
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,
Crm-sig mailing listCrmemail@example.com