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

Consider a specific schema field for unit #105

Open
ianfore opened this issue Mar 3, 2021 · 0 comments
Open

Consider a specific schema field for unit #105

ianfore opened this issue Mar 3, 2021 · 0 comments
Labels
feature New feature or request

Comments

@ianfore
Copy link
Contributor

ianfore commented Mar 3, 2021

Background
In Search discussion on 2 March the following scope was discussed - see document
What is the scope of Search?

  1. agree on how we search for things with a given data model
  2. agree on how we describe data models
  3. agree on the data models themselves

The conclusion was that 1 and 2 are in scope. 3 is beyond scope for specific models but is facilitated by 2. Notably models defined in 3 would be recorded via 2.

Issue
The issue here concerns 2. The schema provided by /tables//info are how the models in 2 are made available.
The specific request is that the metaschema used for 2 should provide explicit handling of unit of measure in structured form.
The current metaschema is JSON-Schema. In Search examples to date unit have been embedded in $comment.
e.g.

{'age':{
   "type": "number",
   "$comment": "UNIT 'Years'",
   "description": "Participant reference age"
}

Finding some way to include unit should be considered. Likely using an existing semantic standard for unit of measure.
The following is a conceptual illustration of a minimal change to accomplish this.

{'age':{
   "type": "number",
   "unit": "Years",
   "description": "Participant reference age"
}

As a test case, the handling of unit should allow for automated use of the kind of age mappings illustrated in this FASP Script.

@mcupak mcupak added this to the 1.0.0 milestone Apr 14, 2021
@mcupak mcupak added the feature New feature or request label Apr 14, 2021
@mcupak mcupak modified the milestones: 1.0.0, 1.1.0 Apr 14, 2021
@mcupak mcupak modified the milestone: 1.1.0 May 26, 2021
@mcupak mcupak removed this from the 1.1.0 milestone Dec 6, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants