Hi Michel,

The subclass relationship in RDF is about subsets, so if A1 is a subset of
A, then members of A1 are members of A. If the user interface knows that P
has domain A, it includes P on forms for A1 instances because those are
also instances of A.

For example, in the kennedys model included with TopBraid Composer, the
 kennedys:parent property has an rdfs:domain of kennedys:Person and
kennedys:Patriarch is a subclass of kennedys:Person, so the kennedys:parent
property appears on the form for the the kennedys:JosephKennedy instance of
kennedys:Patriach.

I wouldn't consider this to be inheritance, which I think of more in terms
of inheritance of instance behavior, but instead as the use by applications
such as TopBraid Composer (and other applications built with the TopBraid
platform) of the model to drive interface behavior.

Bob DuCharme
TopQuadrant




On Fri, Jun 20, 2014 at 5:23 AM, Bohms, H.M. (Michel) <[email protected]>
wrote:

>  Hi Holger, Scot
>
>
>
> We are very eager to get some info on our earlier posted issue:
>
>
>
> “
>
> When I define a class A and a subclass A1
>
> And a property P with domain A
>
> In tbc when instantiating A1 the property is shown. Why is that?
>
> My assumption is that this property is not ‘inherited’ to its subclass.
>
> Is that right?
>
> “
>
> Thx very much for your consideration. In NL were working on a national
> modeling guide in which linking classes <> properties is an important issue
> (typically difficult/different for many involved since it differs from
> tradiotional modeling approaches).
>
> Thx Michel
>
>
>
>
>
>
> Dit bericht kan informatie bevatten die niet voor u is bestemd. Indien u
> niet de geadresseerde bent of dit bericht abusievelijk aan u is
> toegezonden, wordt u verzocht dat aan de afzender te melden en het bericht
> te verwijderen. TNO aanvaardt geen aansprakelijkheid voor de inhoud van
> deze e-mail, de wijze waarop u deze gebruikt en voor schade, van welke aard
> ook, die verband houdt met risico's verbonden aan het elektronisch
> verzenden van berichten.
>
>
>
> This message may contain information that is not intended for you. If you
> are not the addressee or if this message was sent to you by mistake, you
> are requested to inform the sender and delete the message. TNO accepts no
> liability for the content of this e-mail, for the manner in which you use
> it and for damage of any kind resulting from the risks inherent to the
> electronic transmission of messages.
>
>  --
> -- You received this message because you are subscribed to the Google
> Group "TopBraid Suite Users", the topics of which include Enterprise
> Vocabulary Network (EVN), TopBraid Composer, TopBraid Live, TopBraid
> Insight, SPARQLMotion, SPARQL Web Pages and SPIN.
> To post to this group, send email to
> [email protected]
> To unsubscribe from this group, send email to
> [email protected]
> For more options, visit this group at
> http://groups.google.com/group/topbraid-users?hl=en
> ---
> You received this message because you are subscribed to the Google Groups
> "TopBraid Suite Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to [email protected].
> For more options, visit https://groups.google.com/d/optout.
>

-- 
-- You received this message because you are subscribed to the Google
Group "TopBraid Suite Users", the topics of which include Enterprise Vocabulary 
Network (EVN), TopBraid Composer, TopBraid Live, TopBraid Insight, 
SPARQLMotion, SPARQL Web Pages and SPIN.
To post to this group, send email to
[email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/topbraid-users?hl=en
--- 
You received this message because you are subscribed to the Google Groups 
"TopBraid Suite Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
For more options, visit https://groups.google.com/d/optout.

Reply via email to