[
https://issues.apache.org/jira/browse/JENA-1838?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17037489#comment-17037489
]
ASF subversion and git services commented on JENA-1838:
-------------------------------------------------------
Commit 5ae3482d4c0f46e590e51d66c83e36b0b77f1748 in jena's branch
refs/heads/master from Andy Seaborne
[ https://gitbox.apache.org/repos/asf?p=jena.git;h=5ae3482 ]
Merge pull request #688 from afs/prefixes
JENA-1838: Updates to PrefixMap
> Updates to PrefixMap
> --------------------
>
> Key: JENA-1838
> URL: https://issues.apache.org/jira/browse/JENA-1838
> Project: Apache Jena
> Issue Type: Improvement
> Components: RIOT
> Affects Versions: Jena 3.14.0
> Reporter: Andy Seaborne
> Assignee: Andy Seaborne
> Priority: Major
> Fix For: Jena 3.15.0
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> This ticket is for maintenance work on PrefixMap, and how storage of prefix
> maps works in DBOE-based RDF storage.
> It replaces use of IRI in the PrefixMap and ParserProfile interfaces.
> Every retrieval use immediately does .toString() to get URI so base the
> interface using on Strings, not IRIs, makes more sense. It also localizes the
> use of class IRI.
> This prepares for the possible future of switching from jena-iri to a custom
> IRI parser/validator/resolver. jena-iri (IRI) is much more general but is a
> maintenance burden - it's too complicated.
> ParserProfile.makeIRI - becomes deprecated.
> oaj.riot.system.PrefixMap is the general interface.
> oaj.dboe.storage.prefixes.PrefixMapI can now inherit from PrefixMap. Storage
> and usage is better separated.
> It remains to add a point of indirection between PrefixMap and DBOE; it adds
> {{extends Iterable<PrefixEntry>}} (replacing PrefixMap with PrefixMapI would
> be a version disruption).
> Clear-up and renaming.
> The output optimizations for Turtle family writers is still in place.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
