Well... as you brought it up ... 
[oh wait, was that me... well ... as you took the bait ...]

Either a title is a literal string, or a resource.  Currently there's a mess with both being used at the same time.  Also label as somehow distinct from title.

Cleaning up this and either having title as a literal or as a resource, but not both at once, would be a great improvement.

Rob


On Thu, Jul 24, 2014 at 1:49 PM, [log in to unmask] <[log in to unmask]> wrote:
Indeed. These kinds of generated resources also appear in the output of the experimental XQuery transform available at https://github.com/lcnetdev/marc2bibframe and presumably used at http://bibframe.org/tools/transform/start and to produce the example Karen Coyle shows below.

I, too, have been wondering a bit about the intention behind them, particularly because it seems to me (and I may be misunderstanding the operation of that transform) that bf:Works receive titles-linked-by-identifier (as shown in the example below) in the bf:workTitle property but bf:Instances receive literal titles in the bf:title property…

---
A. Soroka
The University of Virginia Library

On Jul 24, 2014, at 4:38 PM, Karen Coyle <[log in to unmask]> wrote:

> On 7/24/14, 1:27 PM, Denenberg, Ray wrote:
>> (I don't think we've thought much about providing identifiers for titles.)
> I hope you *have* because they are in your data ;-)
>
> bf:workTitle <http://bibframe.org/resources/Ahx1405278232/1706459title7> ;
>
> <http://bibframe.org/resources/Ahx1405278232/1706459title7>
>
>    bf:titleValue "The adventures of Tom Sawyer" ;
>
>    a bf:Title .
>
>  bf:instanceTitle <http://bibframe.org/resources/Ahx1405278232/1706459title33>
>
> <http://bibframe.org/resources/Ahx1405278232/1706459title33>
>
>    bf:titleValue "The adventures of Tom Sawyer" ;
>
>    a bf:Title .
>
>
> Those are from a BF record, converted from MARC.[1] I found them rather odd, myself. It makes some sense to give identifiers to work titles, although generally the work title alone does not identify a work.  But I think that this is actually evidence for a discussion that we have not had yet on the massive level of indirection (blank and non-blank nodes) in BIBFRAME.
>
> kc
>
> [1] http://bibframe.org/resources/Ahx1405278232/1706459.rdf
>
> --
> Karen Coyle
> [log in to unmask] http://kcoyle.net
> m: 1-510-435-8234
> skype: kcoylenet



--
Rob Sanderson
Technology Collaboration Facilitator
Digital Library Systems and Services
Stanford, CA 94305