Description of the issue
I have been testing the conversion of OEMetadata to and from RDF data, and have realized that the use of the foaf:logo predicate currently is ambiguous in the Context object.
There are the properties fundingAgencyLogo and publisherLogoright next to each other, both using the same predicate.
Which when serialized to RDF results in something like this:
[] rdf:type Context ;
foaf:logo <url_of_publisher> ;
foaf:logo <url_of_funding_agency> .
Semantic wise there is no possibility to distinguish between the two logos and therefore loading the values back into the correct properties is not possible.
Ideas of solution
The most simple fix would be to use different predicates for the two properties. The best fit probably is schema:logo for one of them.
An alternative solution is to create individual objects for funder and publisher and assign the predicate inside the new objects.
I would prefer the first solution for now as it is only "minimal invasive".
Context and Environment
- Version used: 2.0.4
- Operating system: /
- Environment setup and (python) version: /
Workflow checklist
Description of the issue
I have been testing the conversion of OEMetadata to and from RDF data, and have realized that the use of the
foaf:logopredicate currently is ambiguous in theContextobject.There are the properties
fundingAgencyLogoandpublisherLogoright next to each other, both using the same predicate.Which when serialized to RDF results in something like this:
Semantic wise there is no possibility to distinguish between the two logos and therefore loading the values back into the correct properties is not possible.
Ideas of solution
The most simple fix would be to use different predicates for the two properties. The best fit probably is schema:logo for one of them.
An alternative solution is to create individual objects for funder and publisher and assign the predicate inside the new objects.
I would prefer the first solution for now as it is only "minimal invasive".
Context and Environment
Workflow checklist