Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Use only one Dublin Core namespace for all DC annotations #546

Open
jonathanvajda opened this issue Nov 7, 2024 · 0 comments
Open

Use only one Dublin Core namespace for all DC annotations #546

jonathanvajda opened this issue Nov 7, 2024 · 0 comments

Comments

@jonathanvajda
Copy link

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

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

No branches or pull requests

1 participant