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

Add typValue and nomValue properties on QuantitativeValue type #2903

Open
jaw111 opened this issue Jun 15, 2021 · 1 comment
Open

Add typValue and nomValue properties on QuantitativeValue type #2903

jaw111 opened this issue Jun 15, 2021 · 1 comment
Labels
no-issue-activity Discuss has gone quiet. Auto-tagging to encourage people to re-engage with the issue (or close it!).

Comments

@jaw111
Copy link
Contributor

jaw111 commented Jun 15, 2021

I'm looking at how to represent product descriptions using Schema.org where the products are described using terms from IEC 61360-4 - Common Data Dictionary (CDD). IEC CDD uses the data model defined in ISO 13584-42, which is also used by ECLASS.

Properties in IEC CDD can be described as level type, which is equivalent to the QuantitativeValue type, where the minimum/typical/nominal/maximum values can be specified. The minimum and maximum values can be represented using the minValue and maxValue properties. Whilst the typical and nominal values could be represented using the value, there is a semantic difference between a nominal and typical value that may need to be explicitly communicated. Where typical values are generally based on some characterization of devices (i.e. actual measurements done in the lab), whilst nominal values represent some given or assigned value.

In the GoodRelations ontology (from which some terms in Schema.org are derived), the gr:hasValue property is defined to be a rdfs:subPropertyOf gr:hasMaxValue and gr:hasMinValue, whilst there are no explicit statements relating the Schema.org properties to GoodRelations properties, we would definitely want to avoid that any typical or nominal value is inferred to be a minimum and maximum value.

Therefore I would propose to add new properties typValue and nomValue with the same domain and range as the existing minValue and maxValue properties.

@github-actions
Copy link

This issue is being nudged due to inactivity.

@github-actions github-actions bot added the no-issue-activity Discuss has gone quiet. Auto-tagging to encourage people to re-engage with the issue (or close it!). label Sep 14, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
no-issue-activity Discuss has gone quiet. Auto-tagging to encourage people to re-engage with the issue (or close it!).
Projects
None yet
Development

No branches or pull requests

1 participant