Print

Print


Rob, do, or how do, the defined domains and ranges affect this? For 
example, I looked at just the "assigner" ones, and for domains and 
ranges I got:

audienceAssigner --> assigner [domain:Intended Audience] [range:literal]
identifierAssigner --> assigner [domain:Identifier] [range:literal]
classificationAssigner--> assigner [domain:Classification] [range:literal]
authorityAssigner --> assigner [domain:Authority] [range:Agent]

Except for authorityAssigner the range is literal, so a property 
"assigner" with a range of literal would work for them. 
authorityAssigner has a range of Agent - which wouldn't be compatible 
with a range of literal.

As for the domains, I'm not at all clear what use is expected of domains 
in BIBFRAME. Having a domain of "Classification" allows one to infer 
that any subject with the predicate classificationAssigner is therefore 
of rdfs:type "Classification." (true?) If that is true, what is the 
intended use of this inference, and how important is it in practice? Is 
it enough to justify the creation of a unique predicate?

BTW, this same type of proliferation of predicates based on domains is 
used heavily in both FRBRer and RDA, so it would be good to understand 
the necessity (or lack thereof) before we continue down this path.

kc


On 7/16/14, 4:27 PM, Robert Sanderson wrote:
>
> As promised, an initial list of predicates that could be collapsed 
> without affecting the model at all (as far as I can tell)
>
> authorityAssigner --> assigner
> authoritySource --> source
> categorySource --> source
> categoryType --> type
> categoryValue --> value
> classificationAssigner--> assigner
> classificationDesignation --> designation
> classificationEdition --> edition
> classificationItem --> item
> classificationNumber --> number
> classificationScheme --> scheme
> classificationSpanEnd --> spanEnd
> classificationStatus --> status
> classificationTable --> table
> classificationTableSeq --> tableSeq
> eventAgent --> agent
> eventPlace --> place
> eventDate --> date
> identifierAssigner --> assigner
> identifierQualifier --> qualifier
> identifierScheme --> scheme
> identifierStatus --> status
> identifierValue --> value
> audienceAssigner --> assigner
> providerName --> name
> providerPlace --> place
> providerRole --> role
> providerDate --> date
> relatorRole --> role
> titleAttribute --> attribute
> titleQualifier --> qualifier
> titleSource --> source
> titleType --> type
> titleValue --> value
> titleVariationDate --> date
>
> There are other classes of predicate that could also be changed, which 
> I'll try to discuss in a separate mail.
>
> Rob
>
> -- 
> Rob Sanderson
> Technology Collaboration Facilitator
> Digital Library Systems and Services
> Stanford, CA 94305

-- 
Karen Coyle
[log in to unmask] http://kcoyle.net
m: 1-510-435-8234
skype: kcoylenet