Open mielvds opened 1 year ago
Hi Miel, thank you for your question! I think you used ebucore correctly for pointing to the Thing that is annotated (the MediaFragment) and the "meaning" of the annotation, i.e. "annotating an Agent to a Thing" (hasAnnotationAgent). For "annotating a Location to a Thing" you could use "hasLocation" (I think). You observed that hasAnnotationRelatedAgent and hasAnnotationRelatedLocation are gone. They have not made it through the merge of CCDM and EBUCore into EBUCorePlus. I assign this issue to @tormodv who executed the merge and might remember the reason to do so. He will confirm or reject my proposal.
FWIW, I think that sticking with just ebucore:hasAnnotationAgent
is the better modeling choice, but its definition needs to be more clear.
Hi there! I'm looking into using
ebucoreplus:Annotation
for describing automatically annotated content by means of Face Recognition and so on. Using ebucore(plus) for this seems like a great fit, but I have some questions about some of the properties.I'm also not sure I'm interpreting the ontology correctly, so I'll walk through an example. Let's say I have a media resource and I want to annotate the appearance of Brad Pitt (wdt:Q35332) from second 5 to 10.
So far so good I think. Definition of
ec:hasAnnotationTarget
says "To define the target object to which the Annotation applies.", so I think its fine. But now I want to link to Brad Pitt.Is that the correct use of this property? The definition is a bit confusing: "To define the Annotation instance of an Agent. ". This could mean a lot of things.
I also see that the superproperty
ebucore:hasAnnotationPurpose
(which I interpreted to be the most generic one, but it's hard to teel, because the defintion/label are wrong),ebucore:hasAnnotationRelatedAgent
,ebucore:hasAnnotationRelatedLocation
(which had a slightly clearer definition) are gone. Does that mean thatebucore:hasAnnotationAgent
now has a generic use, so it doesn't matter wheter it's a Location or artefact?Best regards!
Miel