Faceted Search

--001a113f39f02581450521e98953
Content-Type: text/plain; charset=UTF-8

I don't know if this is something new, it just seems it was useful for the
kind of interface I was looking for. I was just wondering what would be the
best way to facilitate browsing and search in the application demo I'm
building that renders RDF / Semantic Web contents. I've figured out there
must be a tree hierarchy of categories, roles and instances of data to
which adhere the incoming data parsing so having a common denominator for
different input structures.

Having this structures, browsing through the tree of data, an item (leave
or node) could be 'picked up' as a facet. For example, if the scenario is
"Car Rental" as a category, "Car Model" and "Rental City" as roles and many
models of cars and many cities as instances, what if I could pick a car
model, a city or both and press "Aggregate" and this resulting in root
categories for each specific car rental ("Car Rental 1", "Car Rental 2",
etc) with its roles populated with the corresponding criteria values (the
city corresponding to "Car Rental 1" given its car, etc).

Maybe this sounds dumb. But the question is: how difficult would be to
build such a filter criteria using only RDF datasources. RDF statement
resources are not individualized by their occurrences. An RDF resource is
the same regardless which statements it occurs. And, although I've found a
way to individualize occurrences of, for example, Car Rental(s), I can't
find the way yet to correlate this instances with the instances of their
roles.

Also, I'm restricting my mappings (ontology processing output) to three
levels depth, which seems arbitrary. I could not restrict the graph to any
depth. But I'll keep trying a while with this arrangements. It seems
attractive the correlation of categories, roles and instances with some of
the concepts in the DCI programming model (
https://en.wikipedia.org/wiki/Data,_context_and_interaction) which could
allow for a model driven focused approach of building the client
application, again with the ontology 'common factors' concept in mind.

Source, examples and the demo web application are available in the project
web page:

http://cognescent.blogspot.com
http://sourceforge.net/projects/cognescent/

Regards,
Sebastian

--001a113f39f02581450521e98953
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div><div><div>I don&#39;t know if this is something new, =
it just seems it was useful for=20
the kind of interface I was looking for. I was just wondering what would
 be the best way to facilitate browsing and search in the application=20
demo I&#39;m building that renders RDF / Semantic Web contents. I&#39;ve fi=
gured out there=20
must be a tree hierarchy of categories, roles and instances of data to whic=
h adhere the incoming data parsing so having a common denominator for diffe=
rent input structures.<br>
<br>
Having this structures, browsing through the tree of data, an item (leave
 or node) could be &#39;picked up&#39; as a facet. For example, if the scen=
ario=20
is &quot;Car Rental&quot; as a category, &quot;Car Model&quot; and &quot;Re=
ntal City&quot; as roles=20
and many models of cars and many cities as instances, what if I could=20
pick a car model, a city or both and press &quot;Aggregate&quot; and this=
=20
resulting in root categories for each specific car rental (&quot;Car Rental=
 1&quot;,=20
&quot;Car Rental 2&quot;, etc) with its roles populated with the correspond=
ing=20
criteria values (the city corresponding to &quot;Car Rental 1&quot; given i=
ts car,
 etc).<br>
<br>
Maybe this sounds dumb. But the question is: how difficult would be to=20
build such a filter criteria using only RDF datasources. RDF statement=20
resources are not individualized by their occurrences. An RDF resource is t=
he same regardless which statements it occurs. And, although=20
I&#39;ve found a way to individualize occurrences of, for example, Car=20
Rental(s), I can&#39;t find the way yet to correlate this instances with th=
e
 instances of their roles.<br><br></div><div>Also, I&#39;m restricting my m=
appings (ontology processing output) to three levels depth, which seems arb=
itrary. I could not restrict the graph to any depth. But I&#39;ll keep tryi=
ng a while with this arrangements. It seems attractive the correlation of c=
ategories, roles and instances with some of the concepts in the DCI program=
ming model (<a href=3D"https://en.wikipedia.org/wiki/Data,_context_and_inte=
raction">https://en.wikipedia.org/wiki/Data,_context_and_interaction</a>) w=
hich could allow for a model driven focused approach of building the client=
 application, again with the ontology &#39;common factors&#39; concept in m=
ind.<br></div><div><br>Source, examples and the demo web application
 are available in the project web page:<br><br></div><a href=3D"http://cogn=
escent.blogspot.com">http://cognescent.blogspot.com</a><br><a href=3D"http:=
//sourceforge.net/projects/cognescent/">http://sourceforge.net/projects/cog=
nescent/</a><br><br></div>Regards,<br></div>Sebastian<br><br>
</div>

--001a113f39f02581450521e98953--