Information technology - Business operational view - Part 8: Identification of privacy protection requirements as external constraints on business transactions (Adopted ISO/IEC 15944-8:2012, first edition, 2012-04-01)
This part of ISO/IEC 15944
This part of ISO/IEC 15944 is a BOV-related standard which addresses basic (or primitive) requirements of a privacy protection environment, as legal requirements represented through jurisdictional domains, on business transactions, and also integrates the requirements of the information technology and telecommunications environments. This part of ISO/IEC 15944 contains a methodology and tool for specifying common classes of external constraints through the construct of "jurisdictional domains". It meets the requirements set in ISO/IEC 15944-1 and ISO/IEC 15944-2 through the use of explicitly stated rules, templates, and Formal Description Techniques (FDTs)
This part of ISO/IEC 15944 focuses on the BOV aspects of a business transaction, and does not concern itself with the technical mechanisms needed to achieve the business requirements (the FSV aspects, including the specification of requirements of a Functional Services View (FSV) nature which include security techniques and services, communication protocols, etc.). The FSV includes any existing standard (or standards development of an FSV nature), which have been ratified by existing ISO, IEC, UN/ECE and/or ITU standards.
Internal behaviour of organizations (and public administration) Excluded from the scope of this part of ISO/IEC 15944 is the application of privacy protection requirements within an organization itself. The Open-edi Reference Model, considers these to be internal behaviours of an organization and thus not germane to business transactions (which focus on external behaviours pertaining to electronic data interchange among the autonomous parties to a business transaction). As such, excluded from the scope of this part of ISO/IEC 15944 are any: 1) internal use and management of recorded information pertaining to an identifiable organization Person an organization (or public administration) within an organization; and 2) implementation of internal information management controls, internal procedural controls or operational controls within an organization or public administration necessary for it to comply with applicable privacy requirements that may be required in observance of their lawful or contractual rights, duties and obligations as a legal entity in the jurisdictional domain(s) of which they are part. This should not be taken to mean that an organization could not adapt this part of ISO/IEC 15944 in order to model internal behaviour if they so wished, say when moving personal data within the organization.
"organization Person" From a public policy privacy protection requirements perspective, an "organization Person" is a "natural person" who acts on behalf of and makes commitments on behalf of the organization (or public administration) of which that natural person is an "organization part". But, as an "organization Person, they do not attract inherent rights to privacy. Privacy protection requirements which do apply to an organization Person are placed in an employee-employer context with associated contractual elements. In addition, some jurisdictional domains have privacy protection laws and regulations which apply specifically to employees of their public administrations. As such, from a business transaction perspective, it is an internal behaviour of an organization, as to who makes commitments on behalf of an organization or public administration. How and why organization Persons make decisions and commitments is not germane to the scope and purpose of this part of ISO/IEC 15944. {See further ISO/IEC 15944-1:2011, Clause 6.2 "Person and external constraints: Individual, organization, and public administration" as well as its Figure 17 "Illustration of commitment exchange versus information exchange for organization, organization part(s) and organization Person (s)"} 1.2.4 Overlap of and/or conflict among jurisdictional domains as sources of privacy protection requirements A business transaction requires an exchange of commitments among autonomous parties. Commitment is the making or accepting of a right, an obligation, liability or responsibility by a Person. In the context of a business transaction, the making of commitments pertains to the transfer of a good, service and/or right among the Persons involved. Consequently, it is not an uncommon occurrence, depending on the goal and nature of the business transaction, that the Persons (and parties associated) are in different jurisdictional domains, and that multiple sets of external constraints apply, and overlap will occur. It is also not an uncommon occurrence that there is overlap among such sets of external constraints and/or conflict among them. This is also the case with respect to laws and regulations of a privacy protection nature. Resolving issues of this nature is outside the scope of this part of ISO/IEC 15944. However, modelling business transaction as scenarios and scenario components as re-useable business objects may well serve as a useful methodology for identifying specific overlaps and conflicts (thereby serving as a tool for their harmonization, if only within the context of a specific transaction). The application of business semantic descriptive techniques to laws, regulations, etc., of jurisdictional domains and their modelling of such sets of external constraints as scenarios and scenario components is an essential step to their application in a systematic manner to (electronic) business transactions (and especially e-government, e-commerce, e-education, etc.). Open-edi business agreement descriptive techniques methodologies can serve as a tool in the harmonization and simplification of external constraints arising from jurisdictional domains. NOTE This part of ISO/IEC 15944 is based on the following assumptions: 1) the privacy protection requirements of the individual, as a buyer in a business transaction, are those of the jurisdictional domain in which the individual made the commitments associated with the instantiated business transaction; and 2) where the seller is in a jurisdictional domain other than that of the individual, as the buyer, this edition of ISO/IEC 15944 incorporates and supports the "OECD Guidelines on the Protection of Privacy and Transborder Data Flows of Personal Data".[See further below Clause 2.2] 1.2.5 Publicly available personal information Excluded from the scope of this part of ISO/IEC 15944 is "publicly available personal information" (PAPI). In a business transaction context, the seller does not collect personal information of this nature from the individual (particularly in the "planning phase" of the business transaction process). For example, the seller in advertising product to the market may: 1) publish personal information that is publicly available personal information, such as that found in telephone directories; 2) make use of any personal information declared to be of a public information by a regulation based on an law or regulation of the applicable jurisdictional domain; and, or, 3) include that which the individual itself chose to make public, (e.g., via one or more Internet based applications such as "Facebook"). In a privacy protection context, publicly available personal information is defined as follows: publicly available personal information (PAPI) personal information about an individual that the individual knowingly makes or permits to be made available to the public, or is legally obtained and accessed from: (
This part of ISO/IEC 15944 focuses on the essential and basic aspects of privacy protection requirements. The purpose of this Clause is to identify aspects not currently addressed. These will be addressed in either
It is also assumed the personal information under the control of organization "A" remains under its control and that a merger with or acquisition by organization "B" does not allow organization "B" to access and/or use personal information held by organization "A" without the express and informed consent of the individuals whose personal information is/was organization "A". 17) ICT and other service providers It is presumed that any ICT (or other) services provider which is under contract to provide ICT services to an organization or public administration (which has personal information under its control) shall not access or use such personal information processed as part of its services offering to that organization, unless it has a formal contractual arrangement to do so, in compliance with applicable privacy protection requirements. 18) data mining It is also presumed that an organization shall ensure that any data mining activities undertaken by itself (or via an agent or third party on its behalf) shall be in compliance with applicable privacy protection requirements, and not involve any secondary use or any other use of personal information for which the individual(s) concerned have not provided explicitly informed consent. 19) formal Conformance Statements Clause 13 below deals with conformance requirements at the most primitive level only. More detailed conformance statements with associated rules and procedures are required in implementation. It is also necessary to ensure that any such conformance statement, i.e., declaration by an organization or public administration is "verifiable". 20) linkages and similarities between privacy protection and consumer protection requirements Many of the external constraints pertaining to personal information of a privacy protection nature in a business transaction are similar to consumer protection requirements. {See further below Clause 7.2.2} It is anticipated that some or all of these requirements will be addressed in future editions of ISO/IEC 15944-8 or in companion standards or technical reports (including possible new parts of ISO/IEC 15944)
This part of ISO/IEC 15944 does not assume nor endorse any specific system environment, database management system, database design paradigm, system development methodology, data definition language, command language, system interface, user interface, syntax, computing platform, or any technology required for implementation, i.e., it is information technology neutral. At the same time, this part of ISO/IEC 15944 maximizes an IT-enabled approach to its implementation and maximizes semantic interoperability.
| SDO | CSA: Canadian Standards Association |
| Document Number | |
| Publication Date | Jan. 1, 2015 |
| Language | en - English |
| Page Count | |
| Revision Level | |
| Supercedes | |
| Committee |