Print

Print


This is a great thread and I very much hope it does lead revisions of 
the bibframe class definitions and descriptions. I think Kevin's 
description and modification of Rob's example (where a bf:Person is a 
person in the sense of foaf:Person and then one hangs authority 
information off that) would significantly improve bibframe and make it 
play much more nicely with other linked data.

Cheers,
Simeon


On 7/10/14 12:25 PM, Ford, Kevin wrote:
> ---- An Authority represents a key Concept or Thing.  Works and
> Instances, for example, have defined relationships /to/ these
> important Concepts and Things. ----
>
> I'm not saying that that is perfect, but does it get closer?
>
> I think that a revised definition for Authority would free us up to
> modify the definition of Person to something like:
>
> ---- A person, whether real, fictional, etc. ----
...
>
> Again, with the revised definitions, I actually think we're pretty
> close to this.  I can assuredly say that this is more or less how I
> have viewed bf:Person personally.  I would revise Rob's example ever
> so slightly (and make it even simpler):
>
> _:LotR a bf:Work ; rel:cre _:Tolkien .
>
> _:Tolkien a bf:Person; foaf:name "J.R.R. Tolkien" ; bf:hasAuthority
> _:lcnaf ; bf:authorizedAccessPoint "Tolkien, J.R.R" .
>
> _:lcnaf a madsrdf:PersonalName . madsrdf:authoritativeLabel "Tolkien,
> J.R.R" .