independently repeatable groups are combined in xml example

[karel-debrabandere-bosa-fgov-be]

Hi,

in notice-types/24.json, the groups "GR-ContractingAuthority-Buyer" and "GR-Procedure-SProvider" both are independently repeatable. in the xml example, they are merged into the same xml node, though.
Should their first common ancestor ("GR-ContractingAuthority") be repeatable instead?

// notice-types/24.json

{
    "id" : "GR-ContractingAuthority",
    "contentType" : "group",
    "displayType" : "SECTION",
    "description" : "Contracting Authority",
    "_label" : "group|name|GR-ContractingAuthority",
    "content" : [{
      "id" : "GR-ContractingAuthority-Buyer",
      "contentType" : "group",
      "nodeId" : "ND-ContractingParty",
      "displayType" : "GROUP",
      "description" : "Contracting Party related Information (URL, Legal Type, Contracting Type, Activity, …)",
      "_label" : "group|name|ND-ContractingParty",
      "_repeatable" : true,
      "content" : [ ... ],
    }, {
      "id" : "GR-Procedure-SProvider",
      "contentType" : "group",
      "nodeId" : "ND-ServiceProviderParty",
      "displayType" : "GROUP",
      "description" : "Provided Service (code) and Provider (Reference to Organization)",
      "_label" : "group|name|ND-ServiceProviderParty",
      "_repeatable" : true,
      "content" : [ ... ],
    }, ... ],
  },

<!-- https://github.com/OP-TED/eForms-SDK/blob/develop/examples/notices/can_24_maximal.xml -->

	<cac:ContractingParty>
		<cbc:BuyerProfileURI>https://profile.example.com</cbc:BuyerProfileURI>
		<cac:ContractingPartyType>
			<cbc:PartyTypeCode listName="buyer-legal-type">body-pl</cbc:PartyTypeCode>
		</cac:ContractingPartyType>
		<cac:ContractingActivity>
			<cbc:ActivityTypeCode listName="authority-activity">econ-aff</cbc:ActivityTypeCode>
		</cac:ContractingActivity>
		<cac:Party>
			<cac:PartyIdentification>
				<cbc:ID schemeName="organization">ORG-0001</cbc:ID>
			</cac:PartyIdentification>

			<!-- How can we know to merge this node here?-->
			<cac:ServiceProviderParty>
				<cbc:ServiceTypeCode listName="organisation-role">ted-esen</cbc:ServiceTypeCode>
				<cac:Party>
					<cac:PartyIdentification>
						<cbc:ID schemeName="organization">ORG-0007</cbc:ID>
					</cac:PartyIdentification>
				</cac:Party>
			</cac:ServiceProviderParty>
		</cac:Party>
	</cac:ContractingParty>

[YvesJo]

Indeed, there is an issue in the Notice Type Definition. There may be multiple Buyers and each may have its own set of Service Providers. This will get fixed in a next release.