On 11/24/2010 3:58 PM, Emmanuel Lecharny wrote:
But this is like if you are working in an office in front of a
collegue : most of the time, you don't chit-chat, you work. And when
it comes to make a decision impacting the whole project, then the
discussion is moved to the ML.
In the Jena te
I think this comes down to saxon as the issue
is this helpful?
http://svn.apache.org/viewvc/servicemix/smx4/bundles/tags/org.apache.servicemix.bundles.saxon-9.1.0.1_1/pom.xml?view=markup
the other items (CyberNeko, XML Commons) may be work to find the right
links ...
Jeremy
Jeremy Carroll
On 11/12/2010 6:05 PM, Benson Margulies wrote:
CyberNeko and TagSoup both have acceptable licenses. Some people
prefer TagSoup because it does not require Xerces.
Have you read http://www.apache.org/legal/resolved.html?
No I hadn't. That is very useful.
A first reaction, concerning the GRDDL
On 11/12/2010 5:47 PM, Benson Margulies wrote:
CyberNeko is at least class B, since Tika uses it.
The actual requirement is for a parser that makes a reasonable job of
HTML in the wild, and implements SAX2
No particular reason for CyberNeko but it met those requirements, works,
and met our p
On 11/12/2010 11:51 AM, Paolo Castagna wrote:
Also (from the JenaProposal):
"The Jena GRDDL Reader has some additional dependencies:
http://jena.sourceforge.net/grddl/license.html";
BrowserLauncher2 could be removed in favor of a much simpler approach
(i.e. write it in a file!).
That is ac
On 11/12/2010 3:28 AM, Ross Gardler wrote:
One niggle: have you clarified somewhere that all the dependencies
licenses are Apache-compatible?
We have discussed this and the team believe they are licence
compatible. They have undertaken to remove any licence
incompatibilities during incubatio
- The core API for (mutable) graphs in:
http://incubator.apache.org/clerezza/mvn-site/org.apache.clerezza.rdf.core/apidocs/index.html
http://incubator.apache.org/clerezza/mvn-site/org.apache.clerezza.rdf.core/apidocs/org/apache/clerezza/rdf/core/TripleCollection.html#filter(org.apache.clerezza.rd
I could be accused of having gone overboard ... each of the slightly
different specs as an explicit representation in the code ...
Having changed job and looking at this from a different perspective I am
less convinced by the pickiness.
There is a largely unrealized goal in the IRI code to link e
On 11/9/2010 8:22 AM, Florent Guillaume wrote:
On Tue, Nov 9, 2010 at 1:19 PM, Andy Seaborne
wrote:
Jeremy identified the IRI library as a potential contribution to a commons
area. It is free-standing, and does not use or call any Jena RDF code - it
depends only on ICU4J (and JUnit + Jflex in
On 11/8/2010 7:14 AM, Olivier Grisel wrote:
There is a depedency relationship:
- Stanbol is a of application level HTTP services and set of OSGi
components that use:
- Clerezza as an OSGi service provider which in turn is using:
- Jena as a lib for parsing and serializing RDF models and as a SP
To make the commons discussion more concrete I would suggest the
following items for the commons:
- an IRI library
- some code to do with vocabularies.
- connecting to a URL and doing semweb aware content negotiation (this
is typically done badly)
(Actually the IRI code should probably be wi
11 matches
Mail list logo
