Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Rebuild after #352 #353

Merged
merged 4 commits into from
Oct 28, 2024
Merged

Rebuild after #352 #353

Changes from all commits
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
ed5cba2
Rebuild
HeikoTheissen Oct 28, 2024
65e3d40
auto-refreshed
HeikoTheissen Oct 28, 2024
7f5cfdf
Rebuilt again
HeikoTheissen Oct 28, 2024
0714f90
Merge branch 'fix/rebuild' of [email protected]:SAP/odata-vocabularies.g…
HeikoTheissen Oct 28, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion vocabularies/PersonalData.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -58,7 +58,7 @@ Allowed Value|Description
[DataSubjectIDType](PersonalData.xml#L123) *([Experimental](Common.md#Experimental))*|The type of ID identifying the data subject and which is allocated when creating a consent record, e.g. an e-mail address or a phone number.
[ConsentID](PersonalData.xml#L128) *([Experimental](Common.md#Experimental))*|The unique identifier for a consent<br>A consent is the action of the data subject confirming that the usage of his or her personal data shall be allowed for a given purpose. A consent functionality allows the storage of a consent record in relation to a specific purpose and shows if a data subject has granted, withdrawn, or denied consent.
[PurposeID](PersonalData.xml#L140) *([Experimental](Common.md#Experimental))*|The unique identifier for the purpose of a processing of personal data<br>Any processing of personal data is based on specified, explicit, and legitimate purposes, and data are not further processed in a manner that is incompatible with those purposes. The purposes are defined by the data controller or joint data controllers.
[ContractRelatedID](PersonalData.xml#L149)|The unique identifier for transactional data that is related to a contract that requires processing of personal data<br>Examples:<br/> - Sales Contract ID<br/> - Purchase Contract ID<br/> - Service Contract ID
[ContractRelatedID](PersonalData.xml#L149)|The unique identifier for transactional data that is related to a contract that requires processing of personal data<br>Examples:<br> - Sales Contract ID<br> - Purchase Contract ID<br> - Service Contract ID
[LegalEntityID](PersonalData.xml#L163) *(Deprecated)*|Deprecated in favor of [`DataControllerID`](#DataControllerID)
[UserID](PersonalData.xml#L178) *([Experimental](Common.md#Experimental))*|The unique identifier of a user<br>A user is an individual who interacts with the services supplied by a system.
[EndOfBusinessDate](PersonalData.xml#L186) *([Experimental](Common.md#Experimental))*|Defines the end of active business and the start of residence time and retention period<br>End of business is the point in time when the processing of a set of personal data is no longer required for the active business, for example, when a contract is fulfilled. After this has been reached and a customer-defined residence period has passed, the data is blocked and can only be accessed by users with special authorizations (for example, tax auditors). All fields of type `Edm.Date` or `Edm.DateTimeOffset` on which the end of business determination depends should be annotated.
Expand Down