 |
 |
My thanks to Rob Sanderson, his explanation is very helpful. I can see the need for having title as a resource when there are parsing and categorizing options in play, and the logic of framing the encoding to support that; and understand now that each of the titles in the "Hamlet" example would be a separate resource, not the same resource. The resource is used to enable added structure in specific graphs, not to describe a generalized entity. Stephen On Fri, May 15, 2015 at 11:03 AM, Karen Coyle <[log in to unmask]> wrote: > Simon, DC 1.1 [1] (the original DC 15) is an annotation property. > dct:title in the dcterms namespace [2] is defined as a literal. For RDF, > it's always better to use the dcterms namespace properties. > > [1] http://purl.org/dc/elements/1.1/title > [2] http://purl.org/dc/terms/title > > > On 5/15/15 7:51 AM, Simon Spero wrote: > > On May 15, 2015 10:32 AM, "Robert Sanderson" <[log in to unmask]> wrote: > > > > > > > So if all we ever need is one or more equally preferred strings as the > title, and there are no parts, properties or relationships, then we should > just use dc:title with a string. Otherwise, we need to use a resource. > > And even in this case, the Dublin Core title property is not ideal, since > it is an annotation property. > > Simon > > > -- > Karen [log in to unmask] http://kcoyle.net > m: +1-510-435-8234 > skype: kcoylenet/+1-510-984-3600 > > -- Stephen Hearn, Metadata Strategist Data Management & Access, University Libraries University of Minnesota 160 Wilson Library 309 19th Avenue South Minneapolis, MN 55455 Ph: 612-625-2328 Fx: 612-625-3428 ORCID: 0000-0002-3590-1242