You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Feb 22, 2024. It is now read-only.
When using the POST service of the Annostore, using the defined ontologies for tasks 2.5 and 3.4, the posted graph is filtered with the relation :
(null, RDF.Type, ANNOTATION_TYPE).
This filter causes the loss of all the information linked to the annotation. Moreover, the condition :
if (typeTriples.hasNext()) {
final Response.ResponseBuilder rb = Response.status(Status.BAD_REQUEST);
rb.entity("Graph contains more than one annotation");
throw new WebApplicationException(rb.build());
}
... seems to be a problem, since for each annotation we have several triples to insert.
I think that both the filter and the raised exception on the above condition should be removed.
Best,
Adrien
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
When using the POST service of the Annostore, using the defined ontologies for tasks 2.5 and 3.4, the posted graph is filtered with the relation :
(null, RDF.Type, ANNOTATION_TYPE).
This filter causes the loss of all the information linked to the annotation. Moreover, the condition :
if (typeTriples.hasNext()) {
final Response.ResponseBuilder rb = Response.status(Status.BAD_REQUEST);
rb.entity("Graph contains more than one annotation");
throw new WebApplicationException(rb.build());
}
... seems to be a problem, since for each annotation we have several triples to insert.
I think that both the filter and the raised exception on the above condition should be removed.
Best,
Adrien
The text was updated successfully, but these errors were encountered: