DTr1 PN.CA

Revision as of 14:57, 5 December 2017 by ADbot (talk | contribs) (Automated ADBot page content)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)

PN.CA Person Name - Flavor Canadian Person Name

Datatype Release 1 Realm
PN.CA Flag ca.svg CA

PN.CA Person Names (BC constraints)

Names are encoded as a sequence of Name Parts such as given name, family name, prefixes and suffixes. Constraints for names are consistent with the requirements set out in the Pan Canadian Data Type Specification for the data type flavor PN.BASIC, with some additional constraints described below.

Registered Attributes and Child Elements

@Attribute / Element Cardinality Datatype
@use   optional   set_cs
@nullFlavor   optional   cs
delimiter  0 .. *  ENXP
family  0 .. *  ENXP
given  0 .. *  ENXP
prefix  0 .. *  ENXP
suffix  0 .. *  ENXP

Core Schematron Rules (CSR)

The following rules are defined in the base core schematrons (Alert.png errors, Warning.png warnings, Info.png infos).

Check-circle.svg Rule ID: PN.CA

Extends Rule(s): PN

Constraints

  • Alert.png dtr1-1-PN.CA: given/@qualifier property is required
  • Alert.png dtr1-2-PN.CA: at present, the only value for name/given/@qualifier is IN (initial), indicating that the name part is just an initial
  • Alert.png dtr1-3-PN.CA: supported name parts (part types) are family, given, prefix, suffix
  • Alert.png dtr1-4-PN.CA: Exactly one [1..1] name/family part SHALL be present
  • Alert.png dtr1-5-PN.CA: One or more [1..*] name/given parts SHALL be present
  • Alert.png dtr1-6-PN.CA: Zero or 1 [0..1] name/prefix name parts may be provided
  • Alert.png dtr1-7-PN.CA: Zero or 1 [0..1] name/suffix name parts may be provided
  • Alert.png dtr1-8-PN.CA: At most seven name parts may be present; since a family name part and at least one given name are mandatory, the cardinality for name parts is [2..7]
  • Alert.png dtr1-9-AD.CA: @use must be drawn from 'L', 'P', 'ASGN', 'C', 'HC'