incubator-clerezza-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Manuel Innerhofer (JIRA)" <j...@apache.org>
Subject [jira] Issue Comment Edited: (CLEREZZA-218) Dynamic Resource Enrichment
Date Thu, 20 May 2010 22:10:17 GMT

    [ https://issues.apache.org/jira/browse/CLEREZZA-218?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12869616#action_12869616
] 

Manuel Innerhofer edited comment on CLEREZZA-218 at 5/20/10 6:08 PM:
---------------------------------------------------------------------

> - resources with a common eg:parent should be eg:sibling
> - for every foaf:Person there shall be a foaf:PersonalProfileDocument
Generalized speaking this means that the enrichment would happen if a structural condition
of a resource/resources was met? When this is possible, then it is also possible to say:
   if a resource X has more than 1000 properties, then add the triple {X RDF:type eg:SuperNova}?
When does the enrichment happen? Every time I access the resource or will it be computed for
all resources of a graph (which would be computationally quite expensive I assume)?

> - every non literal resource shall be subject of rdf:type rdfs:Resource statemet
I remember only one place where we test if a resource has the type rdfs:Resource and that
is the TypeHandlerSpace, but otherwise I think adding this type would bring no benefits, wouldn't
it?

> - every eg:City shall have a eg:currentWeather property pointing to a bnode with temperature
and humidity
This seems to be the regular use case, where the enrichment depends on a RDF:type



      was (Author: mir):
    > - resources with a common eg:parent should be eg:sibling
> - for every foaf:Person there shall be a foaf:PersonalProfileDocument
Generalized speaking this means that the enrichment would happen if a structural condition
of a resource/resources was met? When this is possible, then it is also possible to say:
   if a resource X has more than 1000 properties, then add the triple {X RDF:type eg:SuperNova}
When does the enrichment happen? Every time I access the resource or will it be computed for
all resources of a graph (which would be computationally quite expensive I assume)?

> - every non literal resource shall be subject of rdf:type rdfs:Resource statemet
I remember only one place where we test if a resource has the type rdfs:Resource and that
is the TypeHandlerSpace, but otherwise I think adding this type would bring no benefits, wouldn't
it?

> - every eg:City shall have a eg:currentWeather property pointing to a bnode with temperature
and humidity
This seems to be the regular use case, where the enrichment depends on a RDF:type


  
> Dynamic Resource Enrichment 
> ----------------------------
>
>                 Key: CLEREZZA-218
>                 URL: https://issues.apache.org/jira/browse/CLEREZZA-218
>             Project: Clerezza
>          Issue Type: Improvement
>            Reporter: Reto Bachmann-Gmür
>            Assignee: Reto Bachmann-Gmür
>
> Writing TcProviderS to deliver a virtual graph that is the added as temporary addition
to the content graph is quite tedious. As result of this issue one shall be able to provide
a simple service to provide triples about resources of a specific type, a component implemented
in this issue will aggregate those resource descriptions to a virtual graph.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message