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

[ALIGNMENT] reprSciUnits with QUDT #217

Closed
dr-shorthair opened this issue Sep 9, 2020 · 0 comments · Fixed by #221
Closed

[ALIGNMENT] reprSciUnits with QUDT #217

dr-shorthair opened this issue Sep 9, 2020 · 0 comments · Fixed by #221
Assignees
Milestone

Comments

@dr-shorthair
Copy link
Collaborator

dr-shorthair commented Sep 9, 2020

Motivation

QUDT is a standalone system for representation of quantities and units. After a period in the doldrums, it is now being maintained publicly and individual resources can (mostly) be accessed as linked-data from their canonical URIs - e.g. http://qudt.org/vocab/unit/M-PER-SEC . The SWEET master units vocabulary should be aligned with the QUDT master units vocabulary . We might consider retiring the local vocabulary in favour of adopting an externally maintained system. Units required by SWEET and not currently in QUDT can be requested by submitting an issue and pull-request.

Existing alignments

Please check out the existing alignment graphs to make sure an alignment does not already exist. If it does then consider editing or updating the alignment rather than providing a new one.
Additionally, please follow the same style, especially for metadata such that we have some homogeneity throughout the style of SWEET alignments.

Tooling

Have a look at the SWEET Alignment Manager which you may use to generate an initial alignment.

@dr-shorthair dr-shorthair self-assigned this Sep 9, 2020
@lewismc lewismc linked a pull request Jan 21, 2021 that will close this issue
@lewismc lewismc added this to the 3.5.0 milestone Jan 21, 2021
@lewismc lewismc closed this as completed Jan 21, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants