feat: margin of error #190
Conversation
🦋 Changeset detectedLatest commit: c046730 The changes in this PR will be included in the next version bump. This PR includes changesets to release 1 package
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
relation/core.md
Outdated
|
|
||
| ### relation:Confidence {#MarginOfError} | ||
|
|
||
| Use `Confidence` to specify the level of uncertainty in the estimate. It can be used multiple times, |
There was a problem hiding this comment.
Use
Confidenceto specifythe level ofuncertainty in the estimate.
If i were to read something about a level of uncertainty, I would immediately think about some confidence-level (i.e. 99% or 95%)
| sh:path ex:lower-confidence-dimension ; | ||
| meta:dimensionRelation [ | ||
| a relation:ConfidenceLowerBound ; | ||
| dcterms:type "Confidence interval" ; |
There was a problem hiding this comment.
I don't remember if this was already discussed and agreed-upon elsewhere, but the recommended values for dcterms:type may be URIs from a controlled vocabulary
There was a problem hiding this comment.
You're right. It is stated by the vocabulary itself
Recommended practice is to use a controlled vocabulary such as the DCMI Type Vocabulary [DCMI-TYPE]
| ] ; | ||
| ] ; | ||
| sh:property [ | ||
| sh:path ex:lower-confidence-dimension ; |
There was a problem hiding this comment.
Found a small typo here:
sh:property [
sh:path ex:upper-confidence-dimension ;
Adds a new
margin of error, including separate types to relate to measure's lower and upper values to allow for asymmetrical error bars