View Issue Details

IDProjectCategoryView StatusLast Update
0010310Part 84: UAFX ProfilesSpecpublic2025-06-13 12:24
ReporterJan Murzyn Assigned To 
PrioritynormalSeverityminorReproducibilityhave not tried
Status newResolutionopen 
Summary0010310: AliasName Client Base - should it be mandatory from the beginning?
Description

AliasName Client Base is included as mandatory in UAFX ConnectionManager Client 2025 Facet.

I think it’s an unnecessary burden to have this as mandatory now. It can be changed to optional and considered to become mandatory in future releases. Reasoning:

⦁ Use cases of Alias Names are not clear yet. There are many open questions, which was visible during long discussions in Base Facet WG. It seems that in FA the use of Alias Names is marginal or not existing.
⦁ Nobody prototyped or demonstrated a UAFX system using Alias Names yet.

TagsNo tags attached.

Relationships

related to 0010020 acknowledgedPaul Hunkar Part 81: UAFX Connecting Devices and Information Model [sg.BaseFacet] ConnectionManager and manner of identifying Nodes 

Activities

Paul Hunkar

2025-05-14 01:33

manager   ~0022733

AlaisNames are required to be supported in the ConnectionManager models. If a server provides AliasNames, and A CM doe snot support it then the is a serious interoperability issue. it is not required for a server to use them, but a cm does not have the choice on what a server provides. AliasNames have been prototyped in UA extensively, They are required for O-PAS and used extensively - if they are not provided in a CM then a CM will not be able to operate with an O-PAS system, which is a requirement from the steering committee at this point in time.

This topic again can be discussed in the next f2f meeting if desired.

Greg Majcher

2025-06-04 14:01

manager   ~0022956

We will ask Paul to present something at the F2F. Paul may not have time to address this prior to the F2F. His Log Object work takes priority. If he cannot address this prior to the F2F, we should dedicate a meeting to this once he is able to prepare something. Depending on the timing of that we will make the decision about removing this as a mandatory feature or not.

Issue History

Date Modified Username Field Change
2025-04-28 19:35 Jan Murzyn New Issue
2025-05-14 01:33 Paul Hunkar Note Added: 0022733
2025-06-04 14:01 Greg Majcher Note Added: 0022956
2025-06-13 12:24 Greg Majcher Relationship added related to 0010020