[
https://issues.apache.org/jira/browse/JENA-189?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13820129#comment-13820129
]
Andy Seaborne commented on JENA-189:
------------------------------------
There is quite a big difference between, say, needing to change import
statements because of repacking and needing to use IRIs everywhere. This is
not to argue against it but just because some changes require rework, does not
mean it's all the same amount of work.
For this to be a good idea, we'd need to understand the implications. Jena IRI
library performs a detailed parsing of the string. Is that an acceptable cost?
What is a loop is doing an operation where part of the loop body is using the
same string each time - avoiding repeated parsing maybe necessary.
Jena can support multiple APIs - a possibility is to grow this style in
parallel with a fairly direct port of the existing API and see which gains
traction. It allows for a wide scope for change without forcing it it get
access to other improvements that aren't connected to the API.
> Jena 3 / technical
> ------------------
>
> Key: JENA-189
> URL: https://issues.apache.org/jira/browse/JENA-189
> Project: Apache Jena
> Issue Type: Brainstorming
> Reporter: Andy Seaborne
> Attachments: IteratorLockandTransactionsinJena3.pdf
>
>
> This is a JIRA to discuss and collect technical changes to Jena that would
> warrant a "Jena3" whether an incompatible change or just sufficient changes
> to mean bumping the major version number is best.
--
This message was sent by Atlassian JIRA
(v6.1#6144)
