(feat) Improve content negociation using dedicated URI regarding fetch_attr
After fixing !437 (merged) we found out that the RDF triples generated do not follow the URI queried. The owl:sameAs
triple is well-defined, but we would like to have fetch_attr
as subject for the triples if the fetch_attr
is queried, and the other way if the eid
is queried.
I do not know if this is the best way to improve this. What do you think @ethieblin @nchauvat