Recent changes to feature-requests

N3 form: show nicely URI buttons

2014-02-27T19:03:09.509000Z

In DataGUI, the "add URI" buttons should show either an icon related to the Class, property, or an meaningful name, or else a link icon.
The link buttons to "existing" URI's should show either an icon related to the instance individual, or fallback related to the Class, property, or an meaningful name typically the rdfs:label, or else the abbreviated URI as it is today.

log and message pane

2010-03-22T09:58:56Z

remove System.out and System.err
add a tab or text area for messages

see if an IDE does not automatically part of the work

Error on parsing completely stops Drools rules generation

2010-03-15T17:31:58Z

In Project.translateN32Drools(), no exception handling and recovery is done.
So the method completely exits on error.
It is probably a brutal solution.
A better alternative is to try to parse the other N3Sources, and just highlight the fact that
a given set of N3Sources have failed.

It is probably the correct behaviour when dealing with N3Sources for a project.
But how to handle the N3 parsing problems when loading the .n3p in the ApplicationKB?

May be we should try to load as many N3Sources as possible. And then rethrow one Exception
containing all the N3Sources that have failed.

move classes: Drools, gui

2010-03-15T10:20:57Z

NOTE: of course this is not a (user-visible) feature, but it is convenient ot add it here...

Refactoring: move classes

Move n3_project/helpers/*Drools* and related classes to package
eulergui.drools_engine

Move most of n3_project package, starting with ProjectGUI to package eulergui.gui.*
- ProjectGUI to eulergui.gui
- *Management* to package eulergui.gui.actions
- *View* to package eulergui.gui.view

n3_project is too big , and should be splitted; but in doubt to the destination, keep the class here , and we can talk about it.

Olivier, do you have "move class" refactoring in IntelliJ ?
Can you move several classes together?

watch upgrades in Maven dependencies and maybe automatize

2010-03-12T14:58:56Z

pellet , Drools, Euler, ... upgrades : automatize ?

Maybe Maven already has a plugin to watch upgrades in Maven dependencies and maybe automatize.
Here are the places where we manually look for upgrades:

Pellet : http://on.cs.unibas.ch/maven/repository
Drools: http://repository.jboss.org/maven2/org/drools/drools-core/
Euler: http://eulersharp.sourceforge.net/maven2/euler/euler/?C=M;O=D
Jena: http://openjena.org/repo/com/hp/hpl/jena/jena/

change separator in URI's for Java classes

2010-03-12T14:53:35Z

The separator in URI's for Java classes is currently _ , which is bad, as _ can be in class and package names in Java.
We should switch to - .
In class Instanciator there is a constant N3_JAVA_PATH_SEPARATOR .

But several things are hard-coded and dependant on it : other code ( search for "javax_" and "java_" ), tests, examples, swing rules in Déductions project.

Problem in Gloze with XML Schema for XHTML

2010-03-12T14:30:48Z

Problem with the XHTML Schema and string content

Steve Battle may help ...
This rather complex Schema is important in applications.

Here a simple N3 file test/xhtml.n3 based on the XHTML Schema.

@prefix : <http://example.com#>.
@prefix html: <http://www.w3.org/1999/xhtml#>.
<> html:html _:html.
_:html html:body :body .
_:html html:head :head .
:head html:title "bla" .

Starting Gloze stand-alone with these arguments:

test/xhtml.n3
http://www.w3.org/1999/xhtml
http://www.w3.org/2002/08/xhtml/xhtml1-transitional.xsd

I got this rather long stack that is hard to understand.
What is clear is that a Literal "bla" is cast as a Resource.

Thread [main] (Suspended (exception ClassCastException))
element.toXML(Node, RDFNode, Context) line: 631
element.toXML(Element, Resource, int, Set<Statement>, Context) line: 559
sequence.toXML(Element, Resource, int, Set<Statement>, Context) line: 184
choice.toXML(Element, Resource, int, Set<Statement>, Context) line: 155
sequence.toXML(Element, Resource, int, Set<Statement>, Context) line: 188
complexType.toXML(Element, Resource, int, Set<Statement>, boolean, Context) line: 263
complexType.toXML(Element, Resource, int, Set<Statement>, Context) line: 246
element.toXML(Node, RDFNode, Context) line: 632
element.toXML(Element, Resource, int, Set<Statement>, Context) line: 559
sequence.toXML(Element, Resource, int, Set<Statement>, Context) line: 184
complexType.toXML(Element, Resource, int, Set<Statement>, boolean, Context) line: 263
complexType.toXML(Element, Resource, int, Set<Statement>, Context) line: 246
element.toXML(Node, RDFNode, Context) line: 632
Context.toXML(Document, Resource) line: 221
Gloze.drop(Resource) line: 747
Gloze.drop(Model, URI) line: 724
Gloze.rdf_to_xml(URL, File, URI, Model) line: 524
Gloze.rdf_to_xml(URL, String) line: 560
Gloze.runGloze(String[]) line: 821
Gloze.main(String[]) line: 774

use insertLogical() instead of insert()

2010-03-12T14:14:25Z

We should use insertLogical() everywhere instead of insert() in the N3 --> Drools translation .
This will pave the way for :
- retracting windows and forms by the rule engine
- temporarily asserting user data subject to validation rules, so that unvalidated stuff gets whiped out by the engine.

Need to verify that the executation times are inded comparable , if not inferior as Mark says .

dialog with Mark Protor

good evening ! I have a question about insertLogical() ;
I am tempted to use it all the time, but I wonder how much will I have to pay in terms of performances
<conan> not too much
<conan> if you are using trunk
<conan> it's even more efficient there

in Gloze remove Maps with URL as key

2010-03-12T13:58:47Z

I passed FindBugs on Gloze, and it found something interesting:

This method or field is or uses a Map or Set of URLs. Since both the
equals and hashCode method of URL perform domain name resolution, this
can result in a big performance hit. See
http://michaelscharf.blogspot.com/2006/11/javaneturlequals-and-hashcode-make.html
for more information. Consider using java.net.URI instead.

I think it may cause bad performance in Gloze.

Need to check and coordinate with Steve Battle.

Error in parsing should appear in the GUI

2010-03-11T16:00:57Z

When loading a N3Source, if the parsing fails, an error sign should appear left to the file name (with a tooltip corresponding to the error message).
Editing the source would automatically set the caret at the error line.