Contribution RDM-2025-0070-TS-0002_v5_4_0_baseline merged into R5

Original contribution: RDM-2025-0070-TS-0002_v5_4_0_baseline

See merge request !10

TS-0002-oneM2M-Requirements.md

@@ -3,9 +3,9 @@
 
 | **oneM2M**<br />**Technical Specification** | **oneM2M**<br />**Technical Specification**                  |
 | ------------------------------------------- | ------------------------------------------------------------ |
-| Document Number                             | TS-0002-V5.3.0                                               |
+| Document Number                             | TS-0002-V5.4.0                                               |
 | Document Name:                              | Requirements                                                 |
-| Date:                                       | 2024-06-27                                                  |
+| Date:                                       | 2024-11-21                                                   |
 | Abstract:                                   | The present document contains an informative functional role model and normative technical requirements for oneM2M. |
 
 This Specification is provided for future development work within oneM2M only. The Partners accept no liability for any use of this Specification.
@@ -709,13 +709,11 @@ NOTE3: The solution would be complete and will be a part of the oneM2M core func
 |SER-082<br />See ARC--2018-0062 |The oneM2M System shall support M2M Service Subscriber and M2M Service User profiles specifying their restrictions (e.g. privacy restrictions, max number and/or types of applications and devices the M2M Service Subscriber and its authorized M2M Service Users are allowed to register to the M2M System, the maximum number of resources or bytes of data that the M2M Service Subscriber can store in the M2M System, etc.) and their default configurations (e.g. access control policies, expiration times, max number of content instances, etc.). | |
 |SER-083<br />See RDM-2019-0054R01 |The oneM2M System shall support access control and authorization mechanisms for the M2M Service Subscriber or M2M Service User information, based on dynamic parameters (e.g. on/off duty time schedule, location, role or job position etc.). |Rel-4 |
 |SER-084<br />See RDM-2019-0054R01 | The oneM2M System shall be able to access M2M Service Subscriber information or M2M Service User information based on dynamic parameters (e.g. on/off duty time schedule, location, role or job position, etc.) from M2M Applications. |Rel-4 |
-<<<<<<< TS-0002-oneM2M-Requirements.md
 |SER-085<br />See TR-0062 | The oneM2M System shall support the ability to apply pseudonymisation and anonymisation techniques to data based on specified privacy preferences, ensuring compliance with applicable privacy regulations (e.g., GDPR) and protecting data subject identity. |Rel-4 |
 |SER-086<br />See TR-0062 | The oneM2M System shall ensure that "additional information" used for pseudonymisation is securely stored and access-controlled, allowing only authorized entities to link pseudonymised data back to the data subject while maintaining separation from the main data set. |Rel-4 |
 |SER-087<br />See TR-0062 | The oneM2M System shall be able to store, manage and access user's consent information for data processing activities associated with oneM2M resources in compliance with requirements from relevant regulations. |Rel-4 |
 |SER-088<br />See TR-0062 | The oneM2M System shall provide mechanisms for managing consent information, including the ability to update or withdraw consent, specify the scope and purpose of processing activities, and associate each processing activity with one or more oneM2M resources. |Rel-4 |
 |SER-089<br />See TR-0062 | The oneM2M System shall provide mechanisms to immediately delete privacy-related data upon request from the data owner, supporting the "right to be forgotten" as required by regulations like the GDPR and Personal Information Protection Act. |Rel-4 |
->>>>>>> TS-0002-oneM2M-Requirements.md
 
 NOTE 1:    The above requirement does not cover items outside of the oneM2M System, e.g. Underlying Networks.
 
@@ -874,6 +872,9 @@ The requirements contained in this Annex are gathered and targeted for the next
 |V5.1.0 |26-Sep-2022 |This baseline including agreed CR (from RDM#47 to RDM#55):<br />RDM-2022-0028-requirements\_on\_dataset\_creation\_for\_AI\_models |
 |V5.2.0 |14-Dec-2023 |This baseline including agreed contributions from RDM#56 to RDM#62 for Rel.5:<br />RDM-2023-0006R01-ML\_model\_management\_requirements<br />RDM-2023-0008-Requirements\_for\_AI\_ML\_data\_augmentation<br />RDM-2023-0009R01-Requirements\_for\_the\_management\_of\_AI\_ML\_data<br />RDM-2023-0010R01-Requirements\_for\_distributed\_AI\_ML\_model\_on\_Edge\_Fog\_nodes<br />RDM-2023-0011R01-Requirements\_for\_the\_management\_of\_AI\_ML\_classifiers<br />RDM-2023-0012R01-Requirements\_to\_support\_autonomous\_AI\_ML |
 | V5.2.1 | 03-May-2024 | This baseline converts the document to Markdown format. |
-| V5.3.0 | 2024-06-27 | New baseline |
+| V5.3.0 | 27-Jun-2024 | New baseline |
+| V5.4.0 | 21-Nov-2024 | This baseline including agreed Crs from RDM#67 for Rel.5:<br />RDM-2024-00055-New\_requirements\_for\_privacy\_regulations<br />RDM-2024-00056R01-New\_requirements\_for\_consent\_management<br />RDM-2024-00057-New\_requirements\_for\_data\_ownership\_and\_right\_to\_be\_deleted |
+
+