In the "subclassing" scenario, I would not expect that discovering that IssnIdentifier has the property of being a subclass of bf:Identifier would require _any_ inferencing. It would normally be available as a triple just by de-referencing the URI of IssnIdentifier. Making use of that fact to understand that a value for IssnIdentifier can be treated as a bf:Identifier in some application would require inferencing, but not the mere assertion. In contrast, if one is obtaining types from domains, it is impossible even to arrive at the assertion IssnIdentifier rdfs:subClassOf bf:Identifier without inference.
The University of Virginia Library
On Nov 7, 2014, at 11:41 PM, Karen Coyle <[log in to unmask]> wrote:
> Thanks, Rob. I do see what you are intending here. From this, I assume that a reason for using subclassing rather than domains is that the effort to infer that Issnidentifier is a sub-class of bf:Identifier is less than (or different from) the effort to infer that same information based on a property with a domain. Is that the case?