[ 
https://issues.apache.org/jira/browse/MARMOTTA-522?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14206384#comment-14206384
 ] 

Sebastian Schaffert commented on MARMOTTA-522:
----------------------------------------------

The issue in this case is that we explicitly set the context in the 
RDFImporterImpl. The problem is that we cannot verify in advance if the data 
will contain context information, otherwise we could just not pass a default 
context when no context is given. No solution for this now, maybe we could add 
a flag for this.

> Import doesn't honor TRIG context, puts meta data into default context unless 
> manually selected
> -----------------------------------------------------------------------------------------------
>
>                 Key: MARMOTTA-522
>                 URL: https://issues.apache.org/jira/browse/MARMOTTA-522
>             Project: Marmotta
>          Issue Type: Improvement
>          Components: Admin Interface
>    Affects Versions: 3.3.0
>            Reporter: Joshua Dunham
>            Assignee: Sebastian Schaffert
>            Priority: Minor
>              Labels: ADMIN-INTERFACE, CONTEXT, IMPORT, TRIG
>             Fix For: 3.4.0
>
>
> When importing TRIG data via the admin interface the import will not honor 
> the namespace / context in the TRIG file and instead will put the data into 
> the default context. 
> - Sample TRIG - 
> =============
> @prefix context: <http://server.com:8080/marmotta/context/> .
> @prefix xsd: <http://www.w3.org/2001/XMLSchema#> .
> @prefix foaf: <http://xmlns.com/foaf/0.1/> .
> context:people {
>       vrtx:JenniferLopez a foaf:Person ;
>                foaf:givenname "Jennifer" ;
>               foaf:family_name "Lopez" ;
>               foaf:phone "+1-617-555-1212" ;
>                       foaf:mbox <mailto:[email protected]> .
> }
> ===========
> - Desire is to have the importer parse the TRIG and insert data into the 
> correct namespace / context. In this case it is defined as 'people'.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to