This work is distributed under a Creative Commons Attribution License (http://creativecommons.org/licenses/by/3.0/).
Dublin Core Metadata Element Set, Version 1.1
Examples of a Contributor include a person, an organization, or a service. Typically, the name of a Contributor should be used to indicate the entity.
An entity responsible for making contributions to the resource.
Contributor
A second property with the same name as this property has been declared in the dcterms: namespace (http://purl.org/dc/terms/). See the Introduction to the document "DCMI Metadata Terms" (http://dublincore.org/documents/dcmi-terms/) for an explanation.
Spatial topic and spatial applicability may be a named place or a location specified by its geographic coordinates. Temporal topic may be a named period, date, or date range. A jurisdiction may be a named administrative entity or a geographic place to which the resource applies. Recommended best practice is to use a controlled vocabulary such as the Thesaurus of Geographic Names [TGN]. Where appropriate, named places or time periods can be used in preference to numeric identifiers such as sets of coordinates or date ranges.
The spatial or temporal topic of the resource, the spatial applicability of the resource, or the jurisdiction under which the resource is relevant.
Coverage
Examples of a Creator include a person, an organization, or a service. Typically, the name of a Creator should be used to indicate the entity.
An entity primarily responsible for making the resource.
Creator
Date may be used to express temporal information at any level of granularity. Recommended best practice is to use an encoding scheme, such as the W3CDTF profile of ISO 8601 [W3CDTF].
A point or period of time associated with an event in the lifecycle of the resource.
Date
Description may include but is not limited to: an abstract, a table of contents, a graphical representation, or a free-text account of the resource.
An account of the resource.
Description
Examples of dimensions include size and duration. Recommended best practice is to use a controlled vocabulary such as the list of Internet Media Types [MIME].
The file format, physical medium, or dimensions of the resource.
Format
Recommended best practice is to identify the resource by means of a string conforming to a formal identification system.
An unambiguous reference to the resource within a given context.
Identifier
Recommended best practice is to use a controlled vocabulary such as RFC 4646 [RFC4646].
A language of the resource.
Language
Examples of a Publisher include a person, an organization, or a service. Typically, the name of a Publisher should be used to indicate the entity.
An entity responsible for making the resource available.
Publisher
Recommended best practice is to identify the related resource by means of a string conforming to a formal identification system.
A related resource.
Relation
Typically, rights information includes a statement about various property rights associated with the resource, including intellectual property rights.
Information about rights held in and over the resource.
Rights
The described resource may be derived from the related resource in whole or in part. Recommended best practice is to identify the related resource by means of a string conforming to a formal identification system.
A related resource from which the described resource is derived.
Source
Typically, the subject will be represented using keywords, key phrases, or classification codes. Recommended best practice is to use a controlled vocabulary.
The topic of the resource.
Subject
A name given to the resource.
Title
Recommended best practice is to use a controlled vocabulary such as the DCMI Type Vocabulary [DCMITYPE]. To describe the file format, physical medium, or dimensions of the resource, use the Format element.
The nature or genre of the resource.
Type
title
hasVersion
publisher
modified
issued
description
Action
Article 6.1(b) Processing that is necessary for the performance of a contract to which the data subject is party or in order to take steps at the request of the data subject prior to entering into a contract.
ContractualProcessing
Article 20.1 Automated processing intended to evaluate certain personal aspects relating to this natural person or to analyse or predict in particular the natural person's performance at work, economic situation, location, health, personal preferences, reliability or behaviour.
Profiling
Rule that applies only to the transfer of personal data.
TransferRule
Article 4(3) Any operation or set of operations which is performed upon personal data or sets of personal data, whether or not by automated means, such as collection, recording, organization, structuring, storage, adaptation or alteration, retrieval, consultation, use, disclosure by transmission, dissemination or otherwise making available, alignment or combination, erasure or destruction.
DataProcessing
Interest concerning the life or health of a subject.
VitalInterest
A recipient not located within the European Union and not subject to the Regulation.
NonEURecipient
Article 15.2 The request to obtain from the controller communication of the personal data undergoing processing. Where the data subject makes the request in electronic form, the information shall be provided in electronic form, unless otherwise requested by the data subject.
Access
DPH s. 3.4.2 Controllers should document, to data subjects and to the general public, that they will process data in a lawful and transparent manner. Processing operations must not be performed in secret and should not have unforeseeable negative effects. Controllers should ensure that customers, clients or citizens are informed about the use of their data. Further, controllers, so far as possible, must act in a way which promptly complies with the wishes of the data subject, especially where his or her consent forms the legal basis for the data processing.
Trust
The request to obtain from the controller the erasure of personal data relating to them and the abstention from further dissemination of such data.
Erasure
Article 6.1(d) Processing that is necessary in order to protect the vital interests of the data subject.
VitalProcessing
Binding instrument to establish a legal relationship between two or more parties.
Contract
DPH s. 3.3.1 Only such data shall be processed as are "adequate, relevant and not excessive in relation to the purpose for which they are collected and/or further processed". The categories of data chosen for processing must be necessary in order to achieve the declared overall aim of the processing operations, and a controller should strictly limit collection of data to such information as is directly relevant for the specific purpose pursued by the processing.
Relevancy
The actual reason for which the processing is performed. The processing is lawful if one of the lawfulness conditions apply. The lawfulness conditions have a twofold meaning: - they represent the legal grounds that make the processing lawful. This is an application of the lawfulness principle; - they define the boundaries within which the processing is allowed. This is an application of the principle of purpose limitation. The combination of these two facets makes up the processing scope.
ProcessingScope
Article 4(14) Any natural or legal person established in the Union who, explicitly designated by the controller, acts and may be addressed by any supervisory authority and other bodies in the Union instead of the controller, with regard to the obligations of the controller under this Regulation.
Representative
Security measures that concern the organization of the controller or processor, including the division of roles and limited access rights.
OrganisationalMeasures
Article 6.1(c) Processing that is necessary for compliance with a legal obligation to which the controller is subject.
ObligatedProcessing
Article 19.1 The data subject shall have the right to object, on grounds relating to their particular situation, at any time to the processing of personal data which is based on points (d), (e) and (f) of Article 6(1), unless the controller demonstrates compelling legitimate grounds for the processing which override the interests or fundamental rights and freedoms of the data subject.
RightToObject
Any processing that is not based upon the explicit consent of the data subject.
RequiredProcessing
Article 30.1 The controller and the processor shall implement appropriate technical and organisational measures to ensure a level of security appropriate to the risks represented by the processing and the nature of the personal data to be protected, having regard to the state of the art and the costs of their implementation.
Security
Article 40 Any transfer of personal data which are undergoing processing or are intended for processing after transfer to a third country or to an international organisation may only take place if, subject to the other provisions of this Regulation, the conditions laid down in Chapter V are complied with by the controller and processor, including for onward transfers of personal data from the third country or an international organisation to another third country or to another international organisation.
LawfulTransfer
The means by which the controller and the processor tries to avoid data breaches.
Measures
Personal data should be collected only when, and to the extent to which, a given purpose cannot be reached without using anonymous or statistical data or data that do not allow identification of the data subject.
DataMinimization
Article 4(6) A natural or legal person, public authority, agency or any other body which processes personal data on behalf of the controller.
Processor
Article 42.1 Where the Commission has taken no decision pursuant to Article 41, a controller or processor may transfer personal data to a third country or an international organisation only if the controller or processor has adduced appropriate safeguards with respect to the protection of personal data in a legally binding instrument.
AppropriateSafeguards
Security measures introduced in the technical infrastructure of the controller or processor, such as secure protocols, access control systems or encryption.
TechnicalMeasures
Article 4(5) the natural or legal person, public authority, agency or any other body which alone or jointly with others determines the purposes, conditions and means of the processing of personal data; where the purposes, conditions and means of processing are determined by Union law or Member State law, the controller or the specific criteria for his nomination may be designated by Union law or by Member State law.
Controller
Article 16 The data subject shall have the right to obtain from the controller the rectification of personal data relating to them which are inaccurate. The data subject shall have the right to obtain completion of incomplete personal data, including by way of supplementing a corrective statement.
RightToRectification
DPH s. 3.3.3 Article 6 (1) (e) of the Data Protection Directive and, likewise, Article 5 (e) of Convention 108 require Member States to ensure that personal data are "kept in a form which permits identification of data subjects for no longer than is necessary for the The key principles of European data protection law purposes for which the data were collected or for which they are further processed." The data must therefore be erased when those purposes have been served.
Retention
Article 39.1 The Member States and the Commission shall encourage, in particular at European level, the establishment of data protection certification mechanisms and of data protection seals and marks, allowing data subjects to quickly assess the level of data protection provided by controllers and processors. The data protection certifications mechanisms shall contribute to the proper application of this Regulation, taking account of the specific features of the various sectors and different processing operations.
Certification
Article 11 The controller shall have transparent and easily accessible policies with regard to the processing of personal data and for the exercise of data subjects' rights. The controller shall provide any information and any communication relating to the processing of personal data to the data subject in an intelligible form, using clear and plain language, adapted to the data subject, in particular for any information addressed specifically to a child.
TransparentInformation
Article 23.1 Having regard to the state of the art and the cost of implementation, the controller shall, both at the time of the determination of the means for processing and at the time of the processing itself, implement appropriate technical and organisational measures and procedures in such a way that the processing will meet the requirements of this Regulation and ensure the protection of the rights of the data subject.
PrivacyByDesign
Article 15.1 The data subject shall have the right to obtain from the controller at any time, on request, confirmation as to whether or not personal data relating to the data subject are being processed. Where such personal data are being processed, the controller shall provide the following information: (a) the purposes of the processing; (b) the categories of personal data concerned; (c) the recipients or categories of recipients to whom the personal data are to be or have been disclosed, in particular to recipients in third countries; (d) the period for which the personal data will be stored; (e) the existence of the right to request from the controller rectification or erasure of personal data concerning the data subject or to object to the processing of such personal data; (f) the right to lodge a complaint to the supervisory authority and the contact details of the supervisory authority; (g) communication of the personal data undergoing processing and of any available information as to their source; (h) the significance and envisaged consequences of such processing, at least in the case of measures referred to in Article 20.
RightOfAccess
Article 6.1(e) Processing that is necessary for the performance of a task carried out in the public interest or in the exercise of official authority vested in the controller.
PublicInterestProcessing
Article 38.1 The Member States, the supervisory authorities and the Commission shall encourage the drawing up of codes of conduct intended to contribute to the proper application of this Regulation, taking account of the specific features of the various data processing sectors, in particular in relation to: (a) fair and transparent data processing; (b) the collection of data; (c) the information of the public and of data subjects; (d) requests of data subjects in exercise of their rights; (e) information and protection of children; (f) transfer of data to third countries or international organisations; (g) mechanisms for monitoring and ensuring compliance with the code by the controllers adherent to it; (h) out-of-court proceedings and other dispute resolution procedures for resolving disputes between controllers and data subjects with respect to the processing of personal data, without prejudice to the rights of the data subjects pursuant to Articles 73 and 75.
CodeOfConduct
Article 5(f) Personal data must be processed under the responsibility and liability of the controller, who shall ensure and demonstrate for each processing operation the compliance with the provisions of this Regulation.
Compliance
A specific operation which is performed upon personal data or sets of personal data.
ProcessingActivity
A recipient located within the European Union, or subject to the Regulation.
EURecipient
Consent to the processing of personal data of a child below the age of 13 years given or authorised by the child's parent or custodian.
ParentConsent
DPH ch. 3 The principles set out in Article 5 of Convention 108 enshrine the essence of European data protection law. They appear also in Article 6 of the Data Protection Directive as the starting point for more detailed provisions in the subsequent articles of the directive. All later data protection legislation at the CoE or EU level must comply with these principles and they must be kept in mind when interpreting such legislation. Any exemptions from and restrictions to these key principles may be provided for at national level;107 they must be provided for by law, pursue a legitimate aim and be necessary in a democratic society. All three conditions must be fulfilled.
Principle
Article 43.1 A supervisory authority shall in accordance with the consistency mechanism set out in Article 58 approve binding corporate rules, provided that they: (a) are legally binding and apply to and are enforced by every member within the controller’s or processor's group of undertakings, and include their employees; (b) expressly confer enforceable rights on data subjects; (c) fulfil the requirements laid down in paragraph 2.
BindingCorporateRules
Processing that requires human activity.
ManualProcessing
Article 23.2 The controller shall implement mechanisms for ensuring that, by default, only those personal data are processed which are necessary for each specific purpose of the processing and are especially not collected or retained beyond the minimum necessary for those purposes, both in terms of the amount of the data and the time of their storage. In particular, those mechanisms shall ensure that by default personal data are not made accessible to an indefinite number of individuals.
PrivacyByDefault
The data subjects' objection to the processing of personal data, on grounds relating to their particular situation, at any time to the processing of personal data which is based on points (d), (e) and (f) of Article 6(1).
Objection
DPH s. 3.5 The Organisation for Economic Co-operation and Development (OECD) adopted privacy guidelines in 2013 that highlighted that controllers have an important role in making data protection work in practice. The guidelines develop an accountability principle to the effect that "a data controller should be accountable for complying with measures which give effect to the [material] principles stated above."
Accountability
DPH s. 4.1.1 Chapter II of Directive 95/46, entitled ‘General rules on the lawfulness of the processing of personal data’, provides that, subject to the exceptions permitted under Article 13, all processing of personal data must comply, first, with the principles relating to data quality set out in Article 6 of the Data Protection Directive and, secondly, with one of the criteria for making data processing legitimate, listed in Article 7. This explains the cases which legitimise the processing of non-sensitive personal data.
LawfulnessRule
A data subject under the age of 13 years.
ChildDataSubject
DPH s. 3.4.1 This principle establishes an obligation for the controller to keep the data subjects informed about how their data are being used.
Transparency
The specific way in which the processing is performed.
ProcessingMode
DPH s. 5.1 The effectiveness of legal rules in general and data subjects’ rights in particular, depends to a considerable extent on the existence of appropriate mechanisms to enforce them. In European data protection law, the data subject must be empowered by national law to protect his or her data. Independent supervisory authorities must also be established by national law to assist the data subjects in exercising their rights and to supervise the processing of personal data. Additionally, the right to an effective remedy, as guaranteed under the ECHR and the Charter, demands that judicial remedies be available to every person.
DataSubjectRight
The parent or custodian of a child below the age of 13 years.
Parent
Article 17.1 The data subject shall have the right to obtain from the controller the erasure of personal data relating to them and the abstention from further dissemination of such data, especially in relation to personal data which are made available by the data subject while he or she was a child, where one of the following grounds applies: (a) the data are no longer necessary in relation to the purposes for which they were collected or otherwise processed; (b) the data subject withdraws consent on which the processing is based according to point (a) of Article 6(1), or when the storage period consented to has expired, and where there is no other legal ground for the processing of the data; (c) the data subject objects to the processing of personal data pursuant to Article 19; (d) the processing of the data does not comply with this Regulation for other reasons.
RightToErasure
An individual or organization involved in the processing of personal data.
Person
Article 7 The controller shall bear the burden of proof for the data subject's consent to the processing of their personal data for specified purposes. If the data subject's consent is to be given in the context of a written declaration which also concerns another matter, the requirement to give consent must be presented distinguishable in its appearance from this other matter. The data subject shall have the right to withdraw his or her consent at any time. The withdrawal of consent shall not affect the lawfulness of processing based on consent before its withdrawal. Consent shall not provide a legal basis for the processing, where there is a significant imbalance between the position of the data subject and the controller.
Consent
Objective that a subject can legally pursue.
LegitimateInterest
Article 14.1 Where personal data relating to a data subject are collected, the controller shall provide the data subject with at least the following information: (a) the identity and the contact details of the controller and, if any, of the controller's representative and of the data protection officer; (b) the purposes of the processing for which the personal data are intended, including the contract terms and general conditions where the processing is based on point (b) of Article 6(1) and the legitimate interests pursued by the controller where the processing is based on point (f) of Article 6(1); (c) the period for which the personal data will be stored; (d) the existence of the right to request from the controller access to and rectification or erasure of the personal data concerning the data subject or to object to the processing of such personal data; (e) the right to lodge a complaint to the supervisory authority and the contact details of the supervisory authority; (f) the recipients or categories of recipients of the personal data; (g) where applicable, that the controller intends to transfer to a third country or international organisation and on the level of protection afforded by that third country or international organisation by reference to an adequacy decision by the Commission; (h) any further information necessary to guarantee fair processing in respect of the data subject, having regard to the specific circumstances in which the personal data are collected.
RightToInformation
Requirement that the controller or processor must fulfill to be compliant with the Regulation.
Rule
Article 37.1 The controller or the processor shall entrust the data protection officer at least with the following tasks: (a) to inform and advise the controller or the processor of their obligations pursuant to this Regulation and to document this activity and the responses received; (b) to monitor the implementation and application of the policies of the controller or processor in relation to the protection of personal data, including the assignment of responsibilities, the training of staff involved in the processing operations, and the related audits; (c) to monitor the implementation and application of this Regulation, in particular as to the requirements related to data protection by design, data protection by default and data security and to the information of data subjects and their requests in exercising their rights under this Regulation; (d) to ensure that the documentation referred to in Article 28 is maintained; (e) to monitor the documentation, notification and communication of personal data breaches pursuant to Articles 31 and 32; (f) to monitor the performance of the data protection impact assessment by the controller or processor and the application for prior authorisation or prior consultation, if required pursuant Articles 33 and 34; (g) to monitor the response to requests from the supervisory authority, and, within the sphere of the data protection officer's competence, co-operating with the supervisory authority at the latter's request or on the data protection officer's own initiative; (h) to act as the contact point for the supervisory authority on issues related to the processing and consult with the supervisory authority, if appropriate, on his/her own initiative.
DataProtectionOfficer
DPH s. 3.2 In essence, the principle of purpose specification and limitation means that the legitimacy of processing personal data will depend on the purpose of the processing. The purpose must have been specified and made manifest by the controller before the processing of data starts. Under EU law, this must be done either by declaration, in other words by notification, to the appropriate supervisory authority or, at the least, by internal documentation which must be made available by the controller for inspection by the supervisory authorities and access by the data subject.
Purpose
Article 20.1 Every natural person shall have the right not to be subject to a measure which produces legal effects concerning this natural person or significantly affects this natural person, and which is based solely on automated processing intended to evaluate certain personal aspects relating to this natural person or to analyse or predict in particular the natural person's performance at work, economic situation, location, health, personal preferences, reliability or behaviour.
RightToNoProfiling
DPH s. 3.3 The principles of data quality must be implemented by the controller in all processing operations. The principle of limited retention of data makes it necessary to delete data as soon as they are no longer needed for the purposes for which they were collected. Exemptions from the principle of limited retention must be set out by law and need special safeguards for the protection of data subjects.
DataQuality
DPH s. 3.1.1 The processing of personal data may constitute an interference with the right to respect for private life of the data subject. The right to respect for private life is, however, not an absolute right but must be balanced against and reconciled with other legitimate interests, be they of other persons (private interests) or of society as a whole (public interests).
LawfulnessPrinciple
Reason to perform the processing, such as the interest of the data controller.
Justification
Article 4(1) An identified natural person or a natural person who can be identified, directly or indirectly, by means reasonably likely to be used by the controller or by any other natural or legal person, in particular by reference to an identification number, location data, online identifier or to one or more factors specific to the physical, physiological, genetic, mental, economic, cultural or social identity of that person.
DataSubject
Article 4(7) A natural or legal person, public authority, agency or any other body to which the personal data are disclosed
Recipient
Article 41.1 A transfer may take place where the Commission has decided that the third country, or a territory or a processing sector within that third country, or the international organisation in question ensures an adequate level of protection. Such transfer shall not require any further authorisation.
AdequacyDecision
Article 6.1(a) Processing of personal data to which the data subject has given consent for one or more specific purposes.
ConsensualProcessing
A violation of the security measures of the data controller that exposes personal data to unintended subjects.
DataBreach
Article 28.1 Each controller and processor and, if any, the controller's representative, shall maintain documentation of all processing operations under its responsibility.
Documentation
DPH ch. 4 Principles are necessarily of a general nature. Their application to concrete situations leaves a certain margin of interpretation and choice of means. Under CoE law, it is left to the Parties to Convention 108 to clarify this margin of interpretation in their domestic law. The situation in EU law is different: for the establishment of data protection in the internal market, it was deemed necessary to have more detailed rules already at the EU level in order to harmonise the level of data protection of the national laws of the Member States. The Data Protection Directive establishes, under the principles set out in its Article 6, a layer of detailed rules which must be faithfully implemented in national law. The following remarks on detailed data protection rules at the European level deal, therefore, predominantly with EU law.
ProcessingRule
Article 33.1 Where processing operations present specific risks to the rights and freedoms of data subjects by virtue of their nature, their scope or their purposes, the controller or the processor acting on the controller's behalf shall carry out an assessment of the impact of the envisaged processing operations on the protection of personal data.
ImpactAssessment
The request to obtain from the controller the rectification of personal data relating to them which are inaccurate.
Rectification
Article 4(19) A public authority which is established by a Member State in accordance with Article 46.
SupervisoryAuthority
Article 6.1(f) Processing that is necessary for the purposes of the legitimate interests pursued by a controller, except where such interests are overridden by the interests or fundamental rights and freedoms of the data subject which require protection of personal data, in particular where the data subject is a child. This shall not apply to processing carried out by public authorities in the performance of their tasks.
LegitimateInterestProcessing
Behaviour that is legally required of a subject by means of a contract or law.
LegalObligation
Personal data pertaining to a data subject under the age of 13 years.
ChildData
Article 4(3) Disclosure of personal data by transmission, dissemination or otherwise making available.
DataTransfer
DPH s. 3.4 The principle of fair processing governs primarily the relationship between the controller and the data subject.
Fairness
Article 4(2) Any information relating to a data subject.
PersonalData
Article 31.1 In the case of a personal data breach, the controller shall without undue delay and, where feasible, not later than 24 hours after having become aware of it, notify the personal data breach to the supervisory authority. The notification to the supervisory authority shall be accompanied by a reasoned justification in cases where it is not made within 24 hours. Article 32.1 When the personal data breach is likely to adversely affect the protection of the personal data or privacy of the data subject, the controller shall, after the notification referred to in Article 31, communicate the personal data breach to the data subject without undue delay.
BreachNotification
An interest beneficial to a general community of undetermined individuals.
PublicInterest
Article 9.1 Personal data revealing race or ethnic origin, political opinions, religion or beliefs, trade-union membership, and the processing of genetic data or data concerning health or sex life or criminal convictions or related security measures.
SensitiveData
Processing that does not require human activity.
AutomatedProcessing
Article 6.1 Processing of personal data shall be lawful only if and to the extent that at least one of the following applies: (a) the data subject has given consent to the processing of their personal data for one or more specific purposes; (b) processing is necessary for the performance of a contract to which the data subject is party or in order to take steps at the request of the data subject prior to entering into a contract; (c) processing is necessary for compliance with a legal obligation to which the controller is subject; (d) processing is necessary in order to protect the vital interests of the data subject; (e) processing is necessary for the performance of a task carried out in the public interest or in the exercise of official authority vested in the controller; (f) processing is necessary for the purposes of the legitimate interests pursued by a controller, except where such interests are overridden by the interests or fundamental rights and freedoms of the data subject which require protection of personal data, in particular where the data subject is a child. This shall not apply to processing carried out by public authorities in the performance of their tasks.
LawfulProcessing
Reason to perform the processing which is based on legal grounds, such as an legitimate interest of the data controller.
LegalJustification
Article 18 The data subject shall have the right, where personal data are processed by electronic means and in a structured and commonly used format, to obtain from the controller a copy of data undergoing processing in an electronic and structured format which is commonly used and allows for further use by the data subject.
RightToPortability
Consent given under special circumstances, such as to the processing of personal data of a child or to the processing of sensitive data.
SpecialConsent
DPH s. 3.3.2 A controller holding personal information shall not use that information without taking steps to ensure with reasonable certainty that the data are accurate and up to date.
Accuracy
dataName
dataSubjectId
ReligionData
EUTransfer
TradeUnionData
RacialData
SexualData
ECHRLawfulness
NonEUTransfer
HealthcareData
BeliefData
CharterLawfulness
GeneticData
PoliticalData
CriminalData
BiometricData
supervises
performProcessing
exerciseRight
implements
requiredByPublicInterest
mustProvide
appoints
processingAppliesTo
hasPersonalData
requiredByVitalInterest
objectTo
accessData
issueFine
isObjected
hasParties
transferContent
requiredByObligation
processingHasRequirement
processingPerformedBy
hasObligation
requiredByLegitimateInterest
usesProcessingMode
hasParent
specialConsentAppliesTo
cooperateWith
dataWasBreached
hasRecipient
hasVitalInterest
hasGrantedConsent
hasLegitimateInterest
processOnBehalfOf
consentAppliesTo
processingGrantsRight
notifyBreach
requiredForContract
requirementAppliesTo
consentGrantedBy
breachNotifiedTo
pertainsTo
transferHasRequirement
performAccess
date
closeMatch
note
exactMatch
broaderTransitive
broadMatch