schematron.TOOP_BusinessRules_DataExchange-1.2.0.sch Maven / Gradle / Ivy
TOOP Business Rules (specs Version 1.2.0)
The message cannot contain a request both for Data Elements and Documents. Please split the message.
Rule: The UUID MUST be created following the UUID Version 4 specification.
Copies of a document must be identified with a different UUID.
Compulsory use of schemeAgencyID attribute.
A Request should not contain a DataRequestIdentifier, which is used in the response to link to the request.
A Request DocumentTypeIdentifier must be 'urn:eu:toop:ns:dataexchange-1p10::Request##urn:eu.toop.request.registeredorganization::1.10'.
A Request can not contain a DocumentResponse or any DataElementResponseValue element.
A Request should not contain information about the DataProvider.
Rule: A Toop data request MUST have the specification identifier "urn:eu:toop:ns:dataexchange-1p10::Request".
A Response must contain a DataRequestIdentifier.
UNCHECKED: Use the same value that was used in the corresponding Toop Request (path: Request/DocumentUniversalUniqueIdentifier).
A Response DocumentTypeIdentifier must be 'urn:eu:toop:ns:dataexchange-1p10::Response##urn:eu.toop.response.registeredorganization::1.10'.
The DocumentUniversalUniqueIdentifier cannot be identical to the DataRequestIdentifier (which is copied from the Request).
Rule: A Toop data response MUST have the specification identifier "urn:eu:toop:ns:dataexchange-1p10::Response".
Compulsory use of attributes schemeID "toop-doctypeid-qns" (instead of
Compulsory use of attributes schemeID "toop-procid-agreement" (instead of
Rule: An electronic address identifier MUST have a scheme identifier attribute.
Compulsory use of attributes schemeID "iso6523-actorid-upis" (instead of
Rule: The uniqueness identifier consists of:
1. The first part is the Nationality Code of the identifier. This is one of the ISO 3166-1 alpha-2 codes, followed by a slash ("/"))
2. The second part is the Nationality Code of the destination country or international organization. This is one of the ISO 3166-1 alpha-2 codes, followed by a slash ("/")
3. The third part a combination of readable characters. This uniquely identifies the identity asserted in the country of origin but does not necessarily reveal any discernible correspondence with the subject's actual identifier (for example, username, fiscal number etc).
Rule: The schemeAgencyID attribute is mandatory.
Rule: If the Concept Type Code is set on "Data Consumer" the cardinality of the ConceptDefinition element MUST be set to 1...1 (instead of
Rule: Use the value that is used in the element: DataSubject/NaturalPerson/PersonIdentifier.
The LEI code length should be 20 (instead of
The provided value should be a boolean: true or false.
Rule: The currencyID attribute is mandatory (e.g. "EUR").
Rule: do not format the percentage "%" symbol with the response value, just provide a float value (e.g. 0.4).
The DataProviderID contained in an Error must match the ID of a DataProvider in this message.
When more than one ErrorText is present, they all need to have a different language ID.
Rule: At maximum one DataProvider must be present in a Response.
Rule: The DataProvider in a Response is mandatory if there is no fatal error.
The country code must always be specified using the correct code list.
The country code in the first part of the identifier must always be specified using the correct code list (found:
The country code in the second part of the identifier must always be specified using the correct code list (found:
A subject type code must always be specified using the correct code list.
A gender code must always be specified using the correct code list.
A concept type code must always be specified using the correct code list.
A currency type code must always be specified using the correct code list (found:
A standard industrial classification code must always be specified using the correct code list.
An error code must always be specified using the correct code list.
An error code must always be specified using the correct code list.
A document type code must always be specified using the correct code list.
A mimetype code must always be specified using the correct code list.
A process identifier must always be specified using the correct code list.
A schemeAgencyID must always be specified using the correct code list (found:
An error origin code must always be specified using the correct code list.
An error category code must always be specified using the correct code list.
An error severity code must always be specified using the correct code list.
An error code must always be specified using the correct code list.