You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: draft-howe-vcon-lifecycle.md
+6-8Lines changed: 6 additions & 8 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -189,7 +189,7 @@ By combining vCons with SCITT, organizations can build scalable, transparent gov
189
189
These relying parties can then use this information to make decisions
190
190
based on the current state and context of the vCon to account for changes
191
191
in consent, updates in the accuracy of the content, or amendments of the
192
-
information it might contain.
192
+
information it might contain.
193
193
SCITT, the Supply Chain, Integrity, Transparency, and Trust protocol,
194
194
enables clients to register statements about events, physical or virtual,
195
195
such as when things are created or used.
@@ -204,7 +204,7 @@ governance across security boundaries is common and desired by all
204
204
parties. One real-world example of this is management of consent as
205
205
it applies to the use of conversations for different purposes,
206
206
such as machine learning. Using conversations as inputs to machine
207
-
learning has great benefit to both customers and businesses, yet only
207
+
learning has great benefit to both customers and businesses, yet only
208
208
responsibly within the defense of
209
209
personal data rights and compliance with personal data and
210
210
communications privacy laws, united together
@@ -303,7 +303,7 @@ processing and enhancements. A conserver doesn't store a vCon, rather it process
303
303
the vCon for transcription, sentiment, integrity protection on egress, verification
304
304
on ingress, retrieving it from, and saving it to a vCon Registry.
305
305
306
-
**Data Subject**: The individual(s) whose personal information is processed
306
+
**Data Subject**: The individual(s) whose personal information is processed
307
307
(also referred to as the "consumer" in many personal data privacy laws).
308
308
309
309
**Data Originator**: The Entity that records and initiates the vCon,
@@ -329,7 +329,7 @@ responsibility to identify.
329
329
authority over data processing who determines the purposes and
330
330
methods of data processing, bears primary responsibility under
331
331
privacy laws and is the main target of most privacy and data
332
-
protection regulations. Under most data privacy laws, Data Controllers
332
+
protection regulations. Under most data privacy laws, Data Controllers
333
333
are required to enter into data processing agreements with their Data Processors, detailing the rules for data collection and processing in accordance with applicable laws.
334
334
335
335
@@ -641,8 +641,8 @@ stored on SCITT to provide context for the vCon's intent at specific points in t
641
641
642
642
# Security Considerations
643
643
644
-
The security of the vCon lifecycle depends heavily on the integrity and availability of the SCITT
645
-
Transparency Service. Entities MUST ensure that their SCITT implementations are properly
644
+
The security of the vCon lifecycle depends heavily on the integrity and availability of the SCITT
645
+
Transparency Service. Entities MUST ensure that their SCITT implementations are properly
646
646
secured and that access controls are in place to prevent unauthorized modifications.
647
647
648
648
The handling of personally identifiable information (PII) throughout the vCon lifecycle
@@ -684,7 +684,5 @@ This document has no IANA actions.
684
684
685
685
# Acknowledgments
686
686
687
-
{:numbered="false"}
688
-
689
687
* Thank you to Allistair Woodman for connecting the first dots between VCon and SCITT
690
688
* Thank you to Jeff Pulver and Cody Launius for their collaboration and support
0 commit comments