Skip to content

Conversation

@SeemoneB
Copy link

@SeemoneB SeemoneB commented Nov 8, 2022

No description provided.

@lussoluca
Copy link
Member

Is this related to #114 in any way?

@SeemoneB
Copy link
Author

SeemoneB commented Nov 9, 2022

Is this related to #114 in any way?

It is similar, but in this PR I managed the tag ContactPerson also for aggregator and aggregated data. One example below

<md:ContactPerson contactType="other" spid:entityType="spid:aggregator">
	<md:Extensions>
		<spid:VATNumber>vatNumber</spid:VATNumber>
		<spid:FiscalCode>fiscalcode</spid:FiscalCode>
		<spid:PublicServicesLightAggregator/>
	</md:Extensions>
	<md:Company>companyName</md:Company>
	<md:emailaddress>companyEmail</md:EmailAddress>
	<md:TelephoneNumber>companyPhone</md:TelephoneNumber>
</md:ContactPerson>
<md:ContactPerson contactType="other" spid:entityType="spid:aggregated">
	<md:Extensions>
		<spid:IPACode>__aggrsint</spid:IPACode>
		<spid:Public/>
	</md:Extensions>
	<md:Company>Organizzazione fittizia per il collaudo</md:Company>
</md:ContactPerson>

As you can see there is the possibility to insert more then one ContactPerson tag and you can define the empty tag like <spid:Public/> or <spid:PublicServicesLightAggregator/>. Required by Avviso nr 19

The next step would be manage the billing information. It can be done easily

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants