This page lists definitions for terms used throughout the DataPortability project, specifically as they are unique or have a special meaning related to the project.
NOTE: It is not necessary to define all the technologies used, a link to an appropriate definition will suffice (e.g. linking to the Wikipedia entry, etc.). When encountering terms not listed here, please add them. If you can extract a reasonable definition from where you encountered the term, please include it. Otherwise, please enter the term, but leave the definition blank as a prompt to the community that it needs to be filled in.
Primary Definitions
- ACCESSIBLE - data that is available to an external system (e.g. via an API), though not necessarily fully portable (e.g. it may contain CONTEXT-specific IDs).
Note: See the related definition of PORTABLE.
- CONTENT - information and experiences created by individuals, institutions and technology intended to be consumed by audiences in one or more CONTEXTS [ref]
- CONTEXT - circumstances, actions, and related conditions which surround an item, DATA, or experience.
Examples: File and object descriptions, access control lists, etc
- DATA - distinct pieces of information, usually formatted in a special way. [ref]
Note: The term normally needs an associated CONTEXT to have meaning.
- ENCUMBERED - in the context of the DPWG, CONTENT or DATA that is not clearly OWNED by the INDIVIDUAL can be considered encumbered.
Note: It is currently beyond the scope of the DPWG to delve too deeply into rights management that would help to clarify ownership issues.
- PERSONAL - concerning a close relationship between something (e.g. DATA, CONTENT) to an identified individual. [ref]
Note: The term normally needs an associated CONTEXT to have meaning.
- PORTABLE - able to move something from an original environment to a different environment. [ref]
Note: See the related definition of ACCESSIBLE
- PUBLIC - concerning things for the general body of mankind, or of a nation, state, or community [ref]
- OWNERSHIP - exclusive rights to possess, enjoy, and dispose of an object. [ref]
Note: See the related definitions for various OWNERSHIP TYPES.
Applied Definitions
- DATA CONTEXT - the CONTEXT associated with a piece of DATA, generally including the method the data was obtained, it's intended uses, and presumed OWNERSHIP.
Note: For privacy reasons, it will probably be required when accessing PERSONAL DATA, to include the CONTEXT, to ensure legality.
- ENCUMBERED CONTENT - where the OWNERSHIP of eag:CONTENT is shared or otherwise not clear, it is considered to be in some way eag:ENCUMBERED.
Note: While this wouldn't necessarily be a problem, the DPWG needs to address this issue when defining what content should or should not be required/suggested to be PORTABLE.
- OPEN DATA - a philosophy and practice requiring that certain data are freely available to everyone, without restrictions from copyright, patents or other mechanisms of control. [ref]
Note: For the purposes of the DPWG, some consideration will need to be given to the line between types of the types of data that should be portable, and it's ownership.
- PERSONAL CONTENT - CONTENT created or otherwise closely related to the identified INDIVIDUAL.
Examples: Photos, email correspondence, blog posts, favorite lists
Note: In a communication between two parties, OWNERSHIP is not always clearly defined; occaisionally the audience may also assume some claim over the CONTENT. Further, when the content is created within a the CONTEXT of an institution, they may also claim ownership.
- PORTABLE DATA - DATA rendered in a known format such that it is both made ACCESSIBLE and PORTABLE by a system other than that which is rendering it.
Note: Normally the eag:CONTEXT will need to be included, to ensure compliance with ownership and privacy obligations. See the related definitions for various PORTABLE DATA TYPES.
- PUBLIC CONTENT - CONTENT that is assumed to be within the public domain. [ref]
Personal Data Types
- PUBLIC PERSONAL DATA - PERSONAL DATA available to the PUBLIC.
Examples: nickname, CONTENT, some (though not necessarily all) contact details, etc.
- PRIVATE PERSONAL DATA - PERSONAL DATA not available to the PUBLIC.
Examples: full name, address, health records, childrens contact details, banking details, etc..
[Diagram] This diagram shows the types of personal data as layers, with decreasing number of people, in each type of relationship (friends, neighbours, mentors, etc) having access.
Portable Data Types
- PORTABLE ENCUMBERED CONTENT - ENCUMBERED CONTENT which can be moved from one system to another.
Note: This is a problematic situation the DPWG needs to address. Despite it's current prevelance (e.g. in the form of RSS feeds of blogs), the issue of unclear OWNERSHIP must be considered.
- PORTABLE PERSONAL DATA - PERSONAL DATA which can be moved from one system to another.
- PORTABLE PERSONAL CONTENT - PERSONAL CONTENT which can be moved from one system to another.
Note: At this time it is not clear whether this is part of the data portability initiative.
- PORTABLE PUBLIC CONTENT - PUBLIC CONTENT which can be moved from one system to another.
Ownership Types
Loshin (2002) identifies a list of parties laying a potential claim to data [ref]:
- Creator - The party that creates or generate data
- Consumer - The party that uses the data owns the data
- Compiler - This is the entity that selects and compiles information from different information sources
- Enterprise - All data that enters the enterprise or is created within the enterprise is completely owned by the enterprise
- Funder - the user that commissions the data creation claims ownership
- Decoder - In environments where information is "locked" inside particular encoded formats, the party that can unlock the information becomes an owner of that information
- Packager - the party that collects information for a particular use and adds value through formatting the information for a particular market or set of consumers
- Reader as owner - the value of any data that can be read is subsumed by the reader and, therefore, the reader gains value through adding that information to an information repository
- Subject as owner - the subject of the data claims ownership of that data, mostly in reaction to another party claiming ownership of the same data
- Purchaser/Licenser as Owner - the individual or organization that buys or licenses data may stake a claim to ownership
Action Items for the page
- We should cross-reference with other terminology glossaries such as OpenID 2.0 and SAML
|
|
