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
Describe the feature you'd like added
Assert only DC Terms namespace in prefixes, and rely on only DC terms for annotations. All terms in dc11 http://purl.org/dc/elements/1.1/ are redundantly defined in http://purl.org/dc/terms/ . I know of no reason to include both.
Describe alternatives you've considered
I know of no alternatives beside the way it is. Some developers are routinely confused. Some developers are frustrated by the inconsistent use in the larger community of relying on dc elements for some annotations and dc terms for other annotations, when all annotations can be in dc terms.
Additional context
Are there any requirements by the larger BFO community, including OBO Foundry or Industrial Ontologies Foundry (IOF), that require one or the other or both? It seems that OBO does not, but rather the opposite (expecting dc terms), as evidenced by typical queries for QC checks with ROBOT (OBO tool). https://robot.obolibrary.org/report_queries/missing_ontology_license
Describe the feature you'd like added
Assert only DC Terms namespace in prefixes, and rely on only DC terms for annotations. All terms in dc11 http://purl.org/dc/elements/1.1/ are redundantly defined in http://purl.org/dc/terms/ . I know of no reason to include both.
See this concise explanation:
https://stackoverflow.com/questions/47519315/what-is-the-difference-between-dublin-core-terms-and-dublin-core-elements-vocabu
Describe alternatives you've considered
I know of no alternatives beside the way it is. Some developers are routinely confused. Some developers are frustrated by the inconsistent use in the larger community of relying on dc elements for some annotations and dc terms for other annotations, when all annotations can be in dc terms.
Additional context
Are there any requirements by the larger BFO community, including OBO Foundry or Industrial Ontologies Foundry (IOF), that require one or the other or both? It seems that OBO does not, but rather the opposite (expecting dc terms), as evidenced by typical queries for QC checks with ROBOT (OBO tool).
https://robot.obolibrary.org/report_queries/missing_ontology_license
I have also made the same request on BFO's issue tracker.
BFO-ontology/BFO-2020#113
The text was updated successfully, but these errors were encountered: