Skip to content
This repository has been archived by the owner on Feb 22, 2024. It is now read-only.

GraphFilter/Condition on postAnnotation method #1

Open
Adeurien opened this issue Dec 18, 2013 · 0 comments
Open

GraphFilter/Condition on postAnnotation method #1

Adeurien opened this issue Dec 18, 2013 · 0 comments

Comments

@Adeurien
Copy link

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

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

1 participant