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

Datatype of PhysicalProperties::temperature is undefined #36

Open
openBackhaul opened this issue Mar 5, 2024 · 2 comments
Open

Datatype of PhysicalProperties::temperature is undefined #36

openBackhaul opened this issue Mar 5, 2024 · 2 comments

Comments

@openBackhaul
Copy link
Owner

Potential proposal:
Datatype of PhysicalProperties::temperature should be defined to be INT16 in TransmitterEquipment Spec.

@openBackhaul openBackhaul self-assigned this Mar 7, 2024
@openBackhaul
Copy link
Owner Author

openBackhaul commented Apr 16, 2024

As the CoreIM did not define a datatype, the UML2YANG tool assigned String.
It is preferred not to change CoreIM and mediator implementations by sticking with String, but the format of the value inside the String shall be defined in a statement in the TransmitterEquipment Spec.

Decision during the LF ONMI x-haul call on 24th of April 2024:
§31 'ActualEquipment' in chapter 9 'Information' of the 'TransmitterEquipment Spec.' shall be complemented by the following statement: "The value of the PhysicalProperties :: temperature attribute shall be formatted as a decimal64 Built-In Type as it is described in chapter 9.3.1 'Lexical Representation' of the RFC 7950 'The YANG 1.1 Data Modeling Language'."

@openBackhaul
Copy link
Owner Author

Has been updated in Equipment_3.0.0-tsi.240515.1100+spec.1.doc

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

1 participant