[
https://issues.apache.org/jira/browse/JENA-927?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14528317#comment-14528317
]
Rob Vesse commented on JENA-927:
If this is intended as transitional support should this not
Github user amiara514 commented on the pull request:
https://github.com/apache/jena/pull/53#issuecomment-99072949
Ah, I see. But this still doesn't help for cases where there are small
differences between literals within the same language, for example
singular/plural forms that get
Github user osma commented on the pull request:
https://github.com/apache/jena/pull/53#issuecomment-99066248
There was a discussion thread around this topic on the Jena dev mailing
list in late February, starting with this message:
[
https://issues.apache.org/jira/browse/JENA-933?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rob Vesse closed JENA-933.
--
Resolution: Fixed
DOAP needs to provide asfext:id value for implements/Standard
Github user osma commented on the pull request:
https://github.com/apache/jena/pull/53#issuecomment-99062926
Multilingual index manages dynamically one index per language. Hence for
the case where we have two same literals with different languages, they will be
not stored into the
On 05/05/15 16:54, Chris Dollin wrote:
Aside, hope it's useful:
Note that current jena-text doesn't /do/ conjunctive query but has enough
hooks to /enable/ conjunctive query, as is done in our ppd-index code
at https://github.com/epimorphics/ppd-text-index in TextDocProducerBatch.
When it
[
https://issues.apache.org/jira/browse/JENA-933?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14528529#comment-14528529
]
Sebb commented on JENA-933:
---
Thanks for the very prompt attention to this.
DOAP needs to provide
Github user ajs6f commented on the pull request:
https://github.com/apache/jena/pull/56#issuecomment-99121831
Okay, I'll plug `NodeTransform` back in at oaj.sparql.graph, since that is
where it was: minimal disruption. I've got the JavaDocs square and re-separated
the two
Github user afs commented on the pull request:
https://github.com/apache/jena/pull/56#issuecomment-99120861
The vast majority of the PR looks good including converting code in
passing. MultiMap?mulitSet are unlikely to have leaked (and can be restored if
need be); I've already
Github user ajs6f commented on the pull request:
https://github.com/apache/jena/pull/56#issuecomment-99085428
I'm definitely up for breaking this down. :)
The major moves here are:
- I replaced any interface inside oaj.atlas for which I could find a
Github user ajs6f commented on the pull request:
https://github.com/apache/jena/pull/56#issuecomment-99100248
Actually, for `NodeTransform`, perhaps it could be even more tightly scoped
to just `org.apache.jena.sparql.algebra.optimize`?
---
If your project is set up for it, you can
On 05/05/2015 02:04 PM, amiara514 wrote:
Github user amiara514 commented on the pull request:
https://github.com/apache/jena/pull/53#issuecomment-99072949
Ah, I see. But this still doesn't help for cases where there are small
differences between literals within the same language,
[
https://issues.apache.org/jira/browse/JENA-931?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14528468#comment-14528468
]
ASF GitHub Bot commented on JENA-931:
-
Github user ajs6f commented on the pull request:
Github user osma commented on the pull request:
https://github.com/apache/jena/pull/53#issuecomment-99096043
[copying from the email I sent to the dev list, apparently the bot didn't
notice my message]
Thanks a lot Chris, this was indeed very useful! So you're already doing
I think StreamXXX is the future but there is so much goodness in the
functional approach that a fluent API build to work well with that paradigm
ought to work well out of other paradigms.
The other day I was coding up something that parses record-organized .txt
files and make triples and I'd
[
https://issues.apache.org/jira/browse/JENA-934?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andy Seaborne updated JENA-934:
---
Description:
See test3 in
[
https://issues.apache.org/jira/browse/JENA-934?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andy Seaborne updated JENA-934:
---
Environment: (was: See test3 in
Github user ajs6f commented on the pull request:
https://github.com/apache/jena/pull/56#issuecomment-99141455
`NodeTransform` is back-- I think that's all the emendation we wanted, yes?
Did you have thoughts about dividing out this large PR?
---
If your project is set up
[
https://issues.apache.org/jira/browse/JENA-934?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14528850#comment-14528850
]
Andy Seaborne commented on JENA-934:
jsonld-java accpts and correctly handles as a
[
https://issues.apache.org/jira/browse/JENA-934?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andy Seaborne closed JENA-934.
--
Resolution: Fixed
Fix Version/s: Jena 3.0.0
JSONLD writer can output illegal JSON-LD when prefix
[
https://issues.apache.org/jira/browse/JENA-934?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andy Seaborne reassigned JENA-934:
--
Assignee: Andy Seaborne
JSONLD writer can output illegal JSON-LD when prefix used
[
https://issues.apache.org/jira/browse/JENA-933?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14528342#comment-14528342
]
Rob Vesse commented on JENA-933:
Updated DOAP has now been published
DOAP needs to provide
On 04/05/15 11:40, Bruno P. Kinoshita wrote:
Hi all,
I had spotted three tests that looked a bit strange while working on the
JENA-380 and made a note to look at them later after the jena3 merge.
I've committed two of them
TestOneToManyMap#testConstruct1 (sorry, used the wrong commit
[
https://issues.apache.org/jira/browse/JENA-934?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14528866#comment-14528866
]
ASF subversion and git services commented on JENA-934:
--
Commit
[
https://issues.apache.org/jira/browse/JENA-934?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14528871#comment-14528871
]
ASF subversion and git services commented on JENA-934:
--
Commit
[
https://issues.apache.org/jira/browse/JENA-933?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14528195#comment-14528195
]
ASF subversion and git services commented on JENA-933:
--
Commit 1677763
[
https://issues.apache.org/jira/browse/JENA-933?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sebb reopened JENA-933:
---
Thanks for fixing the file in SVN.
However the projects website is built from the file
[
https://issues.apache.org/jira/browse/JENA-933?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rob Vesse closed JENA-933.
--
DOAP needs to provide asfext:id value for implements/Standard
On 28/04/15 13:09, Ying Jiang wrote:
Hi all,
FYI, Google announced the accepted projects of GSoC 2015 yesterday. A
Jena project of Extend CONSTRUCT to build quads (JENA-491) [1] is
among them.
Cheers,
Ying Jiang
[1]
[
https://issues.apache.org/jira/browse/JENA-189?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andy Seaborne resolved JENA-189.
Resolution: Fixed
Fix Version/s: Jena 3.0.0
Jena 3 has now started so we move to specific JIRA
Hi there,
I've noticed a few more places where some Java 8 changes could be
brought into play in the interest of simplification, and in
particular, the use of Java 8 Streams seems like a nice way to go. It
would let Jena cut out a fair bit of API and implementation code in
favor of letting Java
Andy Seaborne created JENA-934:
--
Summary: JSONLD writer can output illegal JSON-LD when prefix
used
Key: JENA-934
URL: https://issues.apache.org/jira/browse/JENA-934
Project: Apache Jena
32 matches
Mail list logo