You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jena.apache.org by "Andy Seaborne (JIRA)" <ji...@apache.org> on 2015/12/27 18:07:49 UTC
[jira] [Updated] (JENA-1107) Improve jena-base lib.Tuple
[ https://issues.apache.org/jira/browse/JENA-1107?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Andy Seaborne updated JENA-1107:
--------------------------------
Summary: Improve jena-base lib.Tuple (was: Rework jena-base lib.Tuple)
> Improve jena-base lib.Tuple
> ---------------------------
>
> Key: JENA-1107
> URL: https://issues.apache.org/jira/browse/JENA-1107
> Project: Apache Jena
> Issue Type: Improvement
> Reporter: Andy Seaborne
> Assignee: Andy Seaborne
> Priority: Minor
>
> Tuples, which are immutable, value-equality fixed length sequences of instances of the same type, accessed by index.
> They are like {{T[]}} but immutable, with .equals based on contents, could be improved to work independently of their original use in TDB.
> Proposal:
> # Make Tuple an interface (simpler than current), with special implementations for low number of elements.
> # {{ColumnMap}} ==> {{TupleMap}} and sort out the naming as much as possible to use as a way to manage index mapping, not just rewriting Tuples.
> An intermediate step is to move {{ColumnMap}} into TDB.
> This is not a proposal to add it to {{Triple}} or {{Quad}}.
> {{Triple}} is not the same as a 3-length {{Tuple<Node>}}. Triple elements are accessed by name (`getSubject` etc) not index. SPO is just one possible order in which to think about triples but it has no special status.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)