210.TOOP_BUSINESS_RULES.sch Maven / Gradle / Ivy
The newest version!
TOOP EDM Business Rules (specs Version 2.1.0)
Rule: The UUID MUST be created following the UUID Version 4 specification.
Please check , found: .
Rule: The message MUST have the specification identifier "toop-edm:v2.1".
In a QueryRequest, two or more concepts can not share the same ID.
In a QueryRequest, two or more concepts at the same level (with a common parent) can not share the same Qname.
When there are several LocalizedStrings, they all need to have a different language ID.
Each alternative LegaEntityID must have a different schemeID.
Each alternative PersonID must have a different schemeID.
The LEI code length should be 20.
A gender code must always be specified using the correct code list.
The country code must always be specified using the correct code list. Please check .
If the EIDAS code has the format "XX/YY/12345", the country code in the first part of the identifier must always be specified using the correct code list (found: ).
If the EIDAS code has the format "XX/YY/12345", the country code in the second part of the identifier must always be specified using the correct code list (found: ).
A mimetype code SHOULD 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.
An error origin code must always be specified using the correct code list.
A distribution format code must always be specified using the correct code list.
A query definition code must always be specified using the correct code list.
A currency type code must always be specified using the correct code list.
A language code must always be specified using the correct code list.
An error code must always be specified using the correct code list.
A standard industrial classification code should always be specified using the correct code list.
A protocol exception code must always be specified using the correct code list.
An identifier type code SHOULD always be specified using the correct code list.
© 2015 - 2025 Weber Informatics LLC | Privacy Policy