1.1<\/b> Statement of scope<\/p>\n
This part of ISO\/IEC 15944:<\/p>\n
provides method(s) for identifying, in Open-edi modelling technologies and development of scenarios, the additional requirements in Business Operational View (BOV) specifications for identifying the additional external constraints to be applied to recorded information in business transactions relating to personal information of an individual, as required by legal and regulatory requirements of applicable jurisdictional domains having governance over the personal information exchanged among parties to a business transaction;<\/p>\n<\/li>\n
integrates existing normative elements in support of privacy and data protection requirements as are already identified in the current editions of ISO\/IEC 14662 and ISO\/IEC 15944-1, ISO\/IEC 15944-2, ISO\/IEC 15944-4, and ISO\/IEC 15944-5 which apply to information concerning identifiable living individuals as buyers17<\/sup> in a business transaction or whose personal information is used in the transaction;<\/p>\n<\/li>\n provides overarching operational \u2018best practice\u2019 statements for associated (and not necessarily automated) processes, procedures, practices and governance requirements that must act in support of implementing and enforcing technical mechanisms needed to support privacy\/data protection requirements necessary for the implementation in Open-edi transaction environments;<\/p>\n<\/li>\n identifies and provides a sample scenario and implementation (use case) for one or more use cases of privacy\/data protection in business transactions; and,<\/p>\n<\/li>\n provides guidelines on the need for procedural mechanisms in the event that mandatory disclosure rules of transactional information must be implemented.<\/p>\n<\/li>\n<\/ul>\n 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.<\/p>\n 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).<\/p>\n 1.2<\/b> Exclusions<\/p>\n 1.2.1<\/b> Functional Services View (FSV)<\/p>\n 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.<\/p>\n 1.2.2<\/b> Internal behaviour of organizations (and public administration)<\/p>\n Excluded from the scope of this part of ISO\/IEC 15944 is the application of privacy protection requirements within<\/span> 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:<\/p>\n internal use and management of recorded information pertaining to an identifiable organization Person an organization (or public administration) within an organization; and,<\/p>\n<\/li>\n 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.<\/p>\n<\/li>\n<\/ol>\n 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.<\/p>\n 1.2.3<\/b> \u201corganization Person\u201d<\/p>\n From a public policy privacy protection requirements perspective, an \u201corganization Person\u201d is a \u201cnatural person\u201d who acts on behalf of and makes commitments on behalf of the organization (or public administration) of which that natural person is an \u201corganization part\u201d. But, as an \u201corganization 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.<\/p>\n 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 \u201cPerson and external constraints: Individual, organization, and public administration\u201d<\/i> as well as its Figure 17 \u201cIllustration of commitment exchange versus information exchange for organization, organization part(s) and organization Person(s)<\/i>\u201d}<\/p>\n 1.2.4<\/b> Overlap of and\/or conflict among jurisdictional domains as sources of privacy protection requirements<\/p>\n 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.<\/p>\n 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.<\/p>\n 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).<\/p>\n 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.).<\/p>\n Open-edi business agreement descriptive techniques methodologies can serve as a tool in the harmonization and simplification of external constraints arising from jurisdictional domains.<\/p>\n NOTE This part of ISO\/IEC 15944 is based on the following assumptions:<\/p>\n 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,<\/p>\n<\/li>\n 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 \u201cOECD Guidelines on the Protection of Privacy and Transborder Data Flows of Personal Data\u201d.<\/i>[See further below Clause 2.2]<\/p>\n<\/li>\n<\/ol>\n<\/blockquote>\n 1.2.5<\/b> Publicly available personal information<\/p>\n Excluded from the scope of this part of ISO\/IEC 15944 is \u201cpublicly available personal information\u201d (PAPI). In a business transaction context, the seller does not collect personal information of this nature from the individual (particularly in the \u201cplanning phase\u201d of the business transaction process).<\/p>\n For example, the seller in advertising product to the market may:<\/p>\n publish personal information that is publicly available personal information, such as that found in telephone directories;<\/p>\n<\/li>\n 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,<\/p>\n<\/li>\n include that which the individual itself chose to make public, (e.g., via one or more Internet based applications such as \u201cFacebook\u201d).<\/p>\n<\/li>\n<\/ol>\n In a privacy protection context, publicly available personal information is defined as follows:<\/p>\n publicly available personal information (PAPI)<\/b><\/p>\n personal information<\/b> about an individual<\/b> that the individual<\/b> knowingly makes or permits to be made available to the public, or is legally obtained and accessed from: (a) government records that are available to the public; or, (b) information required by law to be made available to the public<\/p>\n EXAMPLE 1 Examples of personal information which an individual knowingly makes or permits to be made available include public telephone directories, advertisements in newspapers, published materials, postings of a similar nature on the internet, etc.<\/p>\n<\/blockquote>\n EXAMPLE 2 Examples of government records that are publicly available include registers of individuals who are entitled to vote, buy or sell a property, or any other personal information that a jurisdictional domain requires to be publicly available, etc.<\/p>\n<\/blockquote>\n Further, determining whether or not personal information is of a \u201cPAPI\u201d nature is also excluded from the scope of this part of ISO\/IEC 15944.<\/p>\n 1.3<\/b> Aspects currently not addressed<\/p>\n 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:<\/p>\n an Amendment to this part of ISO\/IEC 15944,<\/p>\n<\/li>\n new editions of this part of ISO\/IEC 15944,<\/p>\n<\/li>\n through a new part of ISO\/IEC 15944,<\/p>\n<\/li>\n in a new edition of an existing part of ISO\/IEC 15944 (as may be applicable),<\/p>\n<\/li>\n through a new edition of an existing standard of ISO\/IEC JTC1, or another existing ISO\/IEC JTC1\/SC, or ISO, IEC or ITU; and\/or,<\/p>\n<\/li>\n new standard(s) by any of the above noted committees.<\/p>\n<\/li>\n<\/ol>\n ISO\/IEC 15944-8 also does yet address the following requirements:<\/p>\n differences in equality in the use of official languages by an individual, in being informed and exercising privacy protection rights within a jurisdictional domain18<\/sup>;<\/p>\n<\/li>\n interworking between privacy protection and consumer protection requirements as two sets of external constraints applicable to an individual as a buyer in a business transaction;<\/p>\n<\/li>\n identification and registration of schemas involving the control and management of legally recognized names (LRNs) as personas and associated unique identifiers for the unambiguous identification of an individual and\/or the role qualification of an individual in a specific context;<\/p>\n<\/li>\n more detailed information management and audit requirements pertaining to ensuring privacy protection of personal information that should be enacted by and among organizations and public administrations as parties to a business transaction;<\/p>\n<\/li>\n more detailed rules and associated text pertaining to the BOV perspective with respect to transborder data flows of personal information;<\/p>\n<\/li>\n inter-operation between jurisdictional domains where they do not possess defined equivalents to their protection requirements (interoperability) or where protection requirements simply are different;<\/p>\n<\/li>\n instances in which privacy protection requirements continue to apply to the personal information of an individual after his\/her death;<\/p>\n In addition, from a business transaction perspective, there may be some continuity in privacy protection requirements, (e.g., those pertaining to temporal aspects of post-actualization aspects of an instantiated business transaction, (e.g., health care matters, warranties on products, service contracts, rights (including IP), etc.). Instantiated business transactions may require personal information to be retained and continue to be protected following the death of the individual.<\/p>\n NOTE 1 This may also include a settlement of wills, probate, investments, etc., pertaining to that individual once proved deceased.<\/p>\n<\/blockquote>\n NOTE 2 Tax information filed has 4-6 years record retention requirements in most jurisdictional domains. In some jurisdictional domains, tax matters are confidential and in others they are public. The status of personal information may change as a result of litigation and public hearings.<\/p>\n<\/blockquote>\n NOTE 3 Instantiated business transactions may require personal information to be retained and continue to be protected following the death of an individual, (e.g., many credit card agreements exist after the death of the credit card holder).<\/p>\n<\/blockquote>\n NOTE 4 One may need to have an added Clause on privacy protection of personal information on individuals consequent upon the death of the individual.<\/p>\n<\/blockquote>\n<\/li>\n personal information found in journalistic reports:<\/p>\n The use of personal information in a business transaction which is found in journalistic reports including news items, public broadcasts, items published by news media about an individual, personal information published and made available by third parties on the internet, (e.g., via Google, Facebook, Twitter, etc.), which in some jurisdictional domains is held to be \u201cin the public interest\u201d, is not included in this part of ISO\/IEC 15944.<\/p>\n The reasons for exclusion are that a journalistic report containing personal information about an individual:<\/p>\n may contain inaccurate information, allegations, and thus should not (can not) be used as \u201cpersonal information\u201d;<\/p>\n<\/li>\n may be subject to libel and other legal actions by the individual;<\/p>\n<\/li>\n etc.<\/p>\n<\/li>\n<\/ul>\n Further issues pertaining to privacy protection versus journalistic reports on identified individuals resulting in the publishing of personal information is a \u201cgrey area\u201d which courts in various jurisdictional domains are addressing and thus not yet resolved;<\/p>\n<\/li>\n this part of ISO\/IEC 15944 does not address the question of negotiated consent, but rather considers the simplest case, that a scenario may be registered which includes a specific form of consent within it;<\/p>\n<\/li>\n the use of biological characteristics and attributes of an individual which require the physical presence of an individual and are physically \u201ctaken\u201d from an individual in a particular context and for a specified role action of an individual;<\/p>\n These include the use of biometrics, biological (such as hair, blood, DNA samples), dentistry records, etc.<\/p>\n<\/li>\n the application of the rights of individuals who are disabled as stated in the \u201cUN Convention on the Rights of Persons with Disabilities\u201d (2006)19<\/sup>;<\/p>\n Of particular importance here is that this UN Convention takes as its basis the need to support individuals with disabilities to be a fully functioning member of society means that information necessary for these individuals to be able to make commitments including the undertaking of business transactions shall be made available in a form and format so that the semantics are fully communicated, the individual is able to have informed consent, etc.<\/p>\n<\/li>\n this part of ISO\/IEC 15944 does not address the role of an \u201combudsperson\u201d, \u201cPrivacy Commissioner\u201d, a \u201cData Protection Commissioner\u201d, etc., who serves as an independent adjudicator of complaints and ensures compliance with privacy protection requirements (including of internally of the organization or public administration themselves);<\/p>\n Many jurisdictional domains provide for the role of an ombudsperson which may be a role similar in application to public administration.<\/p>\n<\/li>\n detailed rules pertaining to the use of agents and\/or third parties by a seller in a business transaction<\/span><\/p>\n This includes their qualification and assurance of compliance with applicable privacy protection requirements for the personal information pertaining to a business transaction.<\/p>\n<\/li>\n an agent acting on behalf of an individual<\/span><\/p>\n An individual may request an agent to act on its behalf and this may or may not include the individual to require the agent not to reveal the individual identity or any personal information about the individual, i.e., as an anonymous \u201cclient\u201d of the agent.<\/p>\n<\/li>\n detailed rules governing the requirement to tag (or label) at the data elements (or field) level which form part of personal information of an individual generally as is required for as the business transactions(s) and its associated BTI(s);<\/p>\n<\/li>\n mergers and acquisitions<\/span><\/p>\n It is presumed that when an organization \u201cA\u201d merges with, or is acquired by another organization \u201cB\u201d, that the privacy protection requirements applicable to personal information under the control of organization \u201cA\u201d continue to apply and be enforced. It is also assumed the personal information under the control of organization \u201cA\u201d remains under its control and that a merger with or acquisition by organization \u201cB\u201d does not allow organization \u201cB\u201d to access and\/or use personal information held by organization \u201cA\u201d without the express and informed consent of the individuals whose personal information is\/was organization \u201cA\u201d.<\/p>\n<\/li>\n ICT and other service providers<\/span><\/p>\n 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.<\/p>\n<\/li>\n data mining<\/span><\/p>\n 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.<\/p>\n<\/li>\n formal Conformance Statements<\/span><\/p>\n 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 \u201cverifiable\u201d.<\/p>\n<\/li>\n linkages and similarities between privacy protection and consumer protection requirements<\/span><\/p>\n<\/li>\n<\/ol>\n 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}<\/p>\n 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).<\/p>\n 1.4<\/b> IT-systems environment neutrality<\/p>\n 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.<\/p>\n Information technology. Business Operational View – Identification of privacy protection requirements as external constraints on business transactions<\/b><\/p>\n\n
\n
\n
\n
\n
\n
\n
\n
\n
\n
\n
\n
\n
PDF Catalog<\/h4>\n
\n
\n PDF Pages<\/th>\n PDF Title<\/th>\n<\/tr>\n \n 10<\/td>\n 0.1.1 ISO\/IEC\u00a014662 “Open-edi Reference Model” <\/td>\n<\/tr>\n \n 12<\/td>\n 0.1.2 ISO\/IEC\u00a015944-1 \u201cBusiness Agreement Semantic Descriptive Techniques\u201d (\u201cBusiness Operational View (BOV\u201d)) <\/td>\n<\/tr>\n \n 22<\/td>\n 1.2.1 Functional Services View (FSV)
1.2.2 Internal behaviour of organizations (and public administration)
1.2.3 \u201corganization Person\u201d
1.2.4 Overlap of and\/or conflict among jurisdictional domains as sources of privacy protection requirements <\/td>\n<\/tr>\n\n 23<\/td>\n 1.2.5 Publicly available personal information <\/td>\n<\/tr>\n \n 66<\/td>\n 5.3.1 Privacy Protection Principle 1: Preventing Harm <\/td>\n<\/tr>\n \n 67<\/td>\n 5.3.2 Privacy Protection Principle 2: Accountability <\/td>\n<\/tr>\n \n 70<\/td>\n 5.3.3 Privacy Protection Principle 3: Identifying Purposes
5.3.4 Privacy Protection Principle 4: Informed Consent <\/td>\n<\/tr>\n\n 72<\/td>\n 5.3.5 Privacy Protection Principle 5: Limiting Collection <\/td>\n<\/tr>\n \n 74<\/td>\n 5.3.6 Privacy Protection Principle 6: Limiting Use, Disclosure and Retention <\/td>\n<\/tr>\n \n 77<\/td>\n 5.3.7 Privacy Protection Principle 7: Accuracy <\/td>\n<\/tr>\n \n 78<\/td>\n 5.3.8 Privacy Protection Principle 8: Safeguards <\/td>\n<\/tr>\n \n 79<\/td>\n 5.3.9 Privacy Protection Principle 9: Openness <\/td>\n<\/tr>\n \n 80<\/td>\n 5.3.10 Principle Protection Principle 10: Individual Access <\/td>\n<\/tr>\n \n 82<\/td>\n 5.3.11 Privacy Protection Principle 11: Challenging Compliance <\/td>\n<\/tr>\n \n 90<\/td>\n 7.2.1 Privacy protection <\/td>\n<\/tr>\n \n 92<\/td>\n 7.2.2 Person and external constraints: Consumer protection <\/td>\n<\/tr>\n \n 93<\/td>\n 7.2.3 Individual accessibility <\/td>\n<\/tr>\n \n 94<\/td>\n 7.2.4 Human rights
7.2.5 Privacy as a right of an \u201cindividual\u201d and not the right of an organization or public administration <\/td>\n<\/tr>\n<\/table>\n","protected":false},"excerpt":{"rendered":"\n\n
\n Published By<\/td>\n Publication Date<\/td>\n Number of Pages<\/td>\n<\/tr>\n \n BSI<\/b><\/a><\/td>\n 2012<\/td>\n 244<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n","protected":false},"featured_media":352062,"template":"","meta":{"rank_math_lock_modified_date":false,"ep_exclude_from_search":false},"product_cat":[698,2641],"product_tag":[],"class_list":{"0":"post-352056","1":"product","2":"type-product","3":"status-publish","4":"has-post-thumbnail","6":"product_cat-35-240-60","7":"product_cat-bsi","9":"first","10":"instock","11":"sold-individually","12":"shipping-taxable","13":"purchasable","14":"product-type-simple"},"_links":{"self":[{"href":"https:\/\/pdfstandards.shop\/wp-json\/wp\/v2\/product\/352056","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/pdfstandards.shop\/wp-json\/wp\/v2\/product"}],"about":[{"href":"https:\/\/pdfstandards.shop\/wp-json\/wp\/v2\/types\/product"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/pdfstandards.shop\/wp-json\/wp\/v2\/media\/352062"}],"wp:attachment":[{"href":"https:\/\/pdfstandards.shop\/wp-json\/wp\/v2\/media?parent=352056"}],"wp:term":[{"taxonomy":"product_cat","embeddable":true,"href":"https:\/\/pdfstandards.shop\/wp-json\/wp\/v2\/product_cat?post=352056"},{"taxonomy":"product_tag","embeddable":true,"href":"https:\/\/pdfstandards.shop\/wp-json\/wp\/v2\/product_tag?post=352056"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}