[RDF] Views

[Jonas Liljegren]

I find that I shouldn't go futher without resolving the issue of
getting views to work:

        http://uxn.nu/wraf/RDF-Service/doc/html/views.html

Ok. I will go futher. But the solving of this will require some
rewriting of the code.


My current solution is to have statings i two levels.  In the primary
layer (primary cache) all statements are stored pointing at their
model.  The secondary cahce will be selection containers of the
resources meeting the context criterions.  The default criterion will
be to retrieve true statings.


I now came to think about the dynamic properties.  The dynamic
statings will differ depending on which other properties are
considered true.  That means that I can't just initialize all dynamic
properties into the primary cache.

I have previously decided on how to relate the information used for a
infereced (dynamic) property to that property.  The created statings
will be marked with the information needed to decide if it should be
included in a view.

Every initialization of a dynamic property will have to be done
within a context.  The context key (used for reusing previous
selections) will be stored along with the properties for remember
for which contexts the dynamic property has been initialized.


The problem I seen now is that dynamic properties are used for dynamic
types, deciding which interface functions are availible.

The current jumptables will have to be replaced by ones that
incorporate the context keys.


The plan is to find a direct way to find context keys based on the
current context.  A selections context key will consist of the
criterions actually used, not all criterions.

But how do we match the current context with the keys?  Can we compile
the conditions in order to speed up future matches?  It may involve
iterating through the key parts looking for corresponding values in
the context.


-- 
/ Jonas Liljegren

The Wraf project http://www.uxn.nu/wraf/
Sponsored by http://www.rit.se/