On 5/14/13 1:59 AM, Owen Stephens wrote:
> The problem with hasCloseExternalAuthority (or hasExactExternalAuthority) is that as far as I can see these are intended to link an authority to an authority. Given agreement that BIBFRAME Authorities are not the same as LCSH or LCNAF authorities, then I'm not sure these are appropriate.
Owen, excellent point. In addition, I'm wondering why one would want
those links in the "lightweight" entity; what they would be used for. If
there is an intermediate step between bibliographic description and a
full-blown library authority file, it would seem to me that the
"lightweight" would need to carry the "immediate need" properties for
display and indexing, and relationships to other authority files (which
is what these URIs represent) would be a role of the authority data.
p.s. I will get around to the transcription question, but haven't had
clear thoughts yet.
> I think it comes back to your question in the "BIBFRAME Authority - Terminology" thread - what is the nature of a BIBFRAME Authority. This question bothers me as well, and is one of the reasons I proposed splitting out the concept of transcription in the "BIBFRAME Authority - Transcription" thread I started (no takers on that so far 'tho'!) - to try to distil the BIBFRAME Authority until we have the essence of what it is. I think until I have a better grasp of this I'm going to struggle with the semantics of how a BIBFRAME Authority links to 'Authority Files'
[log in to unmask] http://kcoyle.net