Martin's original suggestion involved identifying contexts where we could express compound values as a single string. This approach potentially has merit where such a string, as a whole, is in a format which is meaningful within existing systems and processible by existing software. As you say, there is a direct trade-off between the convenience and structural simplicity of having a single string (and an associated single 'unit') and the [lack of] potential for native RDF querying of the contents of that string.
My concern with this approach is that standard mechanisms for interacting with the data will not expect these sorts of compound values. This would also affect other ongoing discussions, such as compound monetary amounts or other dimensions.
For example, if there are subfield indicators or XML elements embedded within a literal, rather than using the model to manage this information, queries at the model level will not work. If “Dr” is not a separate Appellation from “Snoopy”, with an appropriate Type associated with it to ensure it is known to be a prefix rather than a first name, it will be invisible to SPARQL or any other graph query language.
For names, which already support partitioning, the answer seems obvious to me that we should continue to use the model as intended. The consistency for compound dimensions needs further discussion. Similarly the value range for dimensions should follow existing patterns (P81a anyone?) rather than trying to embed one format within another.
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 ????
On 11/21/2018 6:58 PM, Richard Light wrote:
On 15/11/2018 21:28, Martin Doerr wrote:
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 DoerrHonorary Head of theCenter for Cultural InformaticsInformation Systems LaboratoryInstitute of Computer ScienceFoundation for Research and Technology - Hellas (FORTH)N.Plastira 100, Vassilika Vouton,GR70013 Heraklion,Crete,GreeceVox:+30(2810)391625Email: firstname.lastname@example.orgWeb-site: http://www.ics.forth.gr/isl
_______________________________________________ Crm-sig mailing list Crmemail@example.com http://lists.ics.forth.gr/mailman/listinfo/crm-sig