Classification of Everyday Living · Web viewClassification of Everyday Living Description This...

Classification of Everyday Living Version 1.0

Working Draft 03

23 January 2017

Technical Committee:OASIS Classification of Everyday Living (COEL) TC

Chairs:Joss Langford ([email protected]), Activinsights LtdDavid Snelling ([email protected]), Fujitsu Limited

Editors:Paul Bruton ([email protected]), Tessella Ltd.Joss Langford ([email protected]), Activinsights LtdMatthew Reed ([email protected]), CoelitionDavid Snelling ([email protected]), Fujitsu Limited

Additional artefacts:The additional artefact is a JSON object that provides the content of the Classification of Everyday Living model:

COEL model V1.0 (http://docs.oasis-open.org/coel/COEL/v1.0/csd02/model/coel.json)Related work:

This specification is related to: TBD Abstract:

This document provides TBD. Status:

This Working Draft (WD) has been produced by one or more TC Members; it has not yet been voted on by the TC or approved as a Committee Draft (Committee Specification Draft or a Committee Note Draft). The OASIS document Approval Process begins officially with a TC vote to approve a WD as a Committee Draft. A TC may approve a Working Draft, revise it, and re-approve it any number of times as a Committee Draft.

URI patterns:Initial publication URI:TBDPermanent "Latest version" URI:TBD(Managed by OASIS TC Administration; please don’t modify.)

Copyright © OASIS Open 2015. All Rights Reserved.All capitalized terms in the following text have the meanings assigned to them in the OASIS Intellectual Property Rights Policy (the "OASIS IPR Policy"). The full Policy may be found at the OASIS website.This document and translations of it may be copied and furnished to others, and derivative works that comment on or otherwise explain it or assist in its implementation may be prepared, copied, published, and distributed, in whole or in part, without restriction of any kind, provided that the above copyright notice and this section are included on all such copies and derivative works. However, this document itself may not be modified in any way, including by removing the copyright notice or references to OASIS, except as needed for the purpose of developing any document or deliverable produced by an OASIS Technical Committee (in which case the rules applicable to copyrights, as set forth in the OASIS IPR Policy, must be followed) or as required to translate it into languages other than English.

COEL-v1.0-wd03 Working Draft 03 23 January 2017Standards Track Draft Copyright © OASIS Open 2017. All Rights Reserved. of 42

https://www.oasis-open.org/policies-guidelines/ipr

http://docs.oasis-open.org/coel/BAP/v1.0/BAP-v1.0.docx

http://docs.oasis-open.org/coel/BAP/v1.0/csd01/BAP-v1.0-csd03.docx

https://www.oasis-open.org/policies-guidelines/tc-process#standApprovProcess

https://www.oasis-open.org/policies-guidelines/tc-process#committeeDraft

https://www.oasis-open.org/policies-guidelines/tc-process#dWorkingDraft

http://docs.oasis-open.org/coel/COEL/v1.0/csd02/model/coel.json

http://www.fujitsu.com/

mailto:[email protected]

http://www.coelition.org/


http://www.activinsights.com/


http://tessella.com/


http://www.fujitsu.com/


http://www.activinsights.com/


https://www.oasis-open.org/committees/coel/

The limited permissions granted above are perpetual and will not be revoked by OASIS or its successors or assigns.This document and the information contained herein is provided on an "AS IS" basis and OASIS DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT INFRINGE ANY OWNERSHIP RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.


Table of Contents1 Introduction ......................................................................................................................................... 6

1.1 Objective ........................................................................................................................................... 61.2 Summary of key COEL concepts ......................................................................................................61.3 Implementations ................................................................................................................................ 61.4 Terminology ....................................................................................................................................... 61.5 Notational Conventions ..................................................................................................................... 61.6 Normative References ....................................................................................................................... 61.7 Non-Normative References ...............................................................................................................61.8 Glossary ............................................................................................................................................ 6

2 A COEL ecosystem (non-normative) .................................................................................................102.1 Introduction ...................................................................................................................................... 102.2 Roles ............................................................................................................................................... 10

2.2.1 Summary of Roles ....................................................................................................................102.2.2 Identity Authority ......................................................................................................................102.2.3 Date Engine ............................................................................................................................. 102.2.4 Service Provider .......................................................................................................................102.2.5 Operator ................................................................................................................................... 102.2.6 Consumer ................................................................................................................................. 10

2.3 Principles of Operation of a COEL ecosystem ................................................................................102.4 Ecosystem structure ........................................................................................................................10

2.4.1 Relationships between actors ..................................................................................................102.4.2 Data Flows ............................................................................................................................... 11

3 COEL by Example (non-normative) ..................................................................................................123.1 Setting up a consumer facing health care service with COEL .........................................................123.2 Setting up the Data Engine – Service Provider – Operator handshakes .........................................123.3 Registering a Consumer .................................................................................................................. 123.4 Getting Consent .............................................................................................................................. 123.5 Delivering Service Journey ..............................................................................................................123.6 Etc ................................................................................................................................................... 12

4 The Classification of Everyday Living ................................................................................................134.1 Introduction ...................................................................................................................................... 134.2 Knowledge Base ............................................................................................................................. 134.3 COEL Data Model Specification ......................................................................................................134.4 Methodology .................................................................................................................................... 134.5 Principles behind structuring and populating the knowledge base ..................................................134.6 Structure of the COEL model ..........................................................................................................134.7 Description of the COEL taxonomy .................................................................................................134.8 Visualising the COEL model ............................................................................................................134.9 Principles for version control of COEL model ..................................................................................134.10 Permanent location of COEL JSON artefacts ................................................................................13

5 The Behavioural Atom ....................................................................................................................... 145.1 Introduction ...................................................................................................................................... 145.2 COEL Behavioural Atom Specification ............................................................................................14


5.3 Behavioural Atom Examples ...........................................................................................................146 Security ............................................................................................................................................. 15

6.1 General technical principles: ...........................................................................................................156.1.1 Internet ..................................................................................................................................... 156.1.2 Authentication ..........................................................................................................................156.1.3 Pseudonymous Keys ...............................................................................................................156.1.4 Userids and passwords ............................................................................................................15

6.2 Ecosystem security diagram and analysis .......................................................................................167 Minimal Management Interface .........................................................................................................18

7.1 Introduction ...................................................................................................................................... 187.2 COEL Minimal Management Interface Specification (MMI) .............................................................18

7.2.1 Authorization Protocol ..............................................................................................................187.2.2 Information Request ................................................................................................................. 18

7.2.2.1 Example (non-normative) ....................................................................................................................197.2.3 Service Provider: Create New Operator ...................................................................................19

7.2.3.1 Example (non-normative) ....................................................................................................................207.2.4 Service Provider: Retrieve Operator List ..................................................................................207.2.5 Service Provider: Retrieve Consumer List ................................................................................207.2.6 Service Provider: Forget Consumer .........................................................................................207.2.7 Operator: Create New Consumer .............................................................................................207.2.8 Operator: Assign a Device to a Consumer ...............................................................................20

8 Behavioural Atom Protocol Interface .................................................................................................218.1 Introduction ...................................................................................................................................... 218.2 COEL Behavioural Atom Protocol Interface Specification (BAP) .....................................................21

8.2.1 HTTP Protocol ..........................................................................................................................218.2.2 Media Types for Messages ......................................................................................................218.2.3 Operations ................................................................................................................................ 218.2.4 Security .................................................................................................................................... 218.2.5 Exceptions ................................................................................................................................ 21

9 Public Query Interface ....................................................................................................................... 229.1 Introduction ...................................................................................................................................... 229.2 COEL Public Query Interface Specification (PQI) ...........................................................................22

9.2.1 Authentication and Authorisation ..............................................................................................229.2.2 Query Operation ....................................................................................................................... 229.2.3 Segment Data .......................................................................................................................... 22

10 Identity Authority Interface ................................................................................................................2310.1 Introduction .................................................................................................................................... 23

10.1.1 The Identity Authority (IDA) ....................................................................................................2310.1.2 IDA Protocol Overview ...........................................................................................................23

10.2 COEL Identity Authority Interface Specification (IDA) ....................................................................2310.2.1 Overview ................................................................................................................................ 2310.2.2 Introduction ............................................................................................................................ 2310.2.3 Authentication and Authorisation ............................................................................................2310.2.4 PseudonymousKey endpoint ..................................................................................................2310.2.5 PseudonymousKeyBatch endpoint ........................................................................................23


10.2.6 Validation endpoint ................................................................................................................. 2311 Privacy-by-Design Implementations (non-normative) ........................................................................24

11.1 Principles ....................................................................................................................................... 2411.1.1 Data Separation Principle (P1) ...............................................................................................2411.1.2 Data Atomisation Principle (P2) .............................................................................................2411.1.3 Atomised Consent Principle (P3) ...........................................................................................2411.1.4 Separation of Competence Principle (P4) ..............................................................................2411.1.5 No Conflict of Interest Principle (P5) ......................................................................................2411.1.6 Active Support Principle (P6) .................................................................................................2511.1.7 Transparency Principle (P7) ...................................................................................................25

11.2 Actors, Roles & Responsibilities ....................................................................................................2511.2.1 Identity Authority .................................................................................................................... 2611.2.2 Data Engine ........................................................................................................................... 2611.2.3 Service Provider ..................................................................................................................... 2811.2.4 Operator ................................................................................................................................. 2911.2.5 Consumer ............................................................................................................................... 30

11.3 Actor Relationships ........................................................................................................................3112 Identity Management (non-normative) ..............................................................................................3213 COEL Policies & Adjacencies (non-normative) .................................................................................33

13.1 Security standards ......................................................................................................................... 3313.2 Consent standards ........................................................................................................................3313.3 Identity Assurance standards ........................................................................................................3313.4 Quality-of-Service policies .............................................................................................................3313.5 Use Cases ..................................................................................................................................... 33

14 Conformance ..................................................................................................................................... 3414.1 Conformance Targets .................................................................................................................... 3414.2 Conformance Clause 1: COEL Data Model ...................................................................................3414.3 Conformance Clause 2: COEL Behavioural Atom .........................................................................3414.4 Conformance Clause 3: COEL Minimal Management Interface ....................................................3414.5 Conformance Clause 4: COEL Behavioural Atom Protocol Interface ............................................3414.6 Conformance Clause 5: COEL Public Query Interface ..................................................................3514.7 Conformance Clause 6: COEL Identity Authority Interface ............................................................35

Appendix A. Acknowledgments ................................................................................................................. 36Appendix B. Known Extensions to the COEL Model ..................................................................................37Appendix C. Revision History .................................................................................................................... 381 Introduction ......................................................................................................................................... 6

1.1 Objective ........................................................................................................................................... 61.2 Summary of key COEL concepts ......................................................................................................61.3 Implementations ................................................................................................................................ 61.4 Terminology ....................................................................................................................................... 61.5 Notational Conventions ..................................................................................................................... 61.6 Normative References ....................................................................................................................... 61.7 Non-Normative References ...............................................................................................................61.8 Glossary (quite a bit from the RPE document) ..................................................................................6

2 A COEL ecosystem (This section is non-normative) ...........................................................................7


2.1 Introduction ........................................................................................................................................ 72.2 Roles ................................................................................................................................................. 7

2.2.1 Summary of Roles ...................................................................................................................... 72.2.2 Identity Authority ........................................................................................................................ 72.2.3 Date Engine ............................................................................................................................... 72.2.4 Service Provider ......................................................................................................................... 72.2.5 Operator ..................................................................................................................................... 72.2.6 Consumer ................................................................................................................................... 7

2.3 Principles of Operation of a COEL ecosystem ..................................................................................72.4 Ecosystem structure .......................................................................................................................... 7

2.4.1 Relationships between actors ....................................................................................................72.4.2 Data Flows ................................................................................................................................. 72.4.3 Security considerations ..............................................................................................................7

3 COEL by Example (This section is non-normative) .............................................................................83.1 Setting up a consumer facing health care service with COEL ...........................................................83.2 Setting up the Data Engine – Service Provider – Operator handshakes ...........................................83.3 Registering a Consumer .................................................................................................................... 83.4 Getting Consent ................................................................................................................................ 83.5 Delivering Service Journey ................................................................................................................83.6 Etc ..................................................................................................................................................... 8

4 The Classification of Everyday Living ..................................................................................................94.1 Introduction ........................................................................................................................................ 94.2 Knowledge Base ............................................................................................................................... 94.3 COEL Data Model Specification ........................................................................................................94.4 Methodology ...................................................................................................................................... 94.5 Principles behind structuring and populating the knowledge base ....................................................94.6 Structure of the COEL model ............................................................................................................94.7 Description of the COEL taxonomy ...................................................................................................94.8 Visualising the COEL model ..............................................................................................................94.9 Principles for version control of COEL model ....................................................................................94.10 Permanent location of COEL JSON artefacts ..................................................................................9

5 The Behavioural Atom ....................................................................................................................... 105.1 Introduction ...................................................................................................................................... 105.2 COEL Behavioural Atom Specification ............................................................................................105.3 Behavioural Atom Examples ...........................................................................................................10

6 Minimal Management Interface .........................................................................................................116.1 Introduction ...................................................................................................................................... 116.2 COEL Minimal Management Interface Specification (MMI) .............................................................11

6.2.1 Authorization Protocol ..............................................................................................................116.2.2 Information Request ................................................................................................................. 11

6.2.2.1 Example (non-normative) ....................................................................................................................126.2.3 Service Provider: Create New Operator ...................................................................................12

6.2.3.1 Example (non-normative) ....................................................................................................................136.2.4 Service Provider: Retrieve Operator List ..................................................................................136.2.5 Service Provider: Retrieve Consumer List ................................................................................13


6.2.6 Service Provider: Forget Consumer .........................................................................................136.2.7 Operator: Create New Consumer .............................................................................................136.2.8 Operator: Assign a Device to a Consumer ...............................................................................13

7 Behavioural Atom Protocol Interface .................................................................................................147.1 Introduction ...................................................................................................................................... 147.2 COEL Behavioural Atom Protocol Interface Specification (BAP) .....................................................14

7.2.1 HTTP Protocol ..........................................................................................................................147.2.2 Media Types for Messages ......................................................................................................147.2.3 Operations ................................................................................................................................ 147.2.4 Security .................................................................................................................................... 147.2.5 Exceptions ................................................................................................................................ 14

8 Public Query Interface ....................................................................................................................... 158.1 Introduction ...................................................................................................................................... 158.2 COEL Public Query Interface Specification (PQI) ...........................................................................15

8.2.1 Authentication and Authorisation ..............................................................................................158.2.2 Query Operation ....................................................................................................................... 158.2.3 Segment Data .......................................................................................................................... 15

9 Identity Authority Interface ................................................................................................................169.1 Introduction ...................................................................................................................................... 16

9.1.1 The Identity Authority (IDA) ......................................................................................................169.1.2 IDA Protocol Overview .............................................................................................................16

9.2 COEL Identity Authority Interface Specification (IDA) ......................................................................169.2.1 Overview .................................................................................................................................. 169.2.2 Introduction .............................................................................................................................. 169.2.3 Authentication and Authorisation ..............................................................................................169.2.4 PseudonymousKey endpoint ....................................................................................................169.2.5 PseudonymousKeyBatch endpoint ..........................................................................................169.2.6 Validation endpoint ...................................................................................................................16

10 COEL Policies & Adjacencies (This section is non-normative) .........................................................1710.1 Security standards ......................................................................................................................... 1710.2 Consent standards ........................................................................................................................1710.3 Identity Assurance standards ........................................................................................................1710.4 Quality-of-Service policies .............................................................................................................1710.5 Use Cases ..................................................................................................................................... 17

11 Conformance ..................................................................................................................................... 1811.1 Conformance Targets .................................................................................................................... 1811.2 Conformance Clause 1: COEL Data Model ...................................................................................1811.3 Conformance Clause 2: COEL Behavioural Atom .........................................................................1811.4 Conformance Clause 3: COEL Minimal Management Interface ....................................................1811.5 Conformance Clause 4: COEL Behavioural Atom Protocol Interface ............................................1811.6 Conformance Clause 5: COEL Public Query Interface ..................................................................1911.7 Conformance Clause 6: COEL Identity Authority Interface ............................................................19

Appendix A. Acknowledgments ................................................................................................................. 20Appendix B. Known Extensions to the COEL Model ..................................................................................21Appendix C. Revision History .................................................................................................................... 22


1 IntroductionThis document provides an overview of the structure of the specification and defines the model of the hierarchical taxonomy that provides the holistic framework for measuring everyday living events. The content of the model is defined in the document by a link to the JSON object.

1.1 Objective

1.2 Summary of key COEL concepts

1.3 Implementations

1.4 TerminologyThe key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in Error: Reference source not found.

1.5 Notational Conventions

1.6 Normative References[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP

14, RFC 2119, March 1997. http://www.ietf.org/rfc/rfc2119.txt. [RFC4627] D. Crockford, The application/json Media Type for JavaScript Object Notation

(JSON), July 2006, http://www.ietf.org/rfc/rfc4627.txt. [RFC7617] J. Reschke, Ed., "The 'Basic' HTTP Authentication Scheme", RFC 7617,

September 2015. http://www.ietf.org/rfc/rfc7617.txt [RFC5246] Dierks, T. and E. Rescorla, "The Transport Layer Security (TLS) Protocol Version

1.2", RFC 5246, August 2008. http://www.ietf.org/rfc/rfc5246.txt

1.7 Non-Normative References[Coelition] http://www.coelition.org. [Data to Life] Reed, M. & Langford, J. (2013). Data to Life. Coelition, London. ISBN 978-

0957609402

[1.8] Glossary (quite a bit from the RPE document)Identity Authority (IDA):

Oversees the effective, open running of the eco-system and administers the operation of the IDA service. The IDA service issues and checks unique Pseudonymous Keys that provide security and ensure the interoperability and universality of the ecosystem.

Data Engine:Receives, stores and processes Behavioural Atoms. Data Engines provide business-to-business services to Service Providers and other organisations in the form of queries that create Report Data.


Paul Bruton, 02/21/17,

No longer the right scope.

http://www.coelition.org/

http://www.ietf.org/rfc/rfc5246.txt




Service Provider:Provides the primary link between a Consumer and a Data Engine. They are able to query the atoms held by a Data Engine to develop personalised services for Consumers based on their everyday behaviours. Service Providers will often be consumer facing brands.

Associated Service Provider: A Service Provider that gains access to data collected by another service provider to provide a service to a Consumer.

Operator:Administers contact with the Consumer and hold the directly-identifying personal information (DIPI) needed to engage with the Consumer. An Operator might be an independent app, exist within a Service Provider or be an independent organisation. Operators only receive information from their Consumers and their Service Provider.

Consumer:The generic reference to any individual registered with the eco-system. They might be patients in a healthcare setting, subjects in a trial as well as consumers of a commercial digital service. A Consumer’s primary relationship might be with a Service Provider via a near-invisible Operator or with clearly recognisable Operator that is supported by a Service Provider in the background.

Technical Service Developer:Creates tools, infrastructure and software for managing data or services within the ecosystem, and do not handle Coelition services or personal data. These include: app developers for Service Providers, development agencies that create Service Provider or Data Engine or Coelition infrastructure. It could be that a Data Engine acts as a Technical Service Developer to create software infrastructure that is then run by one of their Service Providers. Technical Service Developers may be members of Coelition if they wish to use the trademarks to display that they conversant with the Coelition ecosystem and the development of software within it.

Hardware Developer:Developers of hardware (such as Internet of Things devices) which are compliant with COEL protocols for use by Service Providers and Operators.

Behavioural Atom: The fundamental data type defined and used extensively throughout the COEL ecosystem is Behavioural Atom (Atom). An Atom is a digital representation of an observable event in an individual’s life. It is a small block of self-describing, micro-structured data. Any type of life event can be coded into a Behavioural Atom using the Classification of Everyday Living, a hierarchical taxonomy of decreasing granularity. The individual’s identity is pseudonymised with the directly identifying personal information (DIPI) segregated from the Behavioural Atoms in both storage and transmission. The Behavioural Atoms also code the time and duration of events, how they were observed and where they occurred. The Atom types are described by the Classification of Everyday Living Version 1.0, one of this collection’s specifications.

Ecosystem:


The Ecosystem is defined as ‘the extended set of corporate and individual actors who interact for their mutual benefit via the medium of the specification and under appropriate voluntarily entered into legal agreements’.

Pseudonymous Key:The unique Pseudonymous Keys are generated by the IDA for use with the ecosystem to provide unique codes for the data and transaction of Consumers, Devices, Operators and Service Providers.

Directly Identifying Personal Information (DIPI):Static or slow-changing data needed to provide services to a Consumer including, for example: name, date of birth, contact information, medical/insurance numbers, payment details, etc. DIPI specifically excludes all event-based information (Behavioural Data / Atoms). DIPI is information that would be generally known as PII in a USA context.

Segment Data:Year of birth, gender, home time zone (GMT+/-x) and home latitude to single degree resolution.

Behavioural Data:Data that is coded according to the COEL TC protocols with, as a minimum, a Classification of Everyday Living code, a unique ConsumerID and a timestamp. A single instance is known as a Behavioural Atom or Atom.

Report Data:Data developed from the analysis of Behavioural Data (Atoms) for the purposes of developing insight and information for the provision of value-add services.

Aggregated and anonymised summary data:Data developed from the analysis of Behavioural Data (Atoms) for the purposes of comparison with Report Data and to deliver business to business services outside a COEL ecosystem.

ConsumerID:An IDA unique Pseudonymous Key for a particular Consumer.

ServiceProviderID:An IDA unique Pseudonymous Key for a particular Service Provider.

OperatorID:An IDA unique Pseudonymous Key for a particular Operator.

DeviceID:An IDA unique Pseudonymous Key for a particular consumer device.

PseudonymousKey:


A string formatted as a UUID as defined in [RFC_4122, Section 3] that uniquely identifies pseudonymously, an entity in the ecosystem. These are used for Consumer, Operator, Service Provider, and Device identifiers.

DateTime: A string formatted as a date-time according to [RFC_3339]. Used to represent the time of

an event within the ecosystem. Authorization Authentication Protocol: There are two authentication/authorisation protocols used in the ecosystem. In all cases

the underlying connection is protected by server side authenticated transport level security (TLS) [RFC5246][Ref??]. The two classes are 1) None: where the TSL connection is anonymous from the client side and therefore there is neither authentication nor authorisation required; and 2) BasicAuth: where the client must both authenticate and be authorised using HTTP Basic Authorisation Authentication [refRFC7617??].



We might get challenged over this since BasicAuth is referred to as an ‘authentication’ rather than authorization protocol, but we wrap both of these up in our error codes (e.g. we reject calls by an ‘operator’ to a ‘service provider’ API in the same way we reject any invalid password.

[2] A COEL ecosystem (This section is non-normative)1.8[2.1] Introduction

1.9[2.2] Roles

1.9.1[2.2.1] Summary of Roles

1.9.2[2.2.2] Identity Authority

1.9.3[2.2.3] Date Engine

1.9.4[2.2.4] Service Provider

1.9.5[2.2.5] Operator

1.9.6[2.2.6] Consumer

1.10[2.3] Principles of Operation of a COEL ecosystem

1.11[2.4] Ecosystem structure

1.11.1[2.4.1] Relationships between actors


1.11.2 Data Flows

The IDA issues a unique Pseudonymous Key to the Operator when the Consumer joins the ecosystem. Once this has been registered with the Data Engine it becomes the ConsumerID and replaces the DIPI in all transactions other than those between the Operator and Consumer.In normal operation the Behavioural Data will stay with the Data Engine unless the Service Provider needs to provide non-standard services or the Consumer makes a specific data request.The illustration shows the Segment Data delivered through the Service Provider, this is accurate when the data is recalled but the Operator sends this directly to the Data Engine when the Consumer is first registered.


Report Data & all services


Segment Data & report requests

Segment Data & report requests

Behavioural Data

DIPI, Segment Data

Device

Consumer


Operator

ServiceProvider

DataEngine

[2.4.2] Security considerations


[3] COEL by Example (This section is non-normative)1.12[3.1] Setting up a consumer facing health care service with COEL

1.13[3.2] Setting up the Data Engine – Service Provider – Operator handshakes

1.14[3.3] Registering a Consumer

1.15[3.4] Getting Consent

1.16[3.5] Delivering Service Journey

1.17[3.6] Etc


2[4] The Classification of Everyday Living2.1[4.1] Introduction

2.2[4.2] Knowledge Base

2.3[4.3] COEL Data Model Specification

2.4[4.4] Methodology

2.5[4.5] Principles behind structuring and populating the knowledge base

2.6[4.6] Structure of the COEL model

2.7[4.7] Description of the COEL taxonomy

2.8[4.8] Visualising the COEL model

2.9[4.9] Principles for version control of COEL model

2.10[4.10] Permanent location of COEL JSON artefacts


3[5] The Behavioural Atom3.1[5.1] Introduction

3.2[5.2] COEL Behavioural Atom Specification

3.3[5.3] Behavioural Atom Examples


4[6] Security4.1 General technical principles:

4.1.1 InternetSSL/TLS [RFC5246] SHALL be used for all internet communications within the ecosystem. This creates an encrypted channel for the data (Behavioural Atoms, Report data and Pseudonymous Keys – no DIPI) and prevents a third party from reading it in transit. It means that servers like the IDA, Data Engine and any Service Provider/ or Operator systems MUST have SSL/TLS certificates.

4.1.2 AuthenticationSingle factor authentication (userid and password) SHALL be used for all Data Engine and IDA calls with the exception of: [a] submitting atoms which can be done anonymously [b] an Operator registering consumers or assigning devices with the DE.

4.1.3 Pseudonymous Keys IDA generated Pseudonymous Keys SHALL be used as the userids for actors in the ecosystem. These are devoid of DIPI and unique across the ecosystem. Pseudonymous Keys used as Consumer IDs need to be handled carefully since they could be mis-used to pollute the atom collection in a data engine, or to retrieve data about a consumer if a service providers credentials are divulged.

4.1.4 Userids and passwordsDifferent userids MAY be used and different passwords SHALL be used for each embodiment (e.g. for Operator with IDA, Operator with Data Engine, Service Provider with different Data Engines). These SHALL be stored in an encrypted format.


4.2 Ecosystem security diagram and analysis

With reference to above diagram, the following is a summary of the specific requirements for the use or otherwise of secure communication:

1. Operator / IDA: The IDA SHALL require single factor authentication with userid and password for an Operator to access the IDA API.

2. Service Provider / IDA: The Service Provider does not have a role in the IDA API. The IDA MAY provide a mechanism to allow a Service Provider to register new Operators and this mechanism MUST be protected through single factor authentication, at least, with userid and password. The IDA SHALL NOT keep any DIPI for Operators.

3. Operator / Data Engine: The Data Engine SHALL NOT require a password from an Operator when registering a new Consumer or when assigning a new Device to a Consumer.

4. Service Provider / Data Engine:

a. The Data Engine SHALL require single factor authentication with userid and password for a Service Provider to access the Management Interface (MI) and Query Interface (QI)


6.

5.

4.

3.

1.

2.

Operator

ServiceProvider

IDA

DataEngine

b. Separate credentials SHOULD be used to access the Management Interface (MI) and Query Interface (QI), reducing the likelihood of getting access to both and retrieving Atoms for all of the Service Provider’s Consumers.

c. The data engine MUST use a secondary method to assert the identity of the Service Provider prior to processing a ‘forget’ request for a Consumer since these requests are not reversible.

5. Operator / Service Provider: Where the Operator is a separate entity, it will request reports on Consumers from the Service Provider, but these reports are pseudonymised and contain no DIPI. Where the Operator is a separate entity their communication MUST use single factor authentication with userid and password.

6. Data Engine / IDA: The IDA SHALL require single factor authentication with userid and password for a Data Engine to access the IDA API.


5[7] Minimal Management Interface5.1[7.1] IntroductionThis section defines the Minimal Management Interface (MMI) between the Data Engine and other actors in the ecosystem. It provides an information request operation through which all actors in the ecosystem discover the URLs for all operations on the Data Engine. It provides operation definitions on the Data Engine for use by a Service Provider to register a new Operator, to retrieve a list of existing Operators, to retrieve a list of Consumers associated with a given Operator, to suspend and resume Operators, register and unassign Devices and to assure a consumer is registered. It also provides operation definitions on the Data Engine for use by an Operator to register a Consumer, forget a Consumer and to associate a device with a consumer. This interface represents the minimal requirements of a Data Engine’s management interface, but does not limit this interface to these capabilities. High quality Data Engines may offer more comprehensive management services.

5.2[7.2] COEL Minimal Management Interface Specification (MMI)

5.2.1[7.2.1] Authorization ProtocolTo access all Service Provider operations on the Data Engine MMI API, Service Providers MUST use the BasicAuth Authorization Protocol.To assess all Operator operations on the Data Engine MMI API, Operators MUST use the None Authorization Protocol.

5.2.2[7.2.2] Information RequestEvery Data Engine SHALL publish its Data Engine Home URI. Performing a GET on this URI SHALL return general information about the Data Engine as JSON object.

Method RequestBody

Response Status ResponseContent-Type

Response Body

GET /home None 200 (OK) application/json JSON object

Format for the response body JSON object:Name Value Description REQUIRED

AtomsURI String The URI of the Atoms service encoded as a string. Yes

QueryURI String The URI of the Query service encoded as a string. Yes

ManagementURI String The URI of the Management service encoded as a string. Yes

ServerTime Integer Current server time in UTC as a Unix timestamp. YesAtomsStatus String The current status of the Atoms service encoded

as a string. It MUST be one of "Up", "Down", or Yes


"Unknown".

QueryStatus StringThe current status of the Query service encoded as a string. It MUST be one of "Up", "Down", or "Unknown".

Yes

ManagementStatus StringThe current status of the Management service encoded as a string. It MUST be one of "Up", "Down", or "Unknown".

Yes

The JSON object of the response MAY contain additional fields with information about the Data Engine.

5.2.2.1[7.2.2.1] Example (non-normative)Example request message:

GET /home

Example response message:

HTTP/1.1 200 OK

{"AtomsURI": "https://www.dataengine.com/atoms", "QueryURI": "https://www.dataengine.com/query", "ManagementURI": "https://www.dataengine.com/management", "AtomsStatus": "Up", "QueryStatus": "Up", "ManagementStatus", "Up", "ServerTime": 1470822001}

5.2.3[7.2.3] Service Provider: Create New OperatorCreate a new Operator within the Data Engine and associate it with the requesting Service Provider. Completion of this operation allows the Operator to register new Consumers.If successful, an HTTP status code of 200 OK MUST be returned. If unsuccessful, an HTTP error code SHOULD be returned and a JSON object MAY be returned providing some explanation of the failure. If validation of the OperatorID fails, with a 410 (Gone) error from the IDA, an error 410 (Gone) should be returned.

Method RequestBody

Response Status ResponseContent-Type

Response Body

POST service-provider/operator

JSON object 200 (OK) None None410 (Gone) application/json JSON object

Format for Content of the request body JSON object:Name Value Description REQUIRED

OperatorID PseudonymousKey

A Pseudonymous Key generated by an IDA and associated with the Operator being registered. Yes

TimeStamp DateTime Time stamp of the OperatorID indicating when Yes


the IDA created this Pseudonymous Key.

Signature String Signature proving that an IDA created this OperatorID. Yes

Format forContent of the response body JSON object:Name Value Description REQUIRED

Reason String An optional description of why the registration failed. No

5.2.3.1[7.2.3.1] Example (non-normative)

Example request message:POST service-provider/operator

{"OperatorID": "00000000-0000-0000-0000-000000000000", "TimeStamp": "2011-02-14T00:00:00", "Signature":"AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA="}

Example response message:

HTTP/1.1 410 Gone

{"Reason":"Operator was not valid."}

5.2.4[7.2.4] Service Provider: Retrieve Operator List

5.2.5[7.2.5] Service Provider: Retrieve Consumer List

5.2.6[7.2.6] Service Provider: Forget Consumer

5.2.7[7.2.7] Operator: Create New Consumer

5.2.8[7.2.8] Operator: Assign a Device to a Consumer


6[8] Behavioural Atom Protocol Interface6.1[8.1] Introduction

6.2[8.2] COEL Behavioural Atom Protocol Interface Specification (BAP)

6.2.1[8.2.1] HTTP Protocol

6.2.2[8.2.2] Media Types for Messages

6.2.3[8.2.3] Operations

6.2.4[8.2.4] Security

6.2.5[8.2.5] Exceptions



Take information request out of here and into MMI

7[9] Public Query Interface7.1[9.1] Introduction

7.2[9.2] COEL Public Query Interface Specification (PQI)

7.2.1[9.2.1] Authentication and Authorisation

7.2.2[9.2.2] Query Operation

7.2.3[9.2.3] Segment Data


8[10] Identity Authority Interface8.1[10.1] Introduction

8.1.1[10.1.1] The Identity Authority (IDA)

8.1.2[10.1.2] IDA Protocol Overview

8.2[10.2] COEL Identity Authority Interface Specification (IDA)

8.2.1[10.2.1] Overview

8.2.2[10.2.2] Introduction

8.2.3[10.2.3] Authentication and Authorisation

8.2.4[10.2.4] PseudonymousKey endpoint

8.2.5[10.2.5] PseudonymousKeyBatch endpoint

8.2.6[10.2.6] Validation endpoint


9[11] Privacy-by-Design Implementations (non-normative)

9.1 Principles

9.1.1 Data Separation Principle (P1)The specification implements a separation of data types: Data Engines keep data on what Consumers do (Behavioural Atoms) and the Service Provider/Operator keeps data on who Consumers are (DIPI). No single organisation holds both sets of data together. This means that it would need a double accidental or malicious disclosure for connected information to be released.

9.1.2 Data Atomisation Principle (P2)Data is deliberately broken down into small chunks of information by the Operator and coded with the Consumer’s ConsumerID (which implies their atomised consent), thus each separate Behavioural Atom has a very low privacy risk. Neither the Operator/Service Provider sees these atoms as raw atoms and can only see composite data from Data Engine under the terms of the specification.

9.1.3 Atomised Consent Principle (P3)Consumer gives informed consent to the Operator under guideline terms set by the specification. Consent allows the Operator to sign up the consumer with a ConsumerID. This ConsumerID is the indicator to Identity Authority and other eco-system actors that the consumer has given appropriate consent. Because each and every Behavioural Atom has the ConsumerID, each atom has that consumer’s consent written into the structure of the data. Removing the ConsumerID from a Behavioural Atom is removing the consent of that individual so the data can no longer be used by either the Operator or Service Provider who signed them up. The time stamp uniquely associated with each Behavioural Atom allows full auditing of this principle.

9.1.4 Separation of Competence Principle (P4)Data Engines are expert data handlers. They know how to run robust, secure and always on cloud based data services; they handle Behavioural Atoms NOT Consumers. Service Providers / Operators are experts at Consumer facing / relevant services and handling DIPI; they handle Consumers NOT Behavioural Atoms. The Identity Authority is expert at overseeing the ecosystem.

9.1.5 No Conflict of Interest Principle (P5)Consumers need to see that there are no conflicts around their data. To ensure this, the Identity Authority acts on behalf of the Consumer in partnership with Operator/Service Provider, Data Engine and regulators.


9.1.6 Active Support Principle (P6)All actors will actively promote the principles of the specification, safeguard the structure of the eco-system and support good data practice for both consumers and enterprise.

9.1.7 Transparency Principle (P7)The roles and identities of all the actors in the eco-system who are working together on behalf of a Consumer will be clear and visible to that Consumer.

9.2 Actors, Roles & Responsibilities

These roles will be performed by a number of actors that create the ecosystem. Actors may have multiple roles but certain combinations are not permissible as described in the Technical Requirements and the table below. The table shows all the possible role pairs; an actor may have more than two roles but every paring must be permitted.

Role 2

IDA Data Engine

Service Provider

Operator Consumer Technical Service

Developer

Hardware Developer

Role 1

IDA

Data Engine

Service Provider

Operator

Consumer

Technical Service

Developer

Hardware Developer


9.2.1 Identity AuthorityTechnical requirement Guiding principles & notes

SHALL Maintain an always-on IDA service that will generate or validate unique Pseudonymous Keys for Data Engine, Service Provider & Operator

P4

Be a non-profit legal entity P5

Provide its services on a fair, reasonable and non-discriminatory basis

P5

Provide Consumers with information about the operation of the eco-system free of charge

P5 & P7

SHALL NOT

Act as a Data Engine or Service Provider (other than for the purposes of providing a limited ‘sandbox’ test environment)

P4 & P5

Store Behavioural Atoms P4 & P5

Hold any Consumer’s directly identifying personal information (DIPI)

P5

MAY Request Data Engine support to deliver population-level insights for public information and the purposes of marketing the specification

P6

Make a query on Data Engines to ensure a specific ConsumerID has been forgotten

P7This allows the Identity Authority to audit the forgetting process.

Provide Consumers with information about their status within the eco-system, i.e. ‘known’ or ‘forgotten’ and only by ConsumerID and not DIPI.

P5 & P7

Provide audit services to Data Engine, Service Provider, Operator and regulators

P6

9.2.2 Data EngineTechnical requirement Guiding principles & notes

SHALL Provide secure storage of Behavioural Atoms for a period to be agreed with the Service Provider in line with the Consumer consent

P2 & P3

Provide minimal interface services for Service Providers to process joiners, movers, and leavers (e.g. Operator & Consumer trees, registration, ID re-allocation, forgetting)

P4


Provide minimal interface services for querying Behavioural Atoms by registered Service Providers

P1

Maintain an always-on, single entry point for uploading Behavioural Atoms to the Data Engine

P4

Receive Behavioural Atoms from Consumers or Devices registered with their Operators that conform to the specification free of charge

Receiving data is a minimal requirement for a Data Engine; commercial services apply to the use and processing of data.

Provide information to the Service Provider about the location and security of the infrastructure used in the delivery of services

P7

SHALL NOT

Link Behavioural Atom data to directly-identifying personal information (DIPI) from external sources

P1

Link Behavioural Atom data directly to external data storage if such link might directly identify Consumers

P1

Hold any Consumer’s directly identifying personal information (DIPI)

P1

Act as a Service Provider or Operator itself

P1 & P4

Request more than the Segment Data as defined in the specification (gender, year of birth, time zone & latitude to 0 decimal points) on registration of a Consumer

P1

Knowingly receive DIPI P1Levy unreasonably punitive charges for the complete download of stored Behavioural Atoms

Supports EU data protection and an open, competitive eco-system.

Utilise IDA unique Pseudonymous Keys outside of the ecosystem

P1

MAY Add non-personal data to the atom store to deliver enhanced services (e.g. local weather data)

P1While Behavioural Atoms cannot be linked out, additional information can be linked in.

Use suitable aggregation techniques rendering the data non-personal to provide indirect services to parties other than contracted Service Providers

P1 & P6

Host multiple Service Providers


9.2.3 Service ProviderTechnical requirement Guiding principles & notes

SHALL Ensure that their Operators have the minimum standard consent from Consumers

P3

Secure additional consent from Consumers when sending personal information outside the eco-system

P3 & P6

When sending Behavioural Atom information outside the eco-system, remove the ConsumerID and replace with DIPI

P6This ensures that information that has left the eco-system can be clearly identified.

Ensure that their Operators follow the specification

P6

For any one purpose and at any one time, have only one Data Engine

Avoids potential data loss for the consumer and ensures the complete audit map of the eco-system.

On a request from a Consumer, supply (or require associated Operator to do so) all DIPI, Segment Data, Behavioural Atoms and any stored Report Data

P2Basic tenet of EU data protection.

On a request from a Consumer to be forgotten, remove or render DIPI to be non-personal

Basic tenet of EU data protection.

On a request from a Consumer to be forgotten, instruct their Data Engine to remove or render data to be non-personal

P2 & P3

On a request from an Operator or Consumer, provide the identity of the Data Engine

P7

Notify Consumers (via Operators) of any mergers and acquisitions or other changes that would result in a change of control over the Consumers’ data

P7

Check the credentials of an Operator every time a request is made to release data for a ConsumerID

Security.

Ensure that all Operators within a specific embodiment are working under equivalent terms (e.g. consent, purpose, retention periods etc.).

P7

Use different passwords to interact with different actors in the ecosystem (within the same service embodiment).

Security.


Use a different ServiceProviderID for every instance of a service embodiment in which they are an actor

Security.

Hold ConsumerID Pseudonymous Keys with the same security level as DIPI.

Security.

Provide a secure interface to Operators such that communication is done in an appropriate manner with basic authentication as a minimum.

Security.

SHALL NOT

Receive Behavioural Atoms directly P1

Send DIPI to a Data Engine P1

Share DIPI with another Service Provider without additional consent from the Consumer

P3

MAY Transfer its operations between Data Engines

Supports open, competitive eco-system.

Host multiple Operators

An Associated Service Provider is a Service Provider that gains access to data collected by another service provider to provide a service to a Consumer. To do so, the Consumer MUST give consent to the Associated Service Provider to access the data collected by the original Service Provider. An Associated Service Provider has no right to grant a third-party any access to the data held by the original Service Provider. All of the technical requirements on a Service Provider above will apply to an Associated Service Provider except for Consumer requests to access or modify data held by the Data Engine which MUST be passed to the original Service Provider that collected the data.

9.2.4 OperatorTechnical requirement Guiding principles & notes

SHALL

Provide a mechanism for the consumer to access their ConsumerID.

P7This allows the Identity Authority to audit the ‘forgetting’ process.

Ensure that the minimum standard consent is given by Consumers - freely, specific & informed

P3

For any one purpose and at any one time, have only one Service Provider

Avoids potential data loss for the consumer and ensure the complete audit map of the eco-system.

Clearly identify the Service Provider to the Consumer

P7

Notify Consumers of any mergers and acquisitions or other changes that would result in a change of control over the Consumers’ data

P7


Hold ConsumerID Pseudonymous Keys with the same security level as DIPI

Security

Use different passwords to interact with different actors in the ecosystem (within the same service embodiment).

Security.

Use a different OperatorID for every instance of a service embodiment in which they are an actor

Security.

SHALL NOT

Store Behavioural Atoms other than for the purposes of transmission to the Data Engine.

P1

Send DIPI to a Data Engine P1

Share DIPI with another Operator or Service Provider without additional consent from the Consumer

P3

Utilise IDA unique Pseudonymous Keys outside of the ecosystem

P1

MAY Host multiple Consumers

9.2.5 ConsumerTechnical requirement Guiding principles & notes

MAY Request to be ‘forgotten’ in the eco-system


Request the Identity Authority to audit their status in the eco-system

P5 & P7

Request the Service Provider to supply their DIPI, demographic information and all Behavioural Atoms



9.3 Actor Relationships


Transparent Transparent

Device

Consumer

Possible Member

Contract Consent

CommercialContract

CommercialContract

Licence

Licence

LikelyMember

Likely Member

Operator

OASISCOEL TC

ServiceProvider

IDA

DataEngine

10 Identity Management (non-normative)

The COEL specification provides tools for the collection and processing of the behavioural data of individuals and therefore identity management will be essential to any overall system implementation. This specification provides a Unique Pseudonymous Key (UPK) that links all data for a specific Consumer. There is no requirement for a Consumer to have only one UPK and so, in true identity terms, a UPK links data for a profile. The ability of Consumer to maintain multiple profiles is an important method by which they can control their identity. Outside the scope of this specification, multiple UPKs (profiles) could be maintained formally or informally by a Consumer to control their personal data and visibility of combinations of their data to any Service Provider.The UPK is a private subject key where the Operator has the responsibility to validate, assure and authenticate the identity of the Consumer to a level appropriate to the application. There is no requirement for the Consumer and Operate to initiate their relationship with a strong identity negotiation. The UPK provides a reference for the collection of data under an ‘assertion of sameness’ principle that may or may not lead to a strong identity negotiation.


[12] COEL Policies & Adjacencies (This section is non-normative)

10.1[12.1] Security standards

10.2[12.2] Consent standards

10.3[12.3] Identity Assurance standards

10.4[12.4] Quality-of-Service policies

10.5[12.5] Use Cases


11[13] Conformance11.1[13.1] Conformance TargetsSections 4, 5, 6, 7, 8 and 9 contain the following implementations that are subject to compliance:

COEL Data ModelCOEL Behavioural AtomCOEL Minimal Management Interface (MMI)COEL Behavioural Atom Protocol Interface (BAP)COEL Public Query Interface (PQI)COEL Identity Authority Interface (IDA)

11.2[13.2] Conformance Clause 1: COEL Data ModelA data object conforms to this specification as COEL Data Model if it satisfies all the statements below:

[(a)] It is valid according to the structure and rules defined in section 4.34.3 "COEL Data Model Specification".

11.3[13.3] Conformance Clause 2: COEL Behavioural AtomA data object conforms to this specification as COEL Behavioural Atom if it satisfies all the statements below:

[(a)] It is valid according to the structure and rules defined in section 5.25.2 "COEL Behavioural Atom Specification".

11.4[13.4] Conformance Clause 3: COEL Minimal Management Interface

A Data Engine process or program conforms to this specification as COEL Minimal Management Interface if it satisfies all the statements below:

[(a)] It can understand and process the functions defined in section 7.26.2 "COEL Minimal Management Interface (MMI)" according to their rules and semantics.

[(b)] It generates errors as required in error cases described in section 7.26.2.

11.5[13.5] Conformance Clause 4: COEL Behavioural Atom Protocol Interface

A Service Provider process or program conforms to this specification as COEL Behavioural Atom Protocol Interface if it satisfies all the statements below:

(a) It classifies events with the COEL Data Model as defined in Clause 1: COEL Data Model.(b) It can correctly format Behavioural Atoms as defined in Clause 2: COEL Behavioural Atom.[(c)] It can transmit or transfer Behavioural Atoms as defined in section 8.27.2 "COEL Behavioural

Atom Protocol Interface Specification (BAP)".


A Data Engine process or program conforms to this specification as COEL Behavioural Atom Protocol Interface if it satisfies all the statements below:

(a) It can parse and recognize the elements of any conforming COEL Behavioural Atom, and generates errors for those data objects that fail to conform as COEL Behavioural Atom when this is clearly intended.

[(b)] It can receive Behavioural Atoms as defined in section 8.27.2 "COEL Behavioural Atom Protocol Interface Specification (BAP)".

[(c)] It generates errors as required in error cases described in section 7.2.[(d)] It correctly implenentsimplements the COEL Minimal Management Interface as defined in

clause Clause 3

11.6[13.6] Conformance Clause 5: COEL Public Query InterfaceA Data Engine process or program conforms to this specification as COEL Public Query Interface if it satisfies all the statements below:

(a) It can correctly format Behavioural Atoms as defined in Clause 2: COEL Behavioural Atom.[(b)] It can understand and process the functions defined in section 9.28.2 "COEL Public Query

Interface (PQI)" according to their rules and semantics.[(c)] It generates errors as required in error cases described in section 8.29.2.[(d)] It correctly implenentsimplements the COEL Minimal Management Interface as defined in

clause 3

11.7[13.7] Conformance Clause 6: COEL Identity Authority InterfaceAn Identity Authority process or program conforms to this specification as COEL Identity Authority Interface if it satisfies all the statements below:

[(a)] It can understand and process the functions defined in section 10.29.2 "COEL Identity Authority Interface (IDA)" according to their rules and semantics.

[(b)] It generates errors as required in error cases described in section 10.29.2.


Appendix A. AcknowledgmentsThe following individuals have participated in the creation of this specification and are gratefully acknowledged:Participants:!!br0ken!!

Paul Bruton, Individual MemberJoss Langford, ActivinsightsMatthew Reed, CoelitionDavid Snelling, Fujitsu


Appendix B. Known Extensions to the COEL Model


Appendix C. Revision HistoryRevision Date Editor Changes Made

0 23/01/2017 David Snelling Initial document outline

1 Joss Langford Atom -> Behavioural AtomAdded Behavioural Atom sectionMoved IDA sectionStandardised section formats & titlesBasic conformance text added

2 27/01/2017 Paul Bruton Added section ’10: Data Engine’ to separate out the data engine information request from the BAP. For discussion: Further restructuring needed.

3 27/01/2017 Paul Bruton Reverted previous changes after discussion: Decided to move Information Request from BAP to MMI Section. Re-ordered sections and conformance clauses to put MMI first

4 02/02/2017 David Snelling Added first two sections of the MMI for discussion.

5 02/09/2017 David Snelling Updated the definitions section for authorization protocols and two data types.

6 21/02/2017 Paul Bruton Put in references for TLS, BasicAuth. Some minor corrections and comments.

7 24/02/2017 Joss Langford Added sections for ‘Privacy-by-Design’, ‘Security’ & ‘Identity Management’.Brought over all text form RPE.


Classification of Everyday Living · Web viewClassification of Everyday Living Description This...

Documents

Transcript of Classification of Everyday Living · Web viewClassification of Everyday Living Description This...