By 'instance-tizing' my classes (make them rdf:type my superclass), I can
get facets. I am glad that I have made some progress, but that seems like
the wrong approach since they are really classes.
Even when I do this, in 4.4 I get no search results. I migrated this
'instancetization' back to 4.2 and I get facets and search results. So I
must not have swa:FacetedSearchGadget and swa:SummarySearchResultsGadget
wired up properly. Are they supposed to be related by arg:id or some such?
In the demo, where swa:Window is used, they have arg:id values, but my
<div> approach does not. Any comments would be welcome. Examples of the two
approaches are provided below (the rest of the content is basically
identical between 4.2 and 4.4).
4.2 version:
<div class="ui-layout-center" width="600px">
<swa:Header arg:label="{= spl:object(?viewTemplate,
ssfhtml:centerHeader) }"/>
<table>
<tr>
<td id="facetsCell" valign="top" width="450px">
<div id="facetsProgressIndicator">Loading
{= ui:label(?treeRoot) }...</div>
<script>startFacets('http://siemens.com/1.0/vocab/biomed-symp#Symptom','','ssf-instance-page');</script>
</td>
<td id="resultsCell" style="padding-left: 12px"
valign="top" width="450px"/>
</tr>
</table>
</div>
4.4 version:
<div class="ui-layout-center" width="600px">
<swa:Header arg:label="{= spl:object(?viewTemplate,
ssfhtml:centerHeader) }"/>
<table>
<tr>
<td id="facetsCell" valign="top" width="450px">
<swa:FacetedSearchGadget
arg:resourceType="biomed-symp:Symptom" ui:args="*"/>
</td>
<td id="resultsCell" style="padding-left: 12px"
valign="top" width="450px">
<swa:SummarySearchResultsGadget
ui:args="*"/>
</td>
</tr>
</table>
</div>
Jack
On Friday, July 25, 2014 8:32:29 AM UTC-7, Jack Hodges wrote:
>
> Do you have a project upload mechanism that I can use. The workspace,
> compressed, is 223 MB. I have sent a project description to your email
> address.
>
> Jack
>
> On Thursday, July 24, 2014 7:47:52 PM UTC-7, Holger Knublauch wrote:
>>
>> Hi Jack,
>>
>> sorry but I believe we will need to get hands on your example file to
>> help you further. Off-list is fine.
>>
>> Holger
>>
>>
>> On 7/25/2014 5:20, Jack Hodges wrote:
>>
>> Hello Irene,
>>
>> I checked all of the classes and they are all rdf:type owl:Class (they
>> subclass owl:Thing). I checked all of the properties I am using as facets
>> and the items in all of their domains and ranges are rdf:type owl:Class.
>> But no faceted search (I closed and opened the model and refreshed the
>> caches and the swp graphs).
>>
>> Jack
>>
>> On Thursday, July 24, 2014 11:26:37 AM UTC-7, Jack Hodges wrote:
>>>
>>> Thanks!
>>>
>>> On Thursday, July 24, 2014 8:28:41 AM UTC-7, Irene Polikoff wrote:
>>>>
>>>> Jack,
>>>>
>>>>
>>>>
>>>> I don’t believe sub-classing is either an issue or a requirement here.
>>>> Faceted search works over instances of a class. Classes are instances of
>>>> either rdfs:Class or owl:Class. So, you need to be faceting over either
>>>> rdfs:Class or owl:Class. And properties to select from as facets would
>>>> need
>>>> to be associated with these e.g., have owl:Class in their domain.
>>>>
>>>>
>>>>
>>>> Irene
>>>>
>>>>
>>>>
>>>> *From:* topbrai...@googlegroups.com [mailto:topbrai...@googlegroups.com]
>>>> *On Behalf Of *Jack Hodges
>>>> *Sent:* Thursday, July 24, 2014 11:17 AM
>>>> *To:* topbrai...@googlegroups.com
>>>> *Subject:* Re: [topbraid-users] faceted search on classes rather than
>>>> instances?
>>>>
>>>>
>>>>
>>>> I am trying to build faceted search across standard
>>>> models/repositories. In this case the classes are terminals for the
>>>> repository and contain all the information an instance would carry. For
>>>> example, in the obolibrary DOID, disease obo:DOID_9352 is fully populated
>>>> with content, and the disease is unlikely to be subclassed or instantiated.
>>>>
>>>> My understanding is that these classes can participate in faceted
>>>> search under certain circumstances. First, they have to subclassed under
>>>> one of my classes. Also, for classes to be facetable they need to carry
>>>> properties and look like resources.
>>>>
>>>> I created namespaces such as the following for Symptoms:
>>>>
>>>> http://siemens.com/1.0/vocab/biomed-symp
>>>>
>>>> and a prefix for it: biomed-symp. I created a class called Symptom and
>>>> then subclassed several (for the purposes of a demo) of the classes in the
>>>> obolibrary (e.g., obo:SYMP_0000455) to biomed-symp:Symptom. I did the same
>>>> for diseases (etc.). I created facets to bridge the repositories, such as
>>>> biomed-symp:involvesDisease, that I hung off biomed-symp:Symptom in the
>>>> defaultFacets property.
>>>>
>>>> In the vocabulary, I added these properties (e.g,. obo:SYMP_0000455
>>>> biomed-symp:involvesDisease obo:DOID_9352).
>>>>
>>>> Unfortunately this approach isn't working, so I haven't gone far enough
>>>> in one way or another, and figure that you guys might know how to do it.
>>>> Any help would be appreciated as faceted search is very important to this
>>>> project. My faceted search in other parts of the project, created the same
>>>> way but on class instances, are working fine.
>>>>
>>>> Jack
>>>>
>>>>
>>>> On Sunday, July 13, 2014 8:22:44 AM UTC-7, Irene Polikoff wrote:
>>>>
>>>> What would you use as facets?
>>>>
>>>>
>>>> On Jul 13, 2014, at 11:11 AM, Jack Hodges <jhodg...@gmail.com> wrote:
>>>>
>>>> Can I build a faceted search on classes rather than on class
>>>> instances? If I have a repository that is basically a taxonomy and has all
>>>> of the content at the class level, then faceted search on the classes
>>>> would
>>>> provide the same benefit as faceted search on instances.
>>>>
>>>>
>>>>
>>>> Jack
>>>>
>>>> --
>>>> -- 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
>>>> topbrai...@googlegroups.com
>>>> To unsubscribe from this group, send email to
>>>> topbraid-user...@googlegroups.com
>>>> 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 topbraid-user...@googlegroups.com.
>>>> 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
>>>> topbrai...@googlegroups.com
>>>> To unsubscribe from this group, send email to
>>>> topbraid-user...@googlegroups.com
>>>> 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 topbraid-user...@googlegroups.com.
>>>> 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
>> topbrai...@googlegroups.com
>> To unsubscribe from this group, send email to
>> topbraid-user...@googlegroups.com
>> 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 topbraid-user...@googlegroups.com.
>> 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
topbraid-users@googlegroups.com
To unsubscribe from this group, send email to
topbraid-users+unsubscr...@googlegroups.com
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 topbraid-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
