Clarrification of implications of <hasInstance>

Within a subject scheme map, hasInstance says that there is an instance-of
relationship between container and contained subjects, e.g.:

<hasInstance>
  <subject keys="person">
    <subject keys="three-initial-corp"/>
  </subject>
</hasInstance>

However, what is the implication if the contained subject has itself
subjects, e.g.:

<hasInstance>
  <subject keys="person">
    <subject keys="three-initial-corp">
      <subject keys="some-subject"/>
    </subject>
  </subject>
</hasInstance>

Ignoring that this is probably nonsensical ontologically, what is the
implication in this case:

1. This is nonsense and the meaning for "some-subject" is undefined.

2. "some-subject" is also an instance of "person"

3. "some-subject" is an instance of the subject "three-initial-corp"

Based on analogy to <hasKind>, which is transitive, I might expect
interpretation (3) but logic suggests either (1) or (2).

The current subject scheme docs don't seem to say. Should we clarify?

Cheers,

E.


-- 
Eliot Kimber
Senior Solutions Architect
"Bringing Strategy, Content, and Technology Together"
Main: 512.554.9368
www.reallysi.com
www.rsuitecms.com