On Dec 22, 2009, at 10:16 AM, Arthur Keen wrote:
> Thanks for the tip. I would prefer making one rule for all magic properties.
> Would it be a good idea to create a specialization of spin:MagicProperties,
> e.g., my:InferredMagicProperty for properties that I would like to have
> behave in this way, and check for instances of it in the where clause? e.g.:
Yes, this would be a good idea. Or just add some other marker property to your
magic properties to identify them.
>
> CONSTRUCT {
> ?a ?inferredMagicProperty ?b .
> }
> WHERE {
> ?inferredMagicProperty a my:InferredMagicProperty.
> ?a ? inferredMagicProperty ?b .
> }
This unfortunately does not work, because ARQ will not recognize magic
properties if they are bound dynamically from variable values. Most likely,
some other meta-magic property will be needed, implemented in Java, e.g.
?a my:metaProperty ( ?inferredMagicProperty ?b) .
Another option is to implement them on a Graph level (again in Jena) so that
those values are computed on demand. But that's more tricky...
Regards,
Holger
--
You received this message because you are subscribed to the Google Groups
"TopBraid Composer Users" group.
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-composer-users?hl=en.
