Skip to content

Commit

Permalink
adds IntendedUse to TECH, revises TECH concepts
Browse files Browse the repository at this point in the history 
- adds IntendedUse and hasIntendedUse to indicate the goal or purpose of
  technology without conflicting with other DPV concepts such as Purpose
  while still permitting flexibility in use; closes #85
- completes revision of cloud concepts; closes #47
  • Loading branch information
@coolharsh55
coolharsh55 committed May 23, 2024
1 parent 82b6235 commit df06291
Show file tree
Hide file tree
Showing 54 changed files with 15,558 additions and 13,880 deletions.
92 changes: 33 additions & 59 deletions code/jinja2_resources/template_tech.jinja2
View file
Original file line number Diff line number Diff line change
Expand Up @@ -64,33 +64,38 @@
</head>
<body>
<section id="abstract">
<p>The [[[DPV]]] provides a rich taxonomy of concepts which includes <i>Technology</i>. While it enables expression of how some technology is applied within the context of personal data and its processing, there is a need for further specific details regarding technologies, their management, and relevance to actual real-world tools and systems. DPV-TECH provides such concepts associated with Technologies as an extension to DPV concepts.</p>
<p>The namespace for terms in dpv-tech is <a href="http://www.w3id.org/dpv/dpv-tech#"><code>https://www.w3id.org/dpv/dpv-tech#</code></a><br/>
The suggested prefix for the namespace is <code>dpv-tech</code><br/>
The DPV-TECH vocabulary and its documentation is available on <a href="https://github.com/w3c/dpv">GitHub</a>.</p>
<p>The [[[DPV]]] provides a rich taxonomy of concepts which includes <i>Technology</i>. While it enables expression of how some technology is applied within the context of personal data and its processing, there is a need for further specific details regarding technologies, their management, and relevance to actual real-world tools and systems. TECH provides such concepts associated with Technologies as an extension to DPV concepts.</p>
<p>The namespace for terms in tech is <a href="http://w3id.org/dpv/tech#"><code>https://w3id.org/dpv/tech#</code></a><br/>
The suggested prefix for the namespace is <code>tech</code><br/>
The TECH vocabulary and its documentation is available on <a href="https://github.com/w3c/dpv">GitHub</a>.</p>

<div class="issue" title="WARNING: unstable vocabulary" data-number="47">
<p><strong>WARNING</strong> This vocabulary will be undergoing major changes based on the necessity to specify cloud technology concepts and to ensure provided concepts are useful. There may be extensive removal/additions of concepts that changes the structure and semantics of this extension.</p>
</div>

{{ dpv_document_family(document='dpv-tech-spec') }}
{{ dpv_document_family(document='tech-spec') }}
{{ sotd() }}
</section>
<section id="overview-core">
<section id="vocab-core">
<h2>Core Concepts</h2>
<p>The concept concepts provided in DPV-TECH include subtypes of `dpv:Technology` as [=DataTechnology=], [=OperationalTechnology=] (as in relating to operations or processes), [=SecurityTechnology=], [=IdentityTechnology=], [=ManagementTechnology=], and [=SurveillanceTechnology=]. These enable expression of the <i>role</i> of a particular technology within the context of personal data processing.</p>
<p>To indicate how technology was provided or is used, the concept [=ProvisionMethod=] and relation [=hasProvisionMethod=] are useful. It enables expression of where technology is used as a Product or Subscription (e.g. from a vendor), or as a System or a Component (e.g. standalone).</p>
<p>The concept [=CommunicationMechanism=] and relation [=hasCommunicationMechanism=] enables expressing how the technology communicates, such as by use of Internet, Cellular Networks, GPS, etc.</p>
<p>To indicate entities or actors associated with the Technology and their specific roles, the concept [=Actor=] and associated relations are useful.</p>
<p>To represent <i>location</i> of technology use, the existing DPV concepts related to location can be used, i.e. `dpv:Location` and `dpv:hasLocation` along with its various types and contextually relevant concepts. To explicitly refer to location as associated with use of technology, the concept [=UsageLocation=] is provided. For example, to indicate that some technology (whose actual location is on a server) is used in an office. Some synonyms used to indicate <i>usage location</i> for similar information are: application, deployment, or operation.</p>
<p>To indicate the maturity of a technology, the concept [=ReadinessLevel=] and relation [=hasTRL=] are useful. This information can be based on standards, such as the <a href="https://www.iso.org/standard/56064.html">ISO 16290:2013</a>, or those provided by other bodies and domains.</p>

{{ list_hierarchy(modules['core']['classes']) }}
</section>
<section id="overview-types">
<h2>Types of Technologies</h2>


<section id="vocab-actors">
<h2>Actors involved in Technologies</h2>
<p>To specify the specific actors and their roles in the context of technologies, [=Actor=] is provided along with the following specific roles as its subtypes:</p>
<ul>
<li>[=Developer=] and [=hasDeveloper=] specifies who develops or has developed the technology.</li>
<li>[=Provider=] and [=hasProvider=] specifies who provides the technology. This could be the same entity as developer, or a different one - such as when the technology is repackaged or modified before provision.</li>
<li>[=User=] and [=hasUser=] specifies who uses or is the user for the technology. Note that while this refers to <i>users</i> in the technical sense of the term, such users may or may not be <i>data subjects</i>. For example, a technology used by an immigration officer has that officer as the user, rather than the immigrating person. To be more explicit, <i>technology user</i> and <i>whom the technology is used on</i> are two different criterias. See distinction below.</li>
<li>[=Subject=] and [=hasSubject=] is the <i>subject</i> of the technology i.e. whom the technology is used on or subjected to. This may be directly (e.g. person within a CCTV camera's vision) or indirectly (e.g. person whose details were used as training data). What is considered a subject may be contextually dependant on the nature and scope of the technology as well as its application. In the future, we may separate this concept for further distinction between direct and indirect subjects (or use alternate terms) - if such categorisation is deemed beneficial in the description of individuals subjected to technologies.</li>
</ul>
<p>Note, that the technology actor concepts are based on the EU's proposal for AI reguation (i.e. AI ACT) and its corresponding concepts (e.g. AI Provider, AI Developer). Rather than limiting such concepts for "AI", we have expanded upon their intended meaning to encompass any technology. The concepts from the AI ACT can thus be modelled as subtypes of these.</p>
{{ list_hierarchy(modules['actors']['classes']) }}
</section>

<section id="vocab-intended-use">
<h2>Intended Use</h2>
</section>
<section id="overview-provision">

<section id="vocab-provision">
<h2>Provision of Technology</h2>
<p>The provision of technology can happen via the following methods:</p>
<ul>
Expand All @@ -100,11 +105,9 @@
</ul>
{{ list_hierarchy(modules['provision']['classes']) }}
</section>
<section id="overview-communication">
<h2>Communication used by Technologies</h2>
<div class="issue" title="Fix missing concepts e.g. GPS -> GPSCommunication"></div>
<div class="issue" title="Fix incorrect parents e.g. BluetoothCommunication -> NetworkingCommunication"></div>
<div class="issue" title="Fix missing concept e.g. LocalStorage does not exist"></div>

<section id="vocab-comms">
<h2>Networking &amp; Communication</h2>
<p>Communication mediums or mechanism used by technology include:</p>
<ul>
<li>[=GPS=] or the location providing Global Positioning System or its equivalent technologies.</li>
Expand All @@ -114,48 +117,19 @@
{{ list_hierarchy(modules['comms']['classes']) }}
</ul>
</section>
<section id="overview-actors">
<h2>Actors involved in Technologies</h2>
<p>To specify the specific actors and their roles in the context of technologies, [=Actor=] is provided along with the following specific roles as its subtypes:</p>
<ul>
<li>[=Developer=] and [=hasDeveloper=] specifies who develops or has developed the technology.</li>
<li>[=Provider=] and [=hasProvider=] specifies who provides the technology. This could be the same entity as developer, or a different one - such as when the technology is repackaged or modified before provision.</li>
<li>[=User=] and [=hasUser=] specifies who uses or is the user for the technology. Note that while this refers to <i>users</i> in the technical sense of the term, such users may or may not be <i>data subjects</i>. For example, a technology used by an immigration officer has that officer as the user, rather than the immigrating person. To be more explicit, <i>technology user</i> and <i>whom the technology is used on</i> are two different criterias. See distinction below.</li>
<li>[=Subject=] and [=hasSubject=] is the <i>subject</i> of the technology i.e. whom the technology is used on or subjected to. This may be directly (e.g. person within a CCTV camera's vision) or indirectly (e.g. person whose details were used as training data). What is considered a subject may be contextually dependant on the nature and scope of the technology as well as its application. In the future, we may separate this concept for further distinction between direct and indirect subjects (or use alternate terms) - if such categorisation is deemed beneficial in the description of individuals subjected to technologies.</li>
</ul>
<p>Note, that the technology actor concepts are based on the EU's proposal for AI reguation (i.e. AI ACT) and its corresponding concepts (e.g. AI Provider, AI Developer). Rather than limiting such concepts for "AI", we have expanded upon their intended meaning to encompass any technology. The concepts from the AI ACT can thus be modelled as subtypes of these.</p>
{{ list_hierarchy(modules['actors']['classes']) }}
</section>


<section id="docs">
<h2>Docs</h2>
<section id="vocab-docs">
<h2>Documentation</h2>
{{ list_hierarchy(modules['docs']['classes']) }}
</section>

<section id="status">
<section id="vocab-status">
<h2>Status</h2>
{{ list_hierarchy(modules['status']['classes']) }}
</section>

<!-- <section id="contributions">
<h2>Expanding the Taxonomy</h2>
<section id="contributions-sources">
<h2>Sources of Information</h2>
<p>To expand on this list of concepts, we are looking for specific taxonomies related to technologies, and their application in specific areas - such as for security. For this, the following sources may be relevant:</p>
<ul>
<li><a href="https://www.enisa.europa.eu/">European Union Agency for Cybersecurity (ENISA)</a> publishes documents detailing specific technologies and their applications relevant to cybersecurity.</li>
</ul>
</section>
<section id="contributions-concepts">
<h2>Concepts of Relevance</h2>
</section>
<section id="contributions-applications">
<h2>Applications of Concepts</h2>
</section>
</section> -->


<section id="tools">
<section id="vocab-tools">
<h2>Tools</h2>
<div class="issue" title="Content missing - Tools"></div>

Expand Down
2 changes: 1 addition & 1 deletion code/vocab_csv/tech-core-properties.csv
View file
Original file line number Diff line number Diff line change
Expand Up @@ -5,7 +5,7 @@ hasProvisionMethod,has provision method,Specifies the provision or usage method
hasDeploymentLocation,has deployment location,Specifies the location of technology deployment and use,dpv:Technology,tech:DeploymentLocation,dpv:Relation,,,,,2024-05-09,,accepted,Harshvardhan J. Pandit,,,,,,,,,,,,,,
hasCapability,has capability,Indicates the capability of the technology,dpv:Technology,tech:Capability,dpv:Relation,,,,,2024-05-09,,accepted,,,,,,,,,,,,,,,
hasFunction,has function,Indicates the function of the technology,dpv:Technology,tech:Function,dpv:Relation,,,,,2024-05-09,,accepted,,,,,,,,,,,,,,,
,,,,,,,,,,,,,,
hasIntendedUse,has intended use,Indicates the intended use of technology,dpv:Technology,tech:IntendedUse,dpv:Relation,,,,,2024-05-22,,accepted,Harshvardhan J. Pandit,https://w3id.org/dpv/meetings/meeting-2024-05-22,,,,,,,,,,,,,
,,,,,,,,,,,,,,

,,,,,,,,,,,,,,
Expand Down
1 change: 1 addition & 0 deletions code/vocab_csv/tech-core.csv
View file
Original file line number Diff line number Diff line change
Expand Up @@ -10,3 +10,4 @@ CommunicationMechanism,Communication Mechanism,Communication mechanism used or p
Capability,Capability,Expression of what the technology is capable of achieving or providing,dpv:Concept,sc,,,,"Examples of capabilities are image recognition, sentiment analysis, machine translation",,2024-05-09,,accepted,,,,,,,,,,,,,,,,,
Function,Function,Expression of what goals or purposes the technology's capabilities are being used towards or developed for,dpv:Concept,sc,,,,"Function is a broad concept that can include purposes such as identify verification, capability such as image recognition, or specific security measures such as encryption",,2024-05-09,,accepted,,,,,,,,,,,,,,,,,
Documentation,Documentation,"Information describing use, functionality, design, or other technical aspects of the Technology",dpv:Concept,sc,,,,,,2024-05-09,,accepted,,,,,,,,,,,,,,,,,
IntendedUse,Intended Use,Describes the 'intended' use of the technology,dpv:Concept,sc,,,,"Intended use can be used to describe how the developer or provider of technology intends it to be used e.g. use a database to store data, and to describe the plan or 'intent' to use the technology by a user or operator e.g. use a database to store and analyse data. Intended Use can involve any concept e.g. DPV's purpose, processing, tech/org measures, and can be low-level purely technical uses such as store data or high-level goals such as legal compliance. Intended Use only describes the intent or ex-ante intention, and may be different from how the technology is being actually used - which is indicated by using isImplementedUsingTechnology in a procss or other relevant context. ",,2024-05-22,,accepted,Harshvardhan J. Pandit,https://w3id.org/dpv/meetings/meeting-2024-05-22,,,,,,,,,,,,,,,
4 changes: 2 additions & 2 deletions code/vocab_csv/tech-provision.csv
View file
Original file line number Diff line number Diff line change
Expand Up @@ -17,8 +17,8 @@ SaaS,Software as a Service,Technology provided as a cloud service consisting of
CaaS,Compute as a Service,Technology provided as a cloud service consisting of managed compute resources,tech:CloudService,tech:TechnologyProvisionMethod,,,,,,2024-05-09,,accepted,,,,,,,,,,,,,,,,,
MBaaS,Mobile backend as a Service,Technology provided as a cloud service consisting of managed 'backend' services for mobile users,tech:CloudService,tech:TechnologyProvisionMethod,,,,,,2024-05-09,,accepted,,,,,,,,,,,,,,,,,
ServerlessComputing,Serverless Computing,Technology provided as a cloud service consisting of fully managed servers for executing functions,tech:CloudService,tech:TechnologyProvisionMethod,,,,,,2024-05-09,,accepted,,,,,,,,,,,,,,,,,
PrivateCloudService,Private Cloud Service,Technology provided as a cloud service that is private,,tech:TechnologyProvisionMethod,,,,,,2024-05-09,,accepted,,,,,,,,,,,,,,,,,
PublicCloudService,Public Cloud Service,Technology provided as a cloud service that is public,,tech:TechnologyProvisionMethod,,,,,,2024-05-09,,accepted,,,,,,,,,,,,,,,,,
PrivateCloudService,Private Cloud Service,Technology provided as a cloud service that is private,tech:CloudService,tech:TechnologyProvisionMethod,,,,,,2024-05-09,,accepted,,,,,,,,,,,,,,,,,
PublicCloudService,Public Cloud Service,Technology provided as a cloud service that is public,tech:CloudService,tech:TechnologyProvisionMethod,,,,,,2024-05-09,,accepted,,,,,,,,,,,,,,,,,
HybridCloudService,Hybrid Cloud Service,Technology provided as a cloud service that is both private and public in parts,"tech:PrivateCloudService,tech:PublicCloudService",tech:TechnologyProvisionMethod,,,,,,2024-05-09,,accepted,,,,,,,,,,,,,,,,,
,,,,,,,,,,,,,,
,,,,,,,,,,,,,,
Expand Down
Binary file modified code/vocab_csv/tech.xlsx
View file
Binary file not shown.
Loading

0 comments on commit df06291

Please sign in to comment.