Hi David,

you are by far not the first person to run into this issue, and you won't be the last. The meaning of rdfs:domain contradicts the intuition of most people.

Holger



On 4/8/15 6:41 PM, David Rouquet wrote:
OK, I sorted this out.

I must say I'm sorry that I posted this as a TopBraid issue when it was in fact a basic misunderstanding of RDFS semantic on my side.

Basically, when for a property P and two classes C1 and C2 I declared both :
P rdfs:domain C1
P rdfs:domain C2

I intuitively interpreted :
P rdfs:domain (C1 UNION C2)

whereas it means, according to RDFS semantics :
P rdfs:domain (C1 INTERSECTION C2)

Therefore I had the inheritance mechanism for rdfs:domain in the properties lattice totally backwards. I would argue the semantic is counter intuitive but hey, thats just how it is !

Best Regards
---
David








Le mercredi 25 mars 2015 19:26:20 UTC+1, Scott Henninger a écrit :

    David, a couple of nice resources that you may find helpful:
     1)
    http://www.topquadrant.com/knowledge-assets/product-documentation/#tbcdoc
    <http://www.topquadrant.com/knowledge-assets/product-documentation/#tbcdoc>
    (both the Getting Started Guide and the Features Overview)
     2) Composer Help > Getting Started Guide
     3) Composer Help > User Interface Overview

    Composer is a very rich tool, so perusing these sources a bit will
    give you an idea of what the capabilities are and where to look
    for finding out how to get things done using the tool.

    And thanks for the good questions!
    -- Scott

    On 3/25/2015 4:06 AM, David Rouquet wrote:
    Well, Scott and Irene, thank you VERY MUCH for the interesting
    and extensive answers (as always :-)

    Guided by your inputs I did a couple of more checks :
    - when I select the "/show widgets for all matching properties/"
    it shows me a list of properties in the form (some of them with
    no value). This list is the same as the one proposed in the
    "/Relevant Properties/" tab that Scott pointed out.
    - This list does not contains ALL the defined properties in the
    model as I first thought. I fail however to see how the
    "relevant" properties are selected as some of them have a domain
    defined that is not a (super)class containing  the instance I'm
    editing...

    I need to check my model to be 100% sure that no error is making
    some kind of "interference".

    My two cents is that when I define the domain of a property, I
    can always assert another RDF triple that add a class in the
    domain (that is the union of all the classes declared with the
    /rdfs:domain/ property). If such a triple is not asserted, it
    does not mean that it is false, just that we don't know if it is
    true.
    Thus, the domain of a property always contains potentially every
    class except if declared otherwise (not even sure how to declare
    that...)
    Well, even if my two cents are correct, it doesn't add up... (I
    then should see all declared properties as "potentially" relevant...)

    Good news : you indirectly pointed a workaround for me.
    I discovered the "/Domain/" tab that list the properties I want
    (namely the one whose declared domain contains the instance I'm
    editing) plus a few that I don't want (namely those that have no
    specific domain declared but this is easily fixed).
    I can drag those properties into my form ET VOILA.
    I did not know such drag and drop where possible. It is really a
    nice feature of the interface.

    Thanks again
    Best regards
    --
    David







    Le mardi 24 mars 2015 23:10:51 UTC+1, Scott Henninger a écrit :

        On 3/24/2015 4:48 PM, Irene Polikoff wrote:
        <But this is not how the feature works.  It displays ALL
        property values, regardless of property definitions.  None
        are hidden. >

        I see what you are saying and I agree.

        If there already exist a triple :resource :someProperty
        :someValue, it will be shown no matter what. But as far
        as “empty” widgets, Resource Editor will only show the
        relevant properties.

        So, in reality the icon, when selected, is really showing
        all relevant property widgets plus widgets for all the
        properties that have values. When deselected, only
        properties that have values are shown.

        The only way to avoid seeing a property for which there is a
        value is by creating a custom form.

        If that is the question, then yes (!).  But if the question
        is just to find out what the relevant properties are for the
        resource, then the Relevant Properties tab is designed
        exactly for that.

        -- Scott


        From: Scott Henninger <[email protected]>
        Organization: TopQuadrant, Inc.
        Reply-To: <[email protected]>
        Date: Tuesday, March 24, 2015 at 5:36 PM
        To: <[email protected]>
        Subject: Re: [topbraid-users] Re: [TBC] : how to show only
        properties with matching domains in forms ?

        But this is not how the feature works.  It displays ALL
        property values, regardless of property definitions.  None
        are hidden. --
        You received this message because you are subscribed to the
        Google Group "TopBraid Suite Users", the topics of which
        include Enterprise Vocabulary Network (EVN), Reference Data
        Manager (RDM), TopBraid Composer, TopBraid Live, TopBraid
        Insight, SPARQLMotion, SPARQL Web Pages and SPIN.
        To post to this group, send email to [email protected]
        ---
        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
        <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), Reference Data Manager
    (RDM), TopBraid Composer, TopBraid Live, TopBraid Insight,
    SPARQLMotion, SPARQL Web Pages and SPIN.
    To post to this group, send email to [email protected]
    <javascript:>
    ---
    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] <javascript:>.
    For more options, visit https://groups.google.com/d/optout
    <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), Reference Data Manager (RDM), TopBraid Composer, TopBraid Live, TopBraid Insight, SPARQLMotion, SPARQL Web Pages and SPIN.
To post to this group, send email to [email protected]
---
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] <mailto:[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), 
Reference Data Manager (RDM), TopBraid Composer, TopBraid Live, TopBraid Insight, 
SPARQLMotion, SPARQL Web Pages and SPIN.
To post to this group, send email to [email protected]
--- 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