Closed borriellom closed 9 years ago
It fails since the NIF you submit seems to be incorrect in the following part:
<http://freme-project.eu/#char=17,20>
a nif:Context , nif:RFC5147String , nif:String ;
nif:anchorOf "day"@en ;
nif:beginIndex "17"^^xsd:nonNegativeInteger ;
nif:endIndex "20"^^xsd:nonNegativeInteger ;
nif:referenceContext <http://freme-project.eu/> ;
itsrdf:term "yes" ;
itsrdf:termInfoRef :2724437 .
the string "day" is marked as nif:Context, however it does not contain nif:isString information. Actually, e-Entity is processing the text of nif:isString. This causes the issue.
This needs to be fixed in e-Terminology, but I will also fix this NullPointerException in DBpedia spotlight. Thanks for reporting this!
I reported this issue to e-Entity https://github.com/freme-project/e-Entity/issues/35
Thanks for the analysis Milan. I assign it to Andis.
fixed from the e-Entity side, check
curl -v -X POST -d @termAnnotatedNIFFile.ttl "http://api-dev.freme-project.eu/current/e-entity/dbpedia-spotlight/documents?confidence=0.2&language=en&informat=turtle" -H "Content-Type:"
Is it correct that the NIF file returned by the e-Entity service doesn't contain term annotations anymore ? I expected an incremental enrichment of the file.
good question, yes you are right, this was fixed, now it works as an incremental enrichment.
@m1ci do term object really need nif:IsString? term objects are created and extracted from string and now becames as term anotations.
This is original String [from example above]:
<http://freme-project.eu/>
a nif:Context , nif:RFC5147String , nif:String ;
nif:beginIndex "0"^^xsd:nonNegativeInteger ;
nif:endIndex "20"^^xsd:nonNegativeInteger ;
nif:isString "What a beautiful day"@en .
and e-terminology is not creating any new string, but is adding anchors or term objects to output.
<http://freme-project.eu/#char=17,20>
a nif:Context , nif:RFC5147String , nif:String ;
nif:anchorOf "day"@en ;
nif:beginIndex "17"^^xsd:nonNegativeInteger ;
nif:endIndex "20"^^xsd:nonNegativeInteger ;
nif:referenceContext <http://freme-project.eu/> ;
itsrdf:term "yes" ;
itsrdf:termInfoRef :2724437 .
Maybe we must not mark the term object as nif:Context, because there is reference nif:referenceContext http://freme-project.eu/ ;
@m1ci is category nif:isString needed for term annotations in nif?
@m1ci is category nif:isString needed for term annotations in nif?
no, nif:String
is only required for nif:Context
. Terms and other substrings should contain nif:anchor
as it is in https://github.com/freme-project/Broker/issues/81#issuecomment-134505665
The topic of this issue has changed. I created #118 to deal with the bug report here
When I submit to the e-Entity (DBpedia engine) service a NIF file returned by the e-Terminology service, a NullPointerException occurs.
termAnnotatedNIFFile.ttl
Request to e-Entity service
Response from e-Entity