[
https://issues.apache.org/jira/browse/JENA-1265?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15739783#comment-15739783
]
A. Soroka commented on JENA-1265:
---------------------------------
Do we have a long-term policy about this? For example, to migrate all
{{Capabilities}} -based metadata into appearing in the type system (not sure
that's possible in every case, but as a general policy)? I've certainly never
used {{Capabilities}} or even seen it used outside of tests.
> GraphView : need to provide a safe set of capabilities, not the in-memory
> settings.
> -----------------------------------------------------------------------------------
>
> Key: JENA-1265
> URL: https://issues.apache.org/jira/browse/JENA-1265
> Project: Apache Jena
> Issue Type: Bug
> Components: ARQ
> Affects Versions: Jena 3.1.1
> Reporter: Andy Seaborne
> Assignee: Andy Seaborne
> Fix For: Jena 3.2.0
>
>
> GraphView provides a setting for Capabilities but that is derived from
> GraphBase, which is the in-memory settings. GraphView should provide settign
> - no iterator remove, no literal datatyping. Specific storage systems use of
> GraphView can override as needed.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
