svn commit: r1205764 - in /incubator/stanbol/branches/lto-reasoners/reasoners: README.md README.txt

[en...@apache.org]

Author: enridaga
Date: Thu Nov 24 09:28:15 2011
New Revision: 1205764

URL: http://svn.apache.org/viewvc?rev=1205764&view=rev
Log:
Minor changes on the readme (and renamed to .md) (STANBOL-343)

Added:
    incubator/stanbol/branches/lto-reasoners/reasoners/README.md
      - copied, changed from r1205460, incubator/stanbol/branches/lto-reasoners/reasoners/README.txt
Removed:
    incubator/stanbol/branches/lto-reasoners/reasoners/README.txt

Copied: incubator/stanbol/branches/lto-reasoners/reasoners/README.md (from r1205460, incubator/stanbol/branches/lto-reasoners/reasoners/README.txt)
URL: http://svn.apache.org/viewvc/incubator/stanbol/branches/lto-reasoners/reasoners/README.md?p2=incubator/stanbol/branches/lto-reasoners/reasoners/README.md&p1=incubator/stanbol/branches/lto-reasoners/reasoners/README.txt&r1=1205460&r2=1205764&rev=1205764&view=diff
==============================================================================
--- incubator/stanbol/branches/lto-reasoners/reasoners/README.txt (original)
+++ incubator/stanbol/branches/lto-reasoners/reasoners/README.md Thu Nov 24 09:28:15 2011
@@ -82,16 +82,21 @@ These additional parameters can be sent:
 Supported output formats:
 Supported return formats are all classic RDF types (n3,turtle,rdf+xml) and HTML. For HTML the returned statements are provided in Turtle (Jena) or OWL Manchester syntax (OWLApi), wrapped in the stanbol layout. It would be nice to have all in the latter, which is very much readable (todo).
 
+Recently added
+=============
+
+* Support for long-term operations. This is crucial for reasoning tasks, since it can take some time with large graphs. This is needed in general for Stanbol, something like "Stanbol Jobs".
+
 Todo
 =============
+
 * Support for return types json and json-ld (need to write jersey writers)
 * The front service actually returns only inferred statements. It is useful also to have the complete set of input+inferred statements
-* Support for long-term operations. This is crucial for reasoning tasks, since it can take some time with large graphs. This is needed in general for Stanbol, something like "Stanbol Jobs".
 * Decouple input preparation from the rest endpoint resource, creating something like an InputProvider SCR api;  each InputProvider is bound to a set of additional parameters. 
 This have several benefits:
 ** Remove of additional optional parameters, bound to specific input sources from the default rest api (ex, session, scope, recipe)
 ** Remove dependencies to ontonet, rules and other modules which are not needed for standard usage. They could be implemented as InputProvider/s, bound to specific parameters.
-** Allow the addition of other input sources (for example 'graph', 'entity' or 'site')
+** Allow the addition of other input sources (for example 'graph', 'entity' or 'site') 
 * Implement a Custom Jena ReasoningService, to use a Jena rules file or a stanbol recipe (when implemented the toJena() functionality in the rules module) from configuration. This could be done as multiple SCR instance, as it is now for entityhub sites, for example.
 * Provide a validation report in case of task CHECK (validity check).
 * Implement a progress monitor, relying on the jena and owlapi apis, which have this feature, for debugging purpose