x27;t
call size() or otherwise look at the InfModel, nothing happens.
So I am wondering what the "right" way is to trigger rule execution in
this case. I am happy to punch a few rules in and then trigger
execution, but I'd like some way to do it that doesn't do any work I
don&
or because the engine wouldn't be able to
work correctly if the Builtin was fixed?
--
Paul Houle
paul.ho...@ontology2.com
nd see if they match) although the perfect system would
probably search A over a small set of prefixes and then filter.
Even add() might have problems because of numeric coercion (there might
be more than one type which fits.)
Would the ability to return binding sets affect both the forward and
backwards
Well if there is not interest in doing it I'd suggest removing the
suggestions that it could be done from the places where it is mentioned
in the documentation.
--
Paul Houle
paul.ho...@ontology2.com
On Thu, Jul 14, 2016, at 11:17 AM, Dave Reynolds wrote:
> On 14/07/16 15:44, Pa
e order of operations has to change, or it is not
so easy to close something when you are done with it because you might
not really be done with it, etc.
--
Paul Houle
paul.ho...@ontology2.com
On Wed, Jul 27, 2016, at 05:39 AM, rwm wrote:
> Github user rwm commented on the issue:
>
ake a lot of sense and
autocomplete doesn't work well in your IDE. It is a little more capable
than the "guava statics" but the amount of suffering it makes you go
through is not worth it.
--
Paul Houle
paul.ho...@ontology2.com
On Wed, Jul 27, 2016, at 01:21 PM, A. Soroka
But realistically any kind of framework or application *does* end up
creating structures that compete with what is in the standard library
when it is as sprawling as it is in Java. (i.e. ClosableIterator vs.
AutoCloseable)
--
Paul Houle
paul.ho...@ontology2.com
On Wed, Jul 27, 2016, at 02
mvn install
--
Paul Houle
paul.ho...@ontology2.com
On Wed, Sep 7, 2016, at 12:07 PM, otheus uibk wrote:
> Please please please -- for this project and any other any of you may
> ever
> do -- include the build instructions in the top-level of the source code.
> The README fi
system that processes web forms, sends emails,
etc. that runs in AWS with DynamoDB. One cool thing there is that I
write business rules in the Jena Rules language to deal with how
messages get routed, which messages are spam, etc.
--
Paul Houle
paul.ho...@ontology2.com
On Thu, Oct 6
facts on the route to a 99% success rate at a geospatial recognition
task. A disciplined approach to "agreeing to disagree" goes a long way
to solve the problem that specific applications require us to split
hairs in different ways.
--
Paul Houle
paul.ho...@ontology2.com
On T
.
--
Paul Houle
paul.ho...@ontology2.com
On Mon, Oct 17, 2016, at 12:31 PM, A. Soroka wrote:
> Yep,
>
> http://iswc2011.semanticweb.org/fileadmin/iswc/Papers/Workshops/SSWS/Ladwig-et-all-SSWS2011.pdf
>
> indicates that they are indexing by subject. As someone who has
> implem
s.
I carefully read the answers to the bad questions because I am intensely
curious about strange details in Jena that trip people up.
--
Paul Houle
paul.ho...@ontology2.com
On Sun, Oct 23, 2016, at 06:07 AM, Colin Maudry wrote:
> Dear Jena developers,
>
> Upon Andy Seaborne’s sugge
These arguments have a way of blending into racism.
One reason why people have challenges communicating on mailing lists is
that English is not their first language.
--
Paul Houle
paul.ho...@ontology2.com
On Mon, Oct 24, 2016, at 10:52 AM, A. Soroka wrote:
> > I take the first bul
At some point there just has to be a 3.1.1. Jena's release cycle is
already too slow.
--
Paul Houle
paul.ho...@ontology2.com
On Mon, Nov 7, 2016, at 08:56 AM, Andy Seaborne wrote:
>
> On 07/11/16 00:05, Stian Soiland-Reyes wrote:
> > I'm afraid my vote is:
&
Read it back how? I can sweat that I have round-tripped java: prefixes
before.
Note that java: is NOT on the list of IANA registered schemes:
http://www.iana.org/assignments/uri-schemes/uri-schemes.xhtml
--
Paul Houle
paul.ho...@ontology2.com
On Wed, Dec 7, 2016, at 10:42 AM, Claude
and then use the answer or put it back in some database.
I know Drools has better support for deletions, so does the RDF
database from Ontotext.
What would be involved in supporting this in Jena?
--
Paul Houle
paul.ho...@ontology2.com
On Mon, Jan 9, 2017, at 02:57 PM, Dave Reynolds wr
On Mon, Jan 9, 2017, at 05:31 PM, Dave Reynolds wrote:
>
> Great that this works for you but the design centre for Jena Rules was
> deductive closure not event-condition-action (ECA) or reactive rules.
One of the things I think about is why production rules haven't
had a bigger impa
Node functions.
> >>>>>>
> >>>>>> As for the Filter implementation. will that be transparant to
> >>> filter
> >>>>>> implementations? I assume so.
> >>>>>>
> >>>>>> On Fri, May
rtaken without being disruptive, and even without too much code
>> churn except when introducing Stream into the core. If it sounds like
>> a good idea, I would be happy to begin it.
>>
>
> Straight to pull request is probably not so easy to see what effect it
> will have
quot; it is clear that RDF is the right answer for many
such conundrums.
--
Paul Houle
*Applying Schemas for Natural Language Processing, Distributed Systems,
Classification and Text Mining and Data Lakes*
(607) 539 6254paul.houle on Skype ontolo...@gmail.com
https://legalentityidentifier.info/lei/lookup
<http://legalentityidentifier.info/lei/lookup>
gt; - Are you writing/blogging about it?
> In this same project, one of the third party libraries used Drools for
> rules to extract content from PDF. While I found it really powerful, it was
> hard to debug and adjust the parameters, as it had some custom code to
> manipulate excels a
ly
> > >>>> vetted
> > >>>> it. It's simple but enough to get started, and that's all I need to
> > bring
> > >>>> the real design questions into focus.
> > >>>>
> > >>>> 5) Snapshot isolation. Transacti
highly efficient reification-supporting RDF store, then
> build one. No need to blindly store as multiple triples (its called
> compression!). You don't see such stores because reification is a minor
> feature of RDF. Event-based modelling and named graphs are often better.
>
&
enterprise but maybe we can make it as reliable as Java or Python if we use
data sets to implement modal, contingent and other relationships.
--
Paul Houle
*Applying Schemas for Natural Language Processing, Distributed Systems,
Classification and Text Mining and Data Lakes*
(607) 539 6254pau
cks and
> determining if there are any conflicts between the patterns.
>
> Because this process can duplicate the current locking strategy it can be
> used as a drop in replacement in the current code. So current code would
> continue to operate as it does currently but future dev
em uses an abstract engine to determine if the user
>>> has
>>> access to the triples. For the locking mechanism the system needs to
>>> track
>>> graph locks and triple patterns locked. If a new request for a triple
>>> pattern matches any existing (a
I'd love to see RDF* and SPARQL* support in Jena but that might be too much
to ask.
On Sat, Jan 2, 2016 at 3:09 PM, Andy Seaborne wrote:
> On 02/01/16 19:36, Paul Houle wrote:
>
>> :s [] [] is a lot like a relational entity, but I think the really
>> interesting thing
I've had many requests to port some of the advances in my
infovore framework to Jena and now I'm getting around to that.
My program Infovore at github
https://github.com/paulhoule/infovore
has a module called "parallel super eyeball" which, like the
eyeball program, checks a RDF
I've had many requests to port some of the advances in my
infovore framework to Jena and now I'm getting around to that.
My program Infovore at github
https://github.com/paulhoule/infovore
has a module called "parallel super eyeball" which, like the
eyeball program, checks a RDF
arly a filter over an basic graph pattern - it's the
> main building block).
>
> If you want to go further (e.g. efficient group operations), then it can be
> done incrementally on top of that.
>
> There is some experimental code elsewhere [1] with slightly better
> a
t;> Rob
>>>
>>> In terms of the destination being the Jena project, this looks like it
>>> is fully aligned to the project charter:
>>>
>>> """
>>> the creation and maintenance of
>>> open-source software related to accessing, storing, querying,
>>> publishing and reasoning with semantic web data while
>>> adhering to relevant W3C and community standards
>>> for distribution at no charge to the public.
>>> """
>>>
>>> and I (personally) am quite relaxed about any variety if there is some
>>> connection to Jena even if it's quite small (e.g. there is at least one
>>> import statement like "org.apache.jena."!). We can't, in all
>>> honesty, adopt random other unrelated software without at least checking
>>> with other linked data projects in ASF. But at the same time, linked
>>> data @ASF isn't the Hadoop-infrastructure ecosystem where each piece can
>>> sustain it's own TLP.
>>>
>>> Andy
>>>
>>
>>
>>
>>
>
--
Paul Houle
Expert on Freebase, DBpedia, Hadoop and RDF
(607) 539 6254paul.houle on Skype ontolo...@gmail.com
ements (i.e.
>> invokedynamic) are unlikely to be used, although compiling SPARQL
>> expressions to the JVM would be a fun project.
>>
>> The library changes are (iirc) mostly around the new file api
>> (finally!). There isn't much messing with files in jena, b
s it is in PB+N).
>
> Protocol Buffers does not have a network layer, it's just the byte encoding,
> but Netty comes with built in protocol buffer handling (PB+N). That works
> fine as well and I have done back and found the equivalent functionality I
> have used in RDF Thrift.
>
> For binary RDF and it's general use, thrift's wider language cover is a plus
> point.
>
> Andy
--
Paul Houle
Expert on Freebase, DBpedia, Hadoop and RDF
(607) 539 6254paul.houle on Skype ontolo...@gmail.com
t;>
>> It looks like you'd only save a few bytes because you still have to store
>> the bulk of the term encoding you just lose some of the surface syntax
>> that something like a NTriples encoding would give you
>
>
> For TDB the big win is speed, not space. At the moment, the on-disk node
> format is a string that needs parsing and producing by string bashing.
>
> Both are relative expensive and the thing that limits load performance for
> medium sized
> datasets is the node table. The node cache largely hides the cost during
> SPARQL execution.
>
> In Lizard, storing Thrift means that remote retrieval is simply
> disk-bytes to network-bytes - no decode-encode in the node table storage
> server.
>
> Andy
>
>
>>
>> Rob
>>
>>>
>>> 5/ Files. Add to RIOT as a new syntax (a fairly direct access to
>>> StreamRDF+Thrift) which then helps TDB loading.
>>>
>>> 6/ Caching results set in queries in Fuseki.
>>>
>>> In an ideal world, the Thrift format could be shared across toolkits.
>>> There is nothing Jena specific about the wire encoding.
>
> ...
>>>
>>>
>>> Andy
>>
>>
>>
>>
>>
>
--
Paul Houle
Expert on Freebase, DBpedia, Hadoop and RDF
(607) 539 6254paul.houle on Skype ontolo...@gmail.com
a managed dependency in jena-parent. The license is
> > Apache 2.0.
> >
> > Andy
>
--
Paul Houle
Expert on Freebase, DBpedia, Hadoop and RDF
(607) 539 6254paul.houle on Skype ontolo...@gmail.com
http://legalentityidentifier.info/lei/lookup
Paul Houle created JENA-1201:
Summary: Improve Function Library For Jena Rules Engine
Key: JENA-1201
URL: https://issues.apache.org/jira/browse/JENA-1201
Project: Apache Jena
Issue Type
Paul Houle created JENA-1204:
Summary: Independently Configurable BulitinRegistry for Jena Rules
Engine
Key: JENA-1204
URL: https://issues.apache.org/jira/browse/JENA-1204
Project: Apache Jena
[
https://issues.apache.org/jira/browse/JENA-1204?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15362626#comment-15362626
]
Paul Houle commented on JENA-1204:
--
Here is some analysis. The only place where
[
https://issues.apache.org/jira/browse/JENA-1204?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15362626#comment-15362626
]
Paul Houle edited comment on JENA-1204 at 7/5/16 3:23 PM:
--
Paul Houle created JENA-1215:
Summary: Make ResultSets closeable
Key: JENA-1215
URL: https://issues.apache.org/jira/browse/JENA-1215
Project: Apache Jena
Issue Type: Improvement
Paul Houle created JENA-1227:
Summary: upgrade apache httpcomponents to 4.5.2
Key: JENA-1227
URL: https://issues.apache.org/jira/browse/JENA-1227
Project: Apache Jena
Issue Type: Improvement
[
https://issues.apache.org/jira/browse/JENA-1233?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15474177#comment-15474177
]
Paul Houle commented on JENA-1233:
--
In theory the identity of blank nodes bet
Paul Houle created JENA-1234:
Summary: Update README file to include build & usage information
Key: JENA-1234
URL: https://issues.apache.org/jira/browse/JENA-1234
Project: Apache Jena
Issue
43 matches
Mail list logo
