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

Inconsistency between ContactInformation and DigitalNameplate #25

Open
shuebner opened this issue Mar 9, 2023 · 2 comments
Open

Inconsistency between ContactInformation and DigitalNameplate #25

shuebner opened this issue Mar 9, 2023 · 2 comments

Comments

@shuebner
Copy link

shuebner commented Mar 9, 2023

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.

@jh-isw
Copy link

jh-isw commented Apr 25, 2023

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)

@shuebner
Copy link
Author

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.

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

3 participants