[
https://issues.apache.org/jira/browse/MARMOTTA-500?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16710282#comment-16710282
]
ASF GitHub Bot commented on MARMOTTA-500:
-----------------------------------------
Github user cbeer closed the pull request at:
https://github.com/apache/marmotta/pull/2
> Support ldpath-linkeddata-backend resources with inlined resources
> ------------------------------------------------------------------
>
> Key: MARMOTTA-500
> URL: https://issues.apache.org/jira/browse/MARMOTTA-500
> Project: Marmotta
> Issue Type: New Feature
> Components: LDCache, LDPath
> Affects Versions: 3.2.0, 3.2.1
> Reporter: Chris Beer
> Priority: Major
>
> I've prepared a proof-of-concept pull request at
> https://github.com/apache/marmotta/pull/2. It's perhaps more invasive than
> ideal, but seems to get the job done.
> Remote RDF resources sometimes contain additional RDF resources besidest he
> request URI. When these inlined resources are requested (using "x within y"
> selector), we can mint a temporary identifier for the resource in the ldcache
> and allow it to be used by downstream selectors as if it were a
> full-fledged web resource.
> The other thing this addresses, and was the impetus for this development, is
> retrieving embedded resources that may result from following an rdfs:seeAlso
> triple. I have a case where the object of a rdfs:seeAlso link contains no
> triples about that resource, but is a RDF document about the original
> resource. As-is, I don't believe there's a way to select the triples from
> that document (short of dumping the result into a triplestore, I suppose).
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
