Participant Business unique identifier Must be unique. http://<hash over Identifier of the Participant. May not exceed 50 characters. BUSDOX is flexible with regard to the use of any one of a May only contain Represents a business wide range of schemes for the format of participant characters. level endpoint key that identifiers, represented by the schemeID. However, uniquely identifies an when using this form of http Web address, which is Participant identifier must be entity in the network. resolved through the DNS system, the format of the trimmed. Examples of identifiers are recipientID and the schemeID is constrained by the company registration and requirements of the DNS system. This means that both VAT numbers, DUNS the recipientID and the schemeID must be strings which If the scheme refers to the numbers, GLN numbers, use the ASCII alphanumeric characters only and which (default) PEPPOL participant email addresses, etc… identifier scheme have to start with an alphabetic character. and the participant identifier is not a wildcard ('*'), then the issuing BUSDOX allocates schemeIDs to conform to this agency specified in the requirement. However, there is no guarantee that the (as its ParticipantIdentifier participant IDs will conform to this requirement for any leading part before ':') must be given scheme (remembering that in many cases the valid.. participant ID scheme will be a pre-existing scheme with its own format rules that might violate the requirements of a DNS name). Refer to §2.2.1 "Operation" for more – detail on the calculation of this identifier.
Participant Identifier Business unique identifier of the Participant. Represents a business level endpoint key that uniquely identifies an entity in the network. Examples of identifiers are company registration and VAT numbers, DUNS numbers, GLN numbers, email addresses, etc… http://<hash over BUSDOX is flexible with regard to the use of any one of a wide range of schemes for the format of participant identifiers, represented by the schemeID. However, when using this form of http Web address, which is resolved through the DNS system, the format of the recipientID and the schemeID is constrained by the requirements of the DNS system. This means that both the recipientID and the schemeID must be strings which use the ASCII alphanumeric characters only and which have to start with an alphabetic character. BUSDOX allocates schemeIDs to conform to this requirement. However, there is no guarantee that the participant IDs will conform to this requirement for any given scheme (remembering that in many cases the participant ID scheme will be a pre-existing scheme with its own format rules that might violate the requirements of a DNS name). Refer to §2.2.1 – "Operation" for more detail on the calculation of this identifier. Must be unique. May not exceed 50 characters. May only contain characters. Participant identifier must be trimmed. If the scheme refers to the (default) PEPPOL participant identifier scheme and the participant identifier is not a wildcard ('*'), then the issuing agency specified in the ParticipantIdentifier (as its leading part before ':') must be valid..
Interface%20Control%20Document%20for%20the%20BDMSL%20-%20v0.4g.docx