essepuntato / lode Goto Github PK

View Code? Open in Web Editor NEW

103.0 103.0 55.0 8.75 MB

Live OWL Documentation Environment, to convert OWL ontologies into HTML human-readable pages.

License: ISC License

CSS 18.97% XSLT 54.99% Java 14.40% HTML 11.42% Dockerfile 0.22%

lode's People

Contributors

Stargazers

Watchers

lode's Issues

LODE 2 error: "HTTP Status 500 - String index out of range: -1"

I get the following error if I try to submit my ontology: "string index index out of range" :(

Service used: http://lode2.linked.data.gov.au/
Module used: I tried all three
File: https://raw.githubusercontent.com/vocol/dwd/master/dwd_weather_ontology.tt

Error:

HTTP Status 500 - String index out of range: -1

type Exception report

message String index out of range: -1

description The server encountered an internal error that prevented it from fulfilling this request.

exception

java.lang.StringIndexOutOfBoundsException: String index out of range: -1
	java.lang.String.substring(String.java:1960)
	com.edmondchuc.lode2.ExtractOntology.removeScripts(ExtractOntology.java:754)
	com.edmondchuc.lode2.ExtractOntology.tidy(ExtractOntology.java:457)
	com.edmondchuc.lode2.ExtractOntology.transform(ExtractOntology.java:383)
	com.edmondchuc.lode2.ExtractOntology.doPost(ExtractOntology.java:279)
	javax.servlet.http.HttpServlet.service(HttpServlet.java:648)
	javax.servlet.http.HttpServlet.service(HttpServlet.java:729)
	org.apache.tomcat.websocket.server.WsFilter.doFilter(WsFilter.java:52)
	org.apache.catalina.filters.CorsFilter.handleNonCORS(CorsFilter.java:437)
	org.apache.catalina.filters.CorsFilter.doFilter(CorsFilter.java:177)

note The full stack trace of the root cause is available in the Apache Tomcat/8.0.32 (Ubuntu) logs.

Abandonned Project

It looks, like the last action by the maintainer on this project is 4 years ago. Meanwhile, there are many pull-requests unanswered.
We should decide on a fork to be the new main one, add some of the people that made PRs on this repo as maintainers/owners there (so it is less likely to get to an abandoned state again), and merge the open PRs from this repo there.
Anyone with me on this one?
Who would be wiling to be a co-owner/-maintainer on the new repo?
It would not come with any fixed responsibility or time involvement.

LODE Error / Reason: The source can't be downloaded in any permitted format.

I am not sure if this is the correct repository to open this issue, but http://purl.org/co/ is currently redirecting to a page with this error.

LODE error

Reason: The source can't be downloaded in any permitted format. # Received fatal alert: handshake_failure # Received fatal alert: handshake_failure # Received fatal alert: handshake_failure # Received fatal alert: handshake_failure # Received fatal alert: handshake_failure # Received fatal alert: handshake_failure

support schema:domain/rangeIncludes

rdfs:domain/range are monomorphic (they bind a property to only one class), whereas schema:domain/rangeIncludes are polymorphic, so they are better suited for ontology reuse.

See OnToology/OnToology#383 for more details, including an explanation by the Schema people.

What I'm looking for is to:

include them in documentation generation
allow multiple domains/ranges for a property
Of course, OWL reasoning won't work on them, but that's ok for my purposes.

@essepuntato what do you think of this idea? I'll look to implement it in LODE, but want to hear your thoughts so as not to create a code split.

Add Dockerfile and docker-compose.yaml files to support a containerized version of Lode

Currently, Lode does not provide any Dockerfile (and related docker-compose.yaml file) in order to create a containerized version of it.

print out more metadata

VladimirAlexiev#1 implements this:

print out more metadata:
dct:created, dct:modified, rdfs:seeAlso, dct:source, foaf:homepage, skos:definition (treated same as rdfs:comment), skos:scopeNote, skos:example
Don't prefixize links to Google Docs eg https://docs.google.com/document/d/1dhMOTlIOC6dOK_jksJRX0CB-GIRoiYY6fWtCnZArUhU/edit
to avoid ugly Namespace Declarations eg random-prefix -> https://docs.google.com/document/d/1dhMOTlIOC6dOK_jksJRX0CB-GIRoiYY6fWtCnZArUhU/
(f:isPrefixeable())

@essepuntato I don't know how to make this PR in your repo instead of mine without mixing it up with the pending PR #13 we have. So please review and comment on the above PR, and once we finalize #13, I'll merge both PRs or resubmit it against the new master.
Thanks!

Could not parse ontology

Hello all,

I wanted to load an ontology via a local file thanks to these command lines:

URL ontologyURL = new URL(path);' 'ontology = manager.loadOntology(IRI.create(ontologyURL.toString()));

I have the following error:

Exception in thread "main" org.semanticweb.owlapi.io.UnparsableOntologyException: Problem parsing file:/C:/Test/pizza.owl
Could not parse ontology. Either a suitable parser could not be found, or parsing failed. See parser logs below for explanation.
The following parsers were tried:

KRSSOWLParser
OWLFunctionalSyntaxOWLParser
KRSS2OWLParser
ManchesterOWLSyntaxOntologyParser
OWLXMLParser
OWLOBOParser

Detailed logs:

Parser: KRSSOWLParser
Encountered " ">" " "" at line 1, column 1.
Was expecting:

(Line 0)

Parser: OWLFunctionalSyntaxOWLParser
Encountered " "< "" at line 1, column 1.
Was expecting:
"Ontology" ...
(Line 0)

Parser: KRSS2OWLParser
de.uulm.ecs.ai.owlapi.krssparser.ParseException: Encountered " ">" " "" at line 1, column 1.
Was expecting:

Parser: ManchesterOWLSyntaxOntologyParser
Encountered '' at line 1 column 1. Expected either 'Ontology:' or 'Prefix:' (Line 1)

Parser: OWLXMLParser
Attribute not found: IRI (Line 49)

Parser: OWLOBOParser
org.coode.owlapi.obo.parser.TokenMgrError: Lexical error at line 1, column 22. Encountered: "\r" (13), after : ""

at uk.ac.manchester.cs.owl.owlapi.ParsableOWLOntologyFactory.loadOWLOntology(ParsableOWLOntologyFactory.java:308)
at uk.ac.manchester.cs.owl.owlapi.OWLOntologyManagerImpl.loadOntology(OWLOntologyManagerImpl.java:830)
at uk.ac.manchester.cs.owl.owlapi.OWLOntologyManagerImpl.loadOntology(OWLOntologyManagerImpl.java:750)
at uk.ac.manchester.cs.owl.owlapi.OWLOntologyManagerImpl.loadOntology(OWLOntologyManagerImpl.java:708)
at it.essepuntato.lode.LodeServlet.parseWithOWLAPI(LodeServlet.java:255)
at SE.LODE_application.App.main(App.java:31)

Thank you for your help.

#<hash> vs #<subject>

the anchors within the generated HTML are made up of some number/hash, instead of the actual subject, which is required for # delimited ontology IRIs.
That kind of defeats half the point of an HTML documentation of RDF.

example:

http://www.essepuntato.it/lode service down

Hi @essepuntato @seralf @nicholascar I love this service and have been using it to generate a cache visualizations of the rather large SWEET ontology suite, the visualizations can be seen at https://esipfed.github.io/stc/sweet_lode/sweetAll.html

As I began iterating through the generation of visualizations for all of the files in SWEET, after a while I encountered the following responses

<html><head><title>Apache Tomcat/6.0.35 - Error report</title><style><!--H1 {font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;font-size:22px;} H2 {font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;font-size:16px;} H3 {font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;font-size:14px;} BODY {font-family:Tahoma,Arial,sans-serif;color:black;background-color:white;} B {font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;} P {font-family:Tahoma,Arial,sans-serif;background:white;color:black;font-size:12px;}A {color : black;}A.name {color : black;}HR {color : #525D76;}--></style> </head><body><h1>HTTP Status 500 - </h1><HR size="1" noshade="noshade"><p><b>type</b> Exception report</p><p><b>message</b> <u></u></p><p><b>description</b> <u>The server encountered an internal error () that prevented it from fulfilling this request.</u></p><p><b>exception</b> <pre>javax.servlet.ServletException: Servlet execution threw an exception
</pre></p><p><b>root cause</b> <pre>java.lang.OutOfMemoryError: Java heap space
</pre></p><p><b>note</b> <u>The full stack trace of the root cause is available in the Apache Tomcat/6.0.35 logs.</u></p><HR size="1" noshade="noshade"><h3>Apache Tomcat/6.0.35</h3></body></html>

...

java.lang.OutOfMemoryError: Java heap space

I therefore fear that I may have crashed your service.
I wanted to say that I was not executing these requests in parallel or within a short time of each other. Each request was submitted literally minutes apart.
Apologies, if I crashed the service.

Cryptic error

If there are individuals in the ontology with an IRI that is simply a URL without any final slash (http://www.example.org) LODE gives the following error:

LODE error
Reason: An empty sequence is not allowed as the third argument of substring()

Which isn't easy to understand.
It would be nice if it was explained more clearly to the user.

server down?

Hello @essepuntato,
I noticed that in these last days the server of LODE is down:

Proxy Error
The proxy server received an invalid response from an upstream server.
The proxy server could not handle the request GET /lode/extract.
Reason: Error reading from remote server

is it possible to fix it?
I've created my ontology documentation there and I've linked my webGIS app with the ontology semantics.

Navigation panel on side

I like the product!

Is it possible to have a navigation pane on the side. Something like this:
https://w3c.github.io/json-ld-bp/

I would also be nice for navigation panel could contract/expand (using "+", "-" icons).

Error processing nested resources

I expect

processing

<owl:ontology>
...

    <dct:creator>
      <owl:NamedIndividual rdf:about="https://w3id.org/italia/data/organization/support-unit/cnr-Z6HZEH/stlab">
        <rdf:type rdf:resource="http://dati.gov.it/onto/dcatapit#Agent"/>
        <dct:identifier>cnr - Z6HZEH - STLab</dct:identifier>
        <foaf:name xml:lang="it">Istituto di Scienze e Tecnologie della Cognizione del CNR - Semantic Technology Lab (STLab)</foaf:name>
      </owl:NamedIndividual>
    </dct:creator>
...

</owl:ontology>

Instead

lode    | Error on line 1976 of extraction.xsl:
lode    |   XTTE1020: A sequence of more than one item is not allowed as the @select attribute of xsl:sort
lode    |   at xsl:call-template name="get.author" (file:///opt/LODE/src/main/webapp/extraction.xsl#196)
lode    |   at xsl:call-template name="structure" (file:///opt/LODE/src/main/webapp/extraction.xsl#260)
lode    |   at xsl:apply-templates (file:///opt/LODE/src/main/webapp/extraction.xsl#121)
lode    |      processing /rdf:RDF/owl:Ontology[1]
lode    |   in built-in template rule
lode    | Error on line 1976 of extraction.xsl:
lode    |   XTTE1020: A sequence of more than one item is not allowed as the @select attribute of xsl:sort
lode    |   at xsl:call-template name="get.author" (file:///opt/LODE/src/main/webapp/extraction.xsl#196)
lode    |   at xsl:call-template name="structure" (file:///opt/LODE/src/main/webapp/extraction.xsl#260)
lode    |   at xsl:apply-templates (file:///opt/LODE/src/main/webapp/extraction.xsl#121)
lode    |      processing /rdf:RDF/owl:Ontology[1]
lode    |   in built-in template rule
lode    | Error on line 1976 of extraction.xsl:
lode    |   XTTE1020: A sequence of more than one item is not allowed as the @select attribute of xsl:sort
lode    |   at xsl:call-template name="get.author" (file:///opt/LODE/src/main/webapp/extraction.xsl#196)
lode    |   at xsl:call-template name="structure" (file:///opt/LODE/src/main/webapp/extraction.xsl#260)
lode    |   at xsl:apply-templates (file:///opt/LODE/src/main/webapp/extraction.xsl#121)
lode    |      processing /rdf:RDF/owl:Ontology[1]
lode    |   in built-in template rule

Note

Applying this changes, the file works. https://gist.github.com/ioggstream/d6aa67cd2623f40dacefab5f1a6b7bde/revisions
The problem here is that LODE doesn't seem to be compatible with files generated by Apache Jena or python rdflib.

See

LODE/src/main/webapp/extraction.xsl

Line 1974 in 91227f9

select="dc:creator|dcterms:creator[ancestor::owl:Ontology]">

cc: @giorgialodi

f:string-last-index-of fails on relative uri with slash

Input:

@base                      <http://data.businessgraph.io/>.
<status/> a skos:ConceptScheme, owl:NamedIndividual;

Note the ConceptScheme URL ends in /: I think this is a legit and often used convention for concept schemes (so one could define a prefix for it eg status:, and use it in Concept qnames, eg status:active).

Causes this error:

Type error at char 146 in xsl:variable/@select on line 1799 column 236 of extraction.xsl:
  XPTY0004: An empty sequence is not allowed as the third argument of substring()
  at xsl:apply-templates (extraction.xsl#1116)
     processing /assertions/assertion[1]/@rdf:resource
  at xsl:call-template name="get.individual.assertions" (extraction.xsl#1015)
  at xsl:call-template name="get.individual.description" (extraction.xsl#454)
  at xsl:apply-templates (extraction.xsl#1605)
     processing /rdf:RDF/owl:NamedIndividual[3]
  at xsl:call-template name="get.namedindividuals" (extraction.xsl#182)
  at xsl:call-template name="structure" (extraction.xsl#193)
  at xsl:apply-templates (extraction.xsl#105)
     processing /rdf:RDF/owl:Ontology[1]
  in built-in template rule
An empty sequence is not allowed as the third argument of substring()

The reported line is last below:

    <xsl:function name="f:getPrefixFromIRI" as="xs:string?">
        <xsl:param name="iri" as="xs:string" />
        
        <xsl:if test="not(starts-with($iri,'_:'))">
            <xsl:variable name="iriNew" select="if (contains($iri,'#') or contains($iri,'/')) then $iri else concat(base-uri($root), $iri)" as="xs:string" />
            
            <xsl:variable name="ns" select="if (contains($iriNew,'#')) then substring($iriNew,1,f:string-first-index-of($iriNew,'#')) else substring($iriNew,1,f:string-last-index-of(replace($iriNew,'://','---'),'/'))" as="xs:string" />

Maybe iriNew is to blame? It assumes that an iri with #/ is absolute. My turtle example uses a relative IRI with / but when I examine the corresponding rdf, I don't see any relative IRIs...

My XSL debugging skills are non-existent.

SSL error on Let'sEncrypt

Using LODE to connect to sites that use Let's Encrypt's certificates, Java throws the following error-

sun.security.validator.ValidatorException: PKIX path building failed

See more info at - link

As LODE is used in several other services such as Protege and WIDOCO, the error also crops up on them.

A sequence of more than one item is not allowed as the value of parameter $iri

hello,

i am getting this error:

LODE error

Reason: A sequence of more than one item is not allowed as the value of parameter $iri ("http://www.w3.org/2004/02/skos...", "http://www.w3.org/2004/02/skos...")

for this tiny ontology (which passes riot --validate):

<rdf:RDF
    xmlns:dct="http://purl.org/dc/terms/"
    xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
    xmlns:owl="http://www.w3.org/2002/07/owl#"
    xmlns:skos="http://www.w3.org/2004/02/skos/core#"
    xmlns:rdfs="http://www.w3.org/2000/01/rdf-schema#"
    xmlns:skosxl="http://www.w3.org/2008/05/skos-xl#"
    xmlns:xsd="http://www.w3.org/2001/XMLSchema#">
  <owl:Ontology rdf:about="http://www.example.com/ont">
    <rdfs:label>an ontology</rdfs:label>
    <rdfs:comment>comment here</rdfs:comment>
  </owl:Ontology>
  <owl:AnnotationProperty rdf:about="http://www.w3.org/2004/02/skos/core#editorialNote">
    <rdfs:subPropertyOf>
      <owl:AnnotationProperty rdf:about="http://www.w3.org/2004/02/skos/core#note">
        <skos:scopeNote xml:lang="en">This property may be used directly, or as a super-property for more specific note types.</skos:scopeNote>
        <skos:definition xml:lang="en">A general note, for any purpose.</skos:definition>
        <rdfs:label xml:lang="en">note</rdfs:label>
        <rdfs:isDefinedBy rdf:resource="http://www.w3.org/2004/02/skos/core"/>
      </owl:AnnotationProperty>
    </rdfs:subPropertyOf>
    <skos:definition xml:lang="en">A note for an editor, translator or maintainer of the vocabulary.</skos:definition>
    <rdfs:label xml:lang="en">editorial note</rdfs:label>
    <rdfs:isDefinedBy rdf:resource="http://www.w3.org/2004/02/skos/core"/>
  </owl:AnnotationProperty>
</rdf:RDF>

full log:

____#### 8081 : http
Error on line 628 of extraction.xsl:
  XTTE0590: A sequence of more than one item is not allowed as the value of parameter $iri
  ("http://www.w3.org/2004/02/skos...", "http://www.w3.org/2004/02/skos...")
  at xsl:apply-templates (file:///mnt/LODE/src/main/webapp/extraction.xsl#1946)
     processing /rdf:RDF/owl:AnnotationProperty[1]/rdfs:subPropertyOf[1]/owl:AnnotationProperty[1]/rdfs:label[1]
  at xsl:call-template name="get.entity.name" (file:///mnt/LODE/src/main/webapp/extraction.xsl#577)
  at xsl:apply-templates (file:///mnt/LODE/src/main/webapp/extraction.xsl#663)
     processing /rdf:RDF/owl:AnnotationProperty[1]/rdfs:subPropertyOf[1]/owl:AnnotationProperty[1]
  at xsl:apply-templates (file:///mnt/LODE/src/main/webapp/extraction.xsl#1676)
     processing /rdf:RDF/owl:AnnotationProperty[1]/rdfs:subPropertyOf[1]
  at xsl:call-template name="get.property.superproperty" (file:///mnt/LODE/src/main/webapp/extraction.xsl#1597)
  at xsl:call-template name="get.property.description" (file:///mnt/LODE/src/main/webapp/extraction.xsl#587)
  at xsl:apply-templates (file:///mnt/LODE/src/main/webapp/extraction.xsl#2259)
     processing /rdf:RDF/owl:AnnotationProperty[1]
  at xsl:call-template name="get.annotationproperties" (file:///mnt/LODE/src/main/webapp/extraction.xsl#238)
  at xsl:call-template name="structure" (file:///mnt/LODE/src/main/webapp/extraction.xsl#260)
  at xsl:apply-templates (file:///mnt/LODE/src/main/webapp/extraction.xsl#121)
     processing /rdf:RDF/owl:Ontology[1]
  in built-in template rule
Error on line 628 of extraction.xsl:
  XTTE0590: A sequence of more than one item is not allowed as the value of parameter $iri
  ("http://www.w3.org/2004/02/skos...", "http://www.w3.org/2004/02/skos...")
  at xsl:apply-templates (file:///mnt/LODE/src/main/webapp/extraction.xsl#1946)
     processing /rdf:RDF/owl:AnnotationProperty[1]/rdfs:subPropertyOf[1]/owl:AnnotationProperty[1]/rdfs:label[1]
  at xsl:call-template name="get.entity.name" (file:///mnt/LODE/src/main/webapp/extraction.xsl#577)
  at xsl:apply-templates (file:///mnt/LODE/src/main/webapp/extraction.xsl#663)
     processing /rdf:RDF/owl:AnnotationProperty[1]/rdfs:subPropertyOf[1]/owl:AnnotationProperty[1]
  at xsl:apply-templates (file:///mnt/LODE/src/main/webapp/extraction.xsl#1676)
     processing /rdf:RDF/owl:AnnotationProperty[1]/rdfs:subPropertyOf[1]
  at xsl:call-template name="get.property.superproperty" (file:///mnt/LODE/src/main/webapp/extraction.xsl#1597)
  at xsl:call-template name="get.property.description" (file:///mnt/LODE/src/main/webapp/extraction.xsl#587)
  at xsl:apply-templates (file:///mnt/LODE/src/main/webapp/extraction.xsl#2259)
     processing /rdf:RDF/owl:AnnotationProperty[1]
  at xsl:call-template name="get.annotationproperties" (file:///mnt/LODE/src/main/webapp/extraction.xsl#238)
  at xsl:call-template name="structure" (file:///mnt/LODE/src/main/webapp/extraction.xsl#260)
  at xsl:apply-templates (file:///mnt/LODE/src/main/webapp/extraction.xsl#121)
     processing /rdf:RDF/owl:Ontology[1]
  in built-in template rule
Error on line 628 of extraction.xsl:
  XTTE0590: A sequence of more than one item is not allowed as the value of parameter $iri
  ("http://www.w3.org/2004/02/skos...", "http://www.w3.org/2004/02/skos...")
  at xsl:apply-templates (file:///mnt/LODE/src/main/webapp/extraction.xsl#1946)
     processing /rdf:RDF/owl:AnnotationProperty[1]/rdfs:subPropertyOf[1]/owl:AnnotationProperty[1]/rdfs:label[1]
  at xsl:call-template name="get.entity.name" (file:///mnt/LODE/src/main/webapp/extraction.xsl#577)
  at xsl:apply-templates (file:///mnt/LODE/src/main/webapp/extraction.xsl#663)
     processing /rdf:RDF/owl:AnnotationProperty[1]/rdfs:subPropertyOf[1]/owl:AnnotationProperty[1]
  at xsl:apply-templates (file:///mnt/LODE/src/main/webapp/extraction.xsl#1676)
     processing /rdf:RDF/owl:AnnotationProperty[1]/rdfs:subPropertyOf[1]
  at xsl:call-template name="get.property.superproperty" (file:///mnt/LODE/src/main/webapp/extraction.xsl#1597)
  at xsl:call-template name="get.property.description" (file:///mnt/LODE/src/main/webapp/extraction.xsl#587)
  at xsl:apply-templates (file:///mnt/LODE/src/main/webapp/extraction.xsl#2259)
     processing /rdf:RDF/owl:AnnotationProperty[1]
  at xsl:call-template name="get.annotationproperties" (file:///mnt/LODE/src/main/webapp/extraction.xsl#238)
  at xsl:call-template name="structure" (file:///mnt/LODE/src/main/webapp/extraction.xsl#260)
  at xsl:apply-templates (file:///mnt/LODE/src/main/webapp/extraction.xsl#121)
     processing /rdf:RDF/owl:Ontology[1]
  in built-in template rule

Command line version

I would love to see a command line version: lode.sh input.rdf output.html

Make lode be able to optionally serve over HTTPS (behind a reverse proxy)

Lode is currently not able to optionally serve files over HTTPS, if behind a reverse proxy.

This is due to two issues:

The servlet hardcodes the http:// prefix while loading css/js resources -> should be changed to // to automatically adapt to the schema
The jetty configuration needs to be instructed to forward https headers to the application so that it can automatically adapt to the schema in use

web version offline

the LODE web services seems to be offline.

Update all dependencies in pom.xml

Several of them are pretty old. PR coming to update them.

Customisation of rendered annotations

Thanks for providing LODE, it's a great tool that I use often. Today I discovered that it renders only certain annotations, like rdfs:label or rdfs:comment. I've an ontology where we try to be more precise and we use properties like dcterms:description, skos:editorialNote. These annotations seem to be currently ignored by LODE, I don't see them in the rendered HTML. I wish I could be able to configure them as desired in the output. I know that the problem could be mitigated by defining some mappings and then enabling the reasoner (e.g., dcterms:description subPropertyOf rdfs:comment). However, that's not the same I want, because I'd like to let the reader know that an editorial note is there with the precise property and not as a generic comment. Besides, I'm not even sure that the OWLAPI reasoner works with hierarchies of annotation properties.

A related issue is that LODE seems to report properties like rdfs:comment only once, even if you have multiple comments for a class/property.

It should be possible to do that by simply adding a configuration option (plus some documentation) to list additional XSL files to be imported by the main one.

LODE error Reason: An empty sequence is not allowed as the value of variable $rdf

I got the above error when trying to access my OWL ontology at:
http://www.dadfha.com:8080/lode/extract?url=http://www.dadfha.com/ont/hls-latest.owl

But the same file is working fine with your service:
http://www.essepuntato.it/lode/owlapi/http://www.dadfha.com/ont/hls-latest.owl

My env is Ubuntu 16.04.1 LTS (GNU/Linux 4.4.0-28-generic x86_64).
Just follow README by git clone your repo and mvn clean jetty:run

OWASP dependency check

Expected - pom.xml should contain OWASP dependency check plugin

<plugin>
	<groupId>org.owasp</groupId>
	<artifactId>dependency-check-maven</artifactId>
	<version>6.0.1</version>
	<executions>
		<execution>
			<goals>
				<goal>check</goal>
			</goals>
		</execution>
	</executions>
</plugin>

OWASP check output:

One or more dependencies were identified with known vulnerabilities in LODE:

commons-beanutils-1.9.3.jar (pkg:maven/commons-beanutils/[email protected], cpe:2.3:a:apache:commons_beanutils:1.9.3:*:*:*:*:*:*:*) : CVE-2014-0114, CVE-2019-10086
commons-io-2.4.jar (pkg:maven/commons-io/[email protected], cpe:2.3:a:apache:commons_io:2.4:*:*:*:*:*:*:*) : CVE-2021-29425
guava-18.0.jar (pkg:maven/com.google.guava/[email protected], cpe:2.3:a:google:guava:18.0:*:*:*:*:*:*:*) : CVE-2018-10237, CVE-2020-8908
guice-4.0-beta.jar/META-INF/maven/com.google.guava/guava/pom.xml (pkg:maven/com.google.guava/[email protected], cpe:2.3:a:google:guava:11.0.1:*:*:*:*:*:*:*) : CVE-2018-10237, CVE-2020-8908
httpclient-4.2.3.jar (pkg:maven/org.apache.httpcomponents/[email protected], cpe:2.3:a:apache:httpclient:4.2.3:*:*:*:*:*:*:*) : CVE-2014-3577, CVE-2015-5262, CVE-2020-13956
httpclient-cache-4.2.5.jar (pkg:maven/org.apache.httpcomponents/[email protected], cpe:2.3:a:apache:httpclient:4.2.5:*:*:*:*:*:*:*) : CVE-2014-3577, CVE-2020-13956
jackson-databind-2.3.3.jar (pkg:maven/com.fasterxml.jackson.core/[email protected], cpe:2.3:a:fasterxml:jackson-databind:2.3.3:*:*:*:*:*:*:*) : CVE-2017-7525, CVE-2018-7489, CVE-2020-35490, CVE-2020-35491, CVE-2020-36518, CVE-2022-42003, CVE-2022-42004
jena-core-2.10.1.jar (pkg:maven/org.apache.jena/[email protected], cpe:2.3:a:apache:jena:2.10.1:*:*:*:*:*:*:*) : CVE-2021-39239, CVE-2022-28890
jena-iri-0.9.6.jar (pkg:maven/org.apache.jena/[email protected], cpe:2.3:a:apache:jena:0.9.6:*:*:*:*:*:*:*) : CVE-2021-39239, CVE-2022-28890
jquery.js (pkg:javascript/[email protected]) : CVE-2011-4969, CVE-2012-6708, CVE-2015-9251, CVE-2019-11358, CVE-2020-11022, CVE-2020-11023
log4j-1.2.17.jar (pkg:maven/log4j/[email protected], cpe:2.3:a:apache:log4j:1.2.17:*:*:*:*:*:*:*) : CVE-2019-17571, CVE-2020-9493, CVE-2021-4104, CVE-2022-23302, CVE-2022-23305, CVE-2022-23307
org.apache.commons.io-2.4.jar (pkg:maven/org.apache.directory.studio/[email protected], cpe:2.3:a:apache:commons_io:2.4:*:*:*:*:*:*:*, cpe:2.3:a:apache:directory_studio:2.4:*:*:*:*:*:*:*) : CVE-2021-29425
owlapi-distribution-4.0.2.jar (pkg:maven/net.sourceforge.owlapi/[email protected], cpe:2.3:a:apache:commons-httpclient:4.0.2:*:*:*:*:*:*:*, cpe:2.3:a:apache:commons_io:4.0.2:*:*:*:*:*:*:*, cpe:2.3:a:binary_project:binary:4.0.2:*:*:*:*:*:*:*) : CVE-2012-6153
owlapi-distribution-4.0.2.jar: httpclient-4.2.5.jar (pkg:maven/org.apache.httpcomponents/[email protected], cpe:2.3:a:apache:httpclient:4.2.5:*:*:*:*:*:*:*) : CVE-2014-3577, CVE-2015-5262, CVE-2020-13956
owlapi-distribution-4.0.2.jar: xz-1.5.jar (cpe:2.3:a:tukaani:xz:1.5:*:*:*:*:*:*:*) : CVE-2015-4035
xercesImpl-2.11.0.jar (pkg:maven/xerces/[email protected], cpe:2.3:a:apache:xerces2_java:2.11.0:*:*:*:*:*:*:*) : CVE-2012-0881, CVE-2013-4002, CVE-2017-10355, CVE-2022-23437

Form not working with Raw github files

More and more ontology development happen on Github.

It would be so cool to be able to point to a raw github file from LODE; this works when doing e.g. http://www.essepuntato.it/lode/https://raw.githubusercontent.com/assemblee-virtuelle/pair/dev/PAIR_v0.4.owl but not when submitting the URL of the RAW github file in the form at http://www.essepuntato.it/lode.

LODE error when using owlapi=true

Hello

i get the following error when using the parameter owlapi=true
e.g. localhost:9030/lode/extract?owlapi=true&url=https://localhost/test.rdf)

LODE error
Reason: Could not find an ontology storer which can handle the format: org.semanticweb.owlapi.io.RDFXMLOntologyFormat@1b0bc2f

I followed the steps described in readme.md, the examples are working fine.
The rdf file is fine as well, tested with http://www.essepuntato.it/lode/owlapi/http://domain.com/test.rdf

Hard to build

Thanks for setting up this service. In the current version it's rather hard to build. May I suggest to use maven as build environment?

essepuntato / lode Goto Github PK

lode's People

Contributors

Stargazers

Watchers

Forkers

lode's Issues

LODE error

Detailed logs:

I expect

Instead

Note

See

Recommend Projects

Recommend Topics

Recommend Org