-
Notifications
You must be signed in to change notification settings - Fork 0
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
Inapplicable data cannot be indicated #24
Comments
End point of the discussion at the Modelling Call on 26th of April 2022: |
The current definition has layerProtocolName attributes in the PtpClockSpec and SynchronizationClockSpec classes, which shall augment the clock class. The When statement at the Augmentation is referencing an attribute, which would have to be augmented at the same time. Instead of testing, whether this is actually possible, an alternative modelling is proposed. Potential proposal:
|
Decision made at the 5G-xhaul call on 7th of September 2022: Details:
|
The model attaches data for both frequency synchronization and PTP to various objects, e.g.
clock
.There is no way to indicate that some data might not be applicable. E.g. the PTP attributes would not be applicable if a clock only supports frequency synchronization.
Possible solutions:
presence
containers which are only present if contained data is applicable.The text was updated successfully, but these errors were encountered: