BS-8766-2004.pdf

BRITISH STANDARD BS 8766:2004 Incorporating Corrigendum No. 1 Names and identifiers of individuals and groups Data structure for interoperability Specification ICS 03.020; 35.040 ? Licensed Copy: London South Bank University, London South Bank University, Fri Dec 08 00:48:31 GMT+00:00 2006, Uncontrolled Copy, (c) BSI BS 8766:2004 This British Standard was published under the authority of the Standards Policy and Strategy Committee on 19 October 2004 © BSI 23 May 2005 The following BSI references relate to the work on this British Standard: Committee reference IST/36 Draft for comment 03/653400 DC ISBN 0 580 44572 0 Committees responsible for this British Standard The preparation of this British Standard was entrusted to Technical Committee IST/36, Geographic information, upon which the following bodies were represented: Association of Geographic Information Babtie Group Ltd. British Geological Survey Defence Estates Defence Geographic and Imagery Intelligence Agency Geobase Consultants IDEA Infoshare ISLINKUP Natural Environment Research Council Office of the e-Envoy Ordnance Survey Ordnance Survey of Northern Ireland Royal Institution of Chartered Surveyors University of Sheffield Amendments issued since publication Amd. No.DateComments 15620 Corrigendum No. 1 23 May 2005Correction to Figure B.1 Licensed Copy: London South Bank University, London South Bank University, Fri Dec 08 00:48:31 GMT+00:00 2006, Uncontrolled Copy, (c) BSI BS 8766:2004 © BSI 23 May 2005 i Contents Page Committees responsibleInside front cover Forewordii 1Scope1 2Normative references1 3Terms and definitions1 4Details of classes of objects2 5Data transfer7 Annex A (informative) Example of information that can be recorded for a person8 Annex B (informative) UML model9 Annex C (informative) Example data for the UML model11 Annex D (informative) Tests for checking conformance12 Annex E (informative) Example XML schema14 Annex F (informative) Example f transfer data in XML18 Bibliography19 Figure B.1 UML model for names10 Figure B.2 UML model for transfer metadata11 Table 1 Attributes of person2 Table 2 Attributes of person name3 Table 3 Attributes of person identifier4 Table 4 Attributes of group5 Table 5 Attributes of group name5 Table 6 Attributes of group identifier6 Table 7 Transfer metadata7 Table C.1 Person11 Table C.2 Group12 Licensed Copy: London South Bank University, London South Bank University, Fri Dec 08 00:48:31 GMT+00:00 2006, Uncontrolled Copy, (c) BSI BS 8766:2004 ii© BSI 23 May 2005 Foreword This British Standard is published under the authority of Technical Committee, IST/36. The Data Protection Act, 1998 1 should be taken into account when storing any data about people. This publication does not purport to include all the necessary provisions of a contract. Users are responsible for its correct application. Compliance with a British Standard does not of itself confer immunity from legal obligations. Summary of pages This document comprises a front cover, an inside front cover, pages i and ii, pages 1 to 19 and a back cover. The BSI copyright notice displayed in this document indicates when the document was last issued. Licensed Copy: London South Bank University, London South Bank University, Fri Dec 08 00:48:31 GMT+00:00 2006, Uncontrolled Copy, (c) BSI BS 8766:2004 © BSI 23 May 2005 1 1 Scope This British Standard specifies a data structure for recording names and identifiers of individuals and groups for the purposes of interoperability between information systems. The data structure is presented as a data model in Unified Modelling Language (UML). The model is formed around six basic classes of objects: person (see 4.1); person name (see 4.2); person identifier (see 4.3); group (see 4.4); group name (see 4.5) and group identifier (see 4.6). This British Standard defines the attributes of these classes of objects in structured English and in tabular format, and specifies the name of the attribute, the UML form of the attribute name, the definition of the attribute, whether the attribute is mandatory or optional, whether there can one be a single value of the attribute, or whether multiple values are allowed and the allowable values. This British Standard also presents the attributes as an example XML schema (see Annex E). This British Standard does not define how individual and group names are created. It does not prescribe any personal or group identifiers but does allow the use of existing identifiers such as National Insurance Number or customer reference number. This British Standard is aimed at information specialists, systems developers and users who have a primary interest or involvement in the interoperability of information systems that use names and identifiers of individuals and groups. 2 Normative references The following referenced documents are indispensable for the application of this document. For dated references, only the edition cited applies. For undated references, the latest edition of the referenced document (including any amendments) applies. ISO 8601, Data elements and interchange formats Information interchange Representation of dates and times. 3 Terms and definitions For purposes of this British Standard, the following terms and definitions apply. 3.1 group (GROUP) set of people identifiable by some criteria for example a family or household, or formally constituted body for example a company or club NOTEThis corresponds to the object class GROUP in the UML model. 3.2 group identifier (GROUPID) external identifier of the group, for example the company registration number NOTEThis corresponds to the object class GROUPID in the UML model. 3.3 group name (GROUPNAME) name used to identify a group NOTEThis corresponds to the object class GROUPNAME in the UML model. 3.4 person (PERSON) individual human being NOTEThis corresponds to the object class PERSON in the UML model. Examples of attributes that can be used for civil and registration purposes are given in Annex A. Licensed Copy: London South Bank University, London South Bank University, Fri Dec 08 00:48:31 GMT+00:00 2006, Uncontrolled Copy, (c) BSI BS 8766:2004 2© BSI 23 May 2005 3.5 person identifier (PERSONID) external identifier of the person, for example the National Insurance Number or customer record number NOTEThis corresponds to the object class PERSONID in the UML model. 3.6 person name (PERSONNAME) name used to identify a person NOTEThis corresponds to the object class PERSONNAME in the UML model. 4 Details of classes of objects 4.1 Person (PERSON) 4.1.1 Structure A person shall have attributes as defined in 4.1.2 and 4.1.3 and in accordance with Table 1. NOTE 1A UML model is shown in Annex B, which also shows the associations with the other classes. Examples are given in Annex C. NOTE 2As appropriate, additional attributes can be added by the user in the context of a particular application. NOTE 3Tests for checking conformance for PERSON are given in Annex D (see D.1). NOTE 4A person can also have a relationship to a group (membership), where a person can be a member of one or more groups. Table 1 Attributes of person All dates shall be recorded in accordance with ISO 8601, consistently either in the basic format (YYYYMMDD) or in the extended format (YYYY-MM-DD). 4.1.2 Mandatory attributes A person shall have the following mandatory (M) attributes: a) person name: a name used to identify the person; b) person identifier: an alphanumeric code used to identify the person. 4.1.3 Optional attributes Where appropriate, a person shall also have one or more of the following optional (O) attributes: a) address: an address used to locate the person; b) place of birth: where the person was born; c) date of birth: when the person was born; d) gender: whether the person is male or female. NameUML nameDescriptionObligationMaximum occurrences Domain person name PersonNameName of the personMaNPERSONNAME person identifier PersonIDIdentifier of the personMaNPERSONID addressAddressAddress of the personObNADDRESS (see Note) place of birth PlaceOfBirthPersons place of birthOb1Character date of birth DateOfBirthPersons date of birthOb1Date genderGenderPersons current gender Ob1Character NOTE The class ADDRESS is a structured address, conforming to a recognized standard, for example, BS 7666-3:2000, or the Royal Mail postal address. a Mandatory attributes. b Optional attributes. Licensed Copy: London South Bank University, London South Bank University, Fri Dec 08 00:48:31 GMT+00:00 2006, Uncontrolled Copy, (c) BSI BS 8766:2004 © BSI 23 May 2005 3 4.2 Person name (PERSONNAME) 4.2.1 Structure A person name shall have attributes as defined in 4.2.2 and 4.2.3 and in accordance with Table 2. NOTE 1A UML model is shown in Annex B, which also shows the associations with the other classes. Examples are given in Annex C. NOTE 2As appropriate, additional attributes can be added by the user in the context of a particular application. NOTE 3Tests for checking conformance for PERSONNAME are given in Annex D (see D.2). Punctuation such as hyphens shall not be included in any attribute, unless it is a stated component of the attribute (e.g. “ORourke”). Where a person has only one name, for example “Prince”, it shall be used for the family name. Initials shall be recorded with a space between each character. Each given name shall be a separate entry, which is recorded in sequence. Table 2 Attributes of person name All dates shall be recorded in accordance with ISO 8601, consistently either in the basic format (YYYYMMDD) or in the extended format (YYYY-MM-DD). 4.2.2 Mandatory attributes A person name shall have the following mandatory (M) attributes: a) person name type: the type of name, for example name given at birth, or preferred name; b) family name: that part of a persons name which is used to describe family, clan, tribal group or marital association; c) start date: the date at which the name started to be used. NameUML nameDescriptionObligationMaximum occurrences Domain person name type PersonNameTypeType of nameMa1Character titleTitleTitle of personObNCharacter initialsInitialsSet of initials for the persons given names Ob1Character family name FamilyNameFamily name of person Ma1Character given names GivenNameForename or personal name ObNCharacter (Note 1) suffixSuffixSuffix to name ObNCharacter languageLanguageLanguage in which name was given Ob1Character (Note 2) start dateStartDateDate at which name started to be used Ma1Date end dateEndDateDate at which name ceased to be current Ob1Date NOTE 1Each given name is a separate entry, recorded in sequence, The sequence order is significant. Thus “Edward”, “George” is a different name from “George”, “Edward”. NOTE 2This might be a code, as defined in BS ISO 639-2:1998. Where no language is specified, English (UK) is assumed. a Mandatory attributes. b Optional attributes. Licensed Copy: London South Bank University, London South Bank University, Fri Dec 08 00:48:31 GMT+00:00 2006, Uncontrolled Copy, (c) BSI BS 8766:2004 4© BSI 23 May 2005 4.2.3 Optional attributes Where appropriate, a person name shall also have one or more of the following optional (O) attributes: a) title: the form of address used to precede a persons name, for example Mr, Mrs, Ms, Dr, Rev, Sir, Lady, Lord, Dame; b) initials: the set of initials for a persons given names; NOTE The initials might not correspond to given names. c) given names: any forename or personal name of a person; d) suffix: a textual suffix that might be added to the end of a persons name, for example OBE, MBE, BSc, JP, GM; e) language: the language in which the name was given (which defaults to English); f) end date: the date at which the name ceased to be current (where appropriate). 4.3 Person identifier (PERSONID) 4.3.1 Structure A person identifier shall have attributes as defined in 4.3.2 and 4.3.3 and in accordance with Table 3. NOTE 1A UML model is shown in Annex B, which also shows the associations with the other classes. Examples are given in Annex C. NOTE 2As appropriate, additional attributes can be added by the user in the context of a particular application. NOTE 3Tests for checking conformance for a PERSONID are given in Annex D (see D.3). Table 3 Attributes of person identifier All dates shall be recorded in accordance with ISO 8601, consistently either in the basic format (YYYYMMDD) or in the extended format (YYYY-MM-DD). 4.3.2 Mandatory attributes A person identifier shall have the following mandatory (M) attributes: a) identifier: externally allocated reference for the person in the form of an alphanumeric sequence, for example “MY530175A”; b) person identifier descriptor: description of the identifier, for example “National Insurance Number”; c) start date: the date at which the identifier was assigned or became valid. 4.3.3 Optional attribute Where appropriate, a person identifier shall also have an end date: the date at which the person identifier ceased to be current. NameUML nameDescriptionObligationMaximum occurrences Domain identifierIdentifierExternally allocated reference for the person Ma1Character person identifier descriptor PersonIDDescriptor Description of identifier Ma1Character start dateStartDateDate at which identifier was assigned or became valid Ma1Date end dateEndDateDate at which person identifier ceased to be current Ob1Date a Mandatory attributes. b Optional attributes. Licensed Copy: London South Bank University, London South Bank University, Fri Dec 08 00:48:31 GMT+00:00 2006, Uncontrolled Copy, (c) BSI BS 8766:2004 © BSI 23 May 2005 5 4.4 Group (GROUP) 4.4.1 Structure A group shall have attributes as defined in 4.4.2 and 4.4.3 and in accordance with Table 4. NOTE 1A UML model is shown in Annex B, which also shows the associations with the other classes. Examples are given in Annex C. NOTE 2As appropriate, additional attributes can be added by the user in the context of a particular application. NOTE 3Tests for checking conformance for a GROUP are given in Annex D (see D.4). NOTE 4A group can also have a relationship to group (membership) where a group can have one or more person members. Table 4 Attributes of group 4.4.2 Mandatory attributes A group shall have the following attributes the following mandatory (M) attributes: a) group name: a name used for the group, for example “The Association for Geographic Information”, “The Royle Family”; b) group identifier: an identifier for the group, for example “registered name of a company”. 4.4.3 Optional attributes Where appropriate, a group shall also have an address: the address for the group. 4.5 Group name (GROUPNAME) 4.5.1 Structure A group name shall have attributes as defined in 4.5.2 and 4.5.3 and in accordance with Table 5. NOTE 1A UML model is shown in Annex B, which also shows the associations with the other classes. Examp