Test
root_element_qnameW - 1
Location
/
Description
The validation process has only been applied on the urn:oasis:names:tc:DSML:2:0:core:batchRequest element. Line numbers and XPath in this report might differ from the actual number in the submitted file
Test
constraint_hpd_common_uidSyntaxR - 1
Location
/batchRequest/addRequest[0]/attr[0]
Description
uid attribute SHALL be formatted using the RDN Format as defined by ISO21091 section 9.2: IssuingAuhorityName:ID (see Tables 3.58.4.1.2.2.2-1: Individual Provider Mapping and 3.58.4.1.2.2.3-1: Organizational Provider Mapping)[ Assertion... ]
Test
constraint_hpd_common_uidValueCardR - 2
Location
/batchRequest/addRequest[0]/attr[0]
Description
uid attribute SHALL be single valued (see Tables 3.58.4.1.2.2.2-1: Individual Provider Mapping and 3.58.4.1.2.2.3-1: Organizational Provider Mapping)[ Assertion... ]
Test
constraint_hpd_common_HcIdentifierValueR - 3
Location
/batchRequest/addRequest[0]/attr[4]
Description
HcIdentifier SHALL be formatted as defined by ISO 21091 (IssuingAuthority:Type:ID:Status) (see Tables 3.58.4.1.2.2.2-1: Individual Provider Mapping, 3.58.4.1.2.2.3-1: Organizational Provider Mapping)[ Assertion... ]
Test
constraint_hpd_common_HcIdentifierValue2R - 4
Location
/batchRequest/addRequest[0]/attr[4]
Description
HcIdentifier Status SHALL be from Status Code Category Values ( see Table 3.58.4.1.2.3-1)[ Assertion... ]
Test
constraint_hpd_common_hpdProviderStatusValueCardR - 5
Location
/batchRequest/addRequest[0]/attr[5]
Description
hpdProviderStatus attribute SHALL be single valued (see Table 3.58.4.1.2.2.2-1: Individual Provider Mapping)[ Assertion... ]
Test
constraint_hpd_common_objectClassValueR - 6
Location
/batchRequest/addRequest[0]/attr[6]
Description
objectClass attribute SHALL be present in every entry, one of the values is either top or alias (see RFC 2256 section 5.1 objectClass)[ Assertion... ]
Test
constraint_hpd_common_objectClassValueCardR - 7
Location
/batchRequest/addRequest[0]/attr[6]
Description
The objectClass attribute is present in every entry, with at least two values. (see RFC 2256 section 5.1 objectClass)[ Assertion... ]
Test
constraint_hpd_common_objectClassValueR - 8
Location
/batchRequest/addRequest[1]/attr[2]
Description
objectClass attribute SHALL be present in every entry, one of the values is either top or alias (see RFC 2256 section 5.1 objectClass)[ Assertion... ]
Test
constraint_hpd_common_objectClassValueCardR - 9
Location
/batchRequest/addRequest[1]/attr[2]
Description
The objectClass attribute is present in every entry, with at least two values. (see RFC 2256 section 5.1 objectClass)[ Assertion... ]
Test
ch_hpd_004_TypeR - 10
Location
/batchRequest/addRequest[0]
Description
For HPD Organizational provider the parameter Org Type (businessCategory) is required[ Assertion... ]
Test
ch_hpd_013_IdentifierSyntaxR - 11
Location
/batchRequest/addRequest[0]
Description
At least one value for hcidentifier must start with RefData:OID: .[ Assertion... ]
Test
ch_hpd_014_Metadata_attributesR - 12
Location
/batchRequest/addRequest[0]
Description
Value of attributes HCRegulatedOrganization.HcSpecialisation and HCRegulatedOrganization.businessCategory must be provided in the following format : BAG:<CodeSystem>:<Code>[:<DisplayName>][ Assertion... ]
Test
ch_hpd_015_Organization_known_namesR - 13
Location
/batchRequest/addRequest[0]
Description
For HPD Organizational provider the parameter Organization known names (O) is required[ Assertion... ]
Test
ch_hpd_012_ownerR - 14
Location
/batchRequest/addRequest[1]
Description
When the addRequest describes a relationship, the owner attribute is required[ Assertion... ]
Test
constraint_hpd_feedRequestAllowedElementsR - 15
Location
/batchRequest
Description
A Provider Information Feed Request only supports the following elements: addRequest, delRequest, modDNRequest and modifyRequest[ Assertion... ]
Test
constraint_hpd_addRequestHCRegulaedOrganization_HcRegisteredNameRequiredR - 16
Location
/batchRequest/addRequest[0]
Description
When the addRequest describes an Organizational Provider, the HcRegisteredName attribute is required (see 3.59.1 and Table 3.58.4.1.2.2.3-1: Organizational Provider Mapping)[ Assertion... ]
Test
constraint_hpd_addRequestHCRegulatedOrganization_HcIdentifierR - 17
Location
/batchRequest/addRequest[0]
Description
When the addRequest describes an Organizational Provider, the HcIdentifier attribute is required (see 3.59.1 and Table 3.58.4.1.2.2.3-1: Organizational Provider Mapping)[ Assertion... ]
Test
constraint_hpd_addRequestHCRegulatedOrganization_oRequiredR - 18
Location
/batchRequest/addRequest[0]
Description
HCRegulatedOrganization SHALL have an o attribute (RFC 2556 section 7.5 describing Organization object class)[ Assertion... ]
Test
constraint_hpd_addRequestHCRegulatedOrganization_uidRequiredR - 19
Location
/batchRequest/addRequest[0]
Description
When the addRequest describes an Organizational Provider, the uid attribute is required (see 3.59.1 and Table 3.58.4.1.2.2.3-1: Organizational Provider Mapping)[ Assertion... ]
Test
constraint_hpd_addRequest_createTimestampCardR - 20
Location
/batchRequest/addRequest[0]
Description
createTimestamp is an operation attribute that LDAP directory server maintains to capture the time when an entry was created[ Assertion... ]
Test
constraint_hpd_addRequest_dnSyntaxR - 21
Location
/batchRequest/addRequest[0]
Description
dn attribute SHALL be formatted as a Distinguish name string.[ Assertion... ]
Test
constraint_hpd_addRequest_dnValidOuR - 22
Location
/batchRequest/addRequest[0]
Description
Nodes that are subordinates to dc=HPD are ou=HCProfessional, ou=HCRegulatedOrganization,ou=HPDCredential and ou=Relationship (see section 3.58.4.1.2.1 HPD Schema Structure)[ Assertion... ]
Test
constraint_hpd_addRequest_modifyTimestampCardR - 23
Location
/batchRequest/addRequest[0]
Description
modifyTimestamp is an operation attribute that LDAP directory server maintains to capture the time when an entry was modified[ Assertion... ]
Test
constraint_hpd_addRequest_objectClassRequiredR - 24
Location
/batchRequest/addRequest[0]
Description
objectClass attribute is required in each entry (see RFC 2256 section 7.1 top)[ Assertion... ]
Test
constraint_hpd_addRequestRelationship_cnRequiredR - 25
Location
/batchRequest/addRequest[1]
Description
When the addRequest describes a relationship, the cn attribute is required (see ISO 21021:2013, section B.4 GroupOfNames)[ Assertion... ]
Test
constraint_hpd_addRequestRelationship_groupOfNamesObjectClassR - 26
Location
/batchRequest/addRequest[1]
Description
Relationships in HPD are represented by LDAP objects using the groupOfNames class (see section 3.58.4.1.2.2.4 Relationships)[ Assertion... ]
Test
constraint_hpd_addRequestRelationship_ownerSVR - 27
Location
/batchRequest/addRequest[1]
Description
When the addRequest describes a relationship, the owner attribute is singled-valued (see section 3.58.4.1.2.2.4 Relationships)[ Assertion... ]
Test
constraint_hpd_addRequest_createTimestampCardR - 28
Location
/batchRequest/addRequest[1]
Description
createTimestamp is an operation attribute that LDAP directory server maintains to capture the time when an entry was created[ Assertion... ]
Test
constraint_hpd_addRequest_dnSyntaxR - 29
Location
/batchRequest/addRequest[1]
Description
dn attribute SHALL be formatted as a Distinguish name string.[ Assertion... ]
Test
constraint_hpd_addRequest_dnValidOuR - 30
Location
/batchRequest/addRequest[1]
Description
Nodes that are subordinates to dc=HPD are ou=HCProfessional, ou=HCRegulatedOrganization,ou=HPDCredential and ou=Relationship (see section 3.58.4.1.2.1 HPD Schema Structure)[ Assertion... ]
Test
constraint_hpd_addRequest_modifyTimestampCardR - 31
Location
/batchRequest/addRequest[1]
Description
modifyTimestamp is an operation attribute that LDAP directory server maintains to capture the time when an entry was modified[ Assertion... ]
Test
constraint_hpd_addRequest_objectClassRequiredR - 32
Location
/batchRequest/addRequest[1]
Description
objectClass attribute is required in each entry (see RFC 2256 section 7.1 top)[ Assertion... ]