-
Notifications
You must be signed in to change notification settings - Fork 1
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
Does Data Type Representation indeed need a Version? #108
Comments
@zwing99 has proposed that we version the entire collection of Representations using semantic versioning. As such, we would carry a single Representation version number across the entire Application Data Model. Data consumers would simply reference the appropriate version of the codes. As such, we could remove the version from each Representatation. @strhea and I like the solution. @aferreyra what are your thoughts? |
Yes, please version them as one! |
I think it’s fine to version the whole thing. I assume an API implementation will have a ModDate on each entry to facilitate synchronization.
Thanks,
Andres
Get Outlook for iOS<https://aka.ms/o0ukef>
…________________________________
From: Zac Oler ***@***.***>
Sent: Wednesday, September 20, 2023 11:33:27 AM
To: ADAPT/Standard ***@***.***>
Cc: Ferreyra Andres USRS ***@***.***>; Mention ***@***.***>
Subject: Re: [ADAPT/Standard] Does Data Type Representation indeed need a Version? (Issue #108)
<https://github.com/zwing99>
CAUTION: This email originated from outside of the organization. Do not click links or open attachments unless you recognize the sender and know the content is safe.
________________________________
@zwing99 has proposed that we version the entire collection of Representations using semantic versioning. As such, we would carry a single Representation version number across the entire Application Data Model. Data consumers would simply reference the appropriate version of the codes. As such, we could remove the version from each Representatation. @strhea<https://github.com/strhea> and I like the solution. @aferreyra<https://github.com/aferreyra> what are your thoughts?
Yes, please version them as one!
—
Reply to this email directly, view it on GitHub<#108 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/ACGW26AOW64LCXIGXTP4JF3X3L5DPANCNFSM6AAAAAA2RU3QX4>.
You are receiving this because you were mentioned.Message ID: ***@***.***>
This message may contain confidential information. If you are not the designated recipient, please notify the sender immediately, and delete the original and any copies. Any use of the message by you is prohibited.
|
Works for me! |
Agreement in 27 September 2023 meeting to implement as proposed, as well as implementing a similar attribute for Unit System version. |
Version requires that any id of a Representation is compound, with Code & Version. Do we intend to version the codes often enough to make the complexity worthwhile?
The text was updated successfully, but these errors were encountered: