That's a great idea.
+1
From: ajs6f
Sent: Tuesday, May 8, 2018 10:55 AM
To: dev@jena.apache.org
Subject: Re: parsing and matching triples
Forking a thread off to dev@:
Do we have a global policy about where null is accepted as a
added as named graph as well and
so included in the union.
What is your application usage that naturally wanted the default model
to be included?
Andy
On 14/04/18 21:00, Adam Jacobs wrote:
> Dataset.getUnionModel() excludes the default graph.
> Would it be appropriate to include the d
Dataset.getUnionModel() excludes the default graph.
Would it be appropriate to include the default graph in this method, or to add
an additional unioning method to the Dataset interface which includes the
default graph?
It seems like an oversight, but maybe there was a reason for excluding it?
[
https://issues.apache.org/jira/browse/JENA-1499?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16388781#comment-16388781
]
Adam Jacobs edited comment on JENA-1499 at 3/7/18 12:43 AM:
>From the API s
[
https://issues.apache.org/jira/browse/JENA-1499?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16388781#comment-16388781
]
Adam Jacobs commented on JENA-1499:
---
>From the API side, I've noticed empty graphs are consisten
[
https://issues.apache.org/jira/browse/JENA-1391?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16382936#comment-16382936
]
Adam Jacobs commented on JENA-1391:
---
This looks fine to me. Nice work.
> Add Convenience Meth
Adam Jacobs created JENA-1495:
-
Summary: Covariant return type for Model's PrefixMapping methods.
Key: JENA-1495
URL: https://issues.apache.org/jira/browse/JENA-1495
Project: Apache Jena
Issue
stance, this seems like something to raise with the
jsonld-java team to find out if that is intentional. Could you open a
discussion issue there?
IIRC empty prefix and the base are mixed up in JSON-LD.
Andy
On 04/01/18 03:34, Adam Jacobs wrote:
> The @vocab prefix is dropped by Jena when parsi
Is it a good idea to have a public mutable model?
From: Cotton Franck
Sent: Sunday, January 7, 2018 11:47 AM
To: dev@jena.apache.org
Subject: RE:PROV vocabulary class
Hi Adam. Here:
The @vocab prefix is dropped by Jena when parsing JsonLD.
An empty prefix is correctly translated into @vocab during serialization, but
is lost during deserialization.
Below code demonstrates the point.
public static void main(String... args) {
String base =
[
https://issues.apache.org/jira/browse/JENA-1452?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16299446#comment-16299446
]
Adam Jacobs commented on JENA-1452:
---
It looks like {{TestGraphUnionRead}} only covers the {{find
I just want to mention that it was not my intent to derail progress on
Jena-1391 (https://issues.apache.org/jira/browse/JENA-1391) by raising the
issue of immutability,
particularly if immutability would be implemented via a new API. I don't think
it should be considered a blocker to that
Note that the original request in Jena-1427 was for a nextOrElse() method
accepting an instance of Supplier.
The implementation of nextOptional(), released in version 3.6, solves my use
case just as well.
The only reason I had not requested nextOptional() directly is that
ExtendedIterator was
Adam Jacobs created JENA-1451:
-
Summary: DatasetFactory.createGeneral() never contains default
graph
Key: JENA-1451
URL: https://issues.apache.org/jira/browse/JENA-1451
Project: Apache Jena
I've noticed a couple of differences between DatasetFactory.create() and
DatasetFactory.createGeneral().
My understanding is that the former is intended to create deep copies of its
graphs whereas the latter maintains shallow links.
The DatasetFactory has quite a few creational methods, and
t;
Multiple calls to a single graph => multiple queries => multiple result sets
(or result graphs) => multiple scopes.
ajs6f
> On Dec 17, 2017, at 11:15 AM, Adam Jacobs <jacobs_...@hotmail.com> wrote:
>
> My understanding is there's nothing wrong with maintaining labels a
My understanding is there's nothing wrong with maintaining labels among
multiple calls to a single graph.
The danger would be the risk of maintaining labels among calls to multiple
graphs.
At least, that's what I get out of this SO answer:
[
https://issues.apache.org/jira/browse/JENA-1427?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16263362#comment-16263362
]
Adam Jacobs commented on JENA-1427:
---
Sounds great to me. Whether integrating with Java's {{Optional
[
https://issues.apache.org/jira/browse/JENA-1427?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16257388#comment-16257388
]
Adam Jacobs commented on JENA-1427:
---
Utility methods don't enable the same fluent style of functional
[
https://issues.apache.org/jira/browse/JENA-1427?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16257356#comment-16257356
]
Adam Jacobs commented on JENA-1427:
---
One more thought, rather than adding more functional methods
[
https://issues.apache.org/jira/browse/JENA-1427?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16257346#comment-16257346
]
Adam Jacobs commented on JENA-1427:
---
{{Optional}} does add an extra object and an extra call
but I am curious about why you
are reaching for the visitor pattern?
ajs6f
> On Nov 17, 2017, at 11:27 AM, Adam Jacobs <jacobs_...@hotmail.com> wrote:
>
> Perhaps only a single generic parameter then, if each method should return
> the same type.
> Or a sub-interface in
[
https://issues.apache.org/jira/browse/JENA-1427?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16257292#comment-16257292
]
Adam Jacobs commented on JENA-1427:
---
The use case would be to consume only one element (or none) from
[
https://issues.apache.org/jira/browse/JENA-1427?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Adam Jacobs updated JENA-1427:
--
Description:
Allow a functional approach for returning a default value or throwing a custom
exception
Adam Jacobs created JENA-1427:
-
Summary: Add nextOrElse() method in ExtendedIterator
Key: JENA-1427
URL: https://issues.apache.org/jira/browse/JENA-1427
Project: Apache Jena
Issue Type
ajs6f
> On Nov 17, 2017, at 10:55 AM, Adam Jacobs <jacobs_...@hotmail.com> wrote:
>
> I wonder if it would be useful to generify the `RDFVisitor` interface...
>
> public interface RDFVisitor<B,U,L> {
>
>B visitBlank( Resource r, AnonId id );
>U visitURI( Res
The subject of immutability was raised in JENA-1391
(https://issues.apache.org/jira/browse/JENA-1391).
Specifically, the `getUnionModel` method in Jena 3.4 returns an immutable model
view, and the implementation of the aforementioned story includes methods that
will return an immutable dataset
[
https://issues.apache.org/jira/browse/JENA-1391?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16241171#comment-16241171
]
Adam Jacobs commented on JENA-1391:
---
One additional method from the {{Model}} interface that would
[
https://issues.apache.org/jira/browse/JENA-1391?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16239546#comment-16239546
]
Adam Jacobs edited comment on JENA-1391 at 11/5/17 1:55 PM:
The integration
[
https://issues.apache.org/jira/browse/JENA-1391?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16239546#comment-16239546
]
Adam Jacobs commented on JENA-1391:
---
The integration with Java's {{Collector}} interface looks very nice
[
https://issues.apache.org/jira/browse/JENA-1391?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Adam Jacobs updated JENA-1391:
--
Description:
The Dataset interface could provide several convenience methods similar to the
Model
[
https://issues.apache.org/jira/browse/JENA-1391?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16155374#comment-16155374
]
Adam Jacobs commented on JENA-1391:
---
Consistency between the `Dataset` and `Model` interfaces seems
Adam Jacobs created JENA-1390:
-
Summary: Add toModel() method in StmtIterator
Key: JENA-1390
URL: https://issues.apache.org/jira/browse/JENA-1390
Project: Apache Jena
Issue Type: Improvement
Adam Jacobs created JENA-1389:
-
Summary: Return `this` rather than `void` from Dataset
Key: JENA-1389
URL: https://issues.apache.org/jira/browse/JENA-1389
Project: Apache Jena
Issue Type
34 matches
Mail list logo