You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The ContactInformation SMC from the ContactInformations template 1.0 is used within the DigitalNameplate template 2.0.
The semanticId of ContactInformation is the same in the ContactInformations template and the ContactInformation SMC in the DigitalNameplate template.
I would thus expect the ContactInformation SMC to be exactly the same in both templates.
However, this is not the case.
In the ContactInformations template the NationalCode has a Multiplicity qualifier of ZeroToOne.
In the DigitalNameplate template the NationalCode has a Multiplicity qualifier of One.
Please fix or clarify the reason for this breaking inconsistency.
The text was updated successfully, but these errors were encountered:
I would say the PDF-documentation of Digital Nameplate 2.0 indicates that some properties are mandatorily required to ensure the provision of a physical address. (see chap. 3.2 on page 13)
Independent of what the PDF says, the AASX packages are inconsistent. The semantic ids are supposed to be a unique identifier. The issue is that the same semantic id is used for two different models.
The
ContactInformation
SMC from theContactInformations
template 1.0 is used within theDigitalNameplate
template 2.0.The
semanticId
ofContactInformation
is the same in theContactInformations
template and theContactInformation
SMC in theDigitalNameplate
template.I would thus expect the
ContactInformation
SMC to be exactly the same in both templates.However, this is not the case.
In the
ContactInformations
template theNationalCode
has a Multiplicity qualifier ofZeroToOne
.In the
DigitalNameplate
template theNationalCode
has a Multiplicity qualifier ofOne
.Please fix or clarify the reason for this breaking inconsistency.
The text was updated successfully, but these errors were encountered: