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

Any (planned) relationship to QUDT? http://www.qudt.org/2.1/vocab/unit #894

Closed
hubert-associates opened this issue Jan 17, 2021 · 4 comments

Comments

@hubert-associates
Copy link

Relationship to W3Cs http://www.qudt.org/2.1/vocab/unit ?
Thanks!

@angularsen
Copy link
Owner

Hi, never hear of this before.
Could you please help me understand what exactly you would envision adding/changing in Units.NET to establish a relationship?

@ebfortin
Copy link
Contributor

I looked quickly and it seems to be trying to solve the same problem as UnitNet. But it's a specification not an implementation. Maybe some interesting concept could be grabbed from it. But I don't see UnitNet as an implementation of QUDT. Would be from what I see a major undertaking.

@lipchev
Copy link
Collaborator

lipchev commented Feb 17, 2021

I have, a while ago, looked into some of the major ontologies (here's the review paper I have bookmarked).

In terms of "stealing-from" - I remember the term measurement scale which I quite liked - here's the related discussion.

Also- as part of some future v5, I've suggested extending the JSON definitions with (optional) links to existing ontological references.

I don't know exactly how this works but I'm guessing there is a use case somewhere for (de)serializing rdf, provided that the reference exists in the UnitInfo.

However I'm yet to discover a single hello world example that communicates with something like a sparql endpoint (such as wiki-data, or even a local store), using anything remotely resembling a POCO (assuming to contain our quantities). If anyone has one available- please, I'd love to check it out.

@angularsen
Copy link
Owner

I'm closing this as no one seems to recognize a concrete feature or change to implement from this. Reopen if someone wants to pursue this further.

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

No branches or pull requests

4 participants