[
https://issues.apache.org/jira/browse/JENA-1225?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15427850#comment-15427850
]
Rob Vesse commented on JENA-1225:
---------------------------------
The specification does not say anything about prefix definitions because those
are features of RDF serialisation formats and not of the protocol itself.
Behind-the-scenes Jena chooses to Store those prefixes and use them for output.
Are you using TDB as the underlying database? TDB maintains a central database
wide registry of prefix definitions AFAIK so it is even possible that
definitions declared by one graph could be returned in the serialisation of
another
Is there any particular reason why this is an issue for you?
> Prefixmappings are not removed permanently from graph with DELETE
> -----------------------------------------------------------------
>
> Key: JENA-1225
> URL: https://issues.apache.org/jira/browse/JENA-1225
> Project: Apache Jena
> Issue Type: Bug
> Components: Fuseki
> Affects Versions: Fuseki 2.4.0
> Environment: Any / appears on Fuseki 2.4.0 or older
> Reporter: Miika Alonen
> Priority: Minor
>
> Prefixmappings are not removed permanently from graphs with DELETE. When
> adding triples to a graph that was deleted earlier old prefixmappings appear
> unexpectedly.
> EXAMPLE:
> PUT http://localhost:3030/example/data?graph=http://example.org/foo#
> @prefix foo: <http://example.org/foo#> .
> foo:foo foo:foo foo:foo
> DELETE http://localhost:3030/example/data?graph=http://example.org/foo#
> PUT http://localhost:3030/example/data?graph=http://example.org/foo#
> @prefix bar: <http://example.org/bar#> .
> bar:bar bar:bar bar:bar .
> GET http://localhost:3030/example/data?graph=http://example.org/foo#
> This returns both old and new prefixmappings:
> @prefix bar: <http://example.org/bar#> .
> @prefix foo: <http://example.org/foo#> .
> bar:bar bar:bar bar:bar .
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
