One way would be to declare the authors name as it appears on the book to be its skos:prefLabel like so:
:A0 a :Book;
:author :A1 .
:A1 a :Person;
skos:prefLabel "Jane Doe";
:sameAs hub:Xxxxx.
The skos:prefLabel assumes a context of some sort, but that's always the case. That context could be as broad or narrow as the data publisher chooses.
If the context isn't declared in the data (e.g. using skos:inScheme) then the context could be "inferred" from the dataset where the URIs resolve as Linked Data. Note that :A0 and :A1 could resolve to the same Linked Data graph, with :A0 as the primary entity.
There are various details to consider, but it would solve the problem.
Jeff
> On Jul 4, 2016, at 11:53 AM, Kučera Jan <[log in to unmask]> wrote:
>
> Oh I didn't expect you cannot attach/link visuals (or any arbitrary attachment) to an instance - in one of the cases we just took photos of all the books while labelling them and expect the cataloguing process to be completely based on the photos.
>
> The problem with pictures, however, is that they are difficult to search, aggregate etc.
>
> -----Original Message-----
> From: Young,Jeff (OR) [mailto:[log in to unmask]]
> Sent: Monday, July 4, 2016 4:44 PM
> To: Kučera Jan <[log in to unmask]>
> Cc: Bibliographic Framework Transition Initiative Forum <[log in to unmask]>
> Subject: Re: [BIBFRAME] Extending authorities
>
> I can think of various ways, but none of them trivial.
>
> One way to kick the can down the road would be to add an image property to the Instance. That way people could take a photo of their copy to capture various nuances like this rather than transcribe them. Sometimes a picture is worth a thousand words. It raises the question of use cases. Back in the MARC days digital cameras didn't exist and there was no mechanism to link the description to a visual representation. Now that those exist, it seems worth questioning the old ways.
>
>> On Jul 4, 2016, at 5:42 AM, Kučera Jan <[log in to unmask]> wrote:
>>
>> Thanks Jeff,
>>
>> Not sure if you can distinguish between language and script using the query, but that example was probably misleading. The idea was to preserve what is on the instance, even if it is misspelled or uses titles or is abbreviated.
>>
>> Thanks!
>> Jan
>>
>> -----Original Message-----
>> From: [log in to unmask] [mailto:[log in to unmask]] On Behalf Of Young,Jeff (OR)
>> Sent: Monday, July 4, 2016 2:09 AM
>> To: Bibliographic Framework Transition Initiative Forum <[log in to unmask]>
>> Subject: Re: [BIBFRAME] Extending authorities
>>
>> From a general discovery POV, it seems like this case could be handled with a query rather than vocabulary. For example:
>>
>> SELECT ?authorName
>> WHERE {
>> :instance1 :inLanguage ?bcp47;
>> :author ?author .
>> ?author :name ?authorName .
>> FILTER(LANG(?authorName) = ?bcp47)
>> }
>>
>> I don't know if BIBFRAME is currently recommending BCP47 to describe the language of material, but it's worth considering.
>>
>> Jeff
>>
>>> On Jul 3, 2016, at 7:56 PM, Kučera Jan <[log in to unmask]> wrote:
>>>
>>> Hello,
>>>
>>> in a bibframe catalogue entry, can I link to an existing authority but specify the particular text used in an instance? (for example, if the author is written in different language or script)
>>>
>>> Or is there a similar equivalent for author as work->instance?
>>>
>>> Thanks,
>>> Jan
|