WGISS 60 edits

Architecture.md

@@ -25,7 +25,7 @@ also the access and usage patterns of data.
 
 | **ID** | **Recommendations** |
 | :-- | :------------ |
-| **DPRES\#1** | Archival systems should comply with the Reference Model for an [Open Archival Information System](https://ccsds.org/wp-content/uploads/gravity_forms/5-448e85c647331d9cbaf66c096458bdd5/2025/01/650x0m3.pdf) (OAIS) and with the forthcoming “OAIS-Interoperability Framework” to facilitate interoperability between archives.                                                   |
+| **DPRES\#1** | Archival systems should comply with the Reference Model for an [Open Archival Information System](https://ccsds.org/wp-content/uploads/gravity_forms/5-448e85c647331d9cbaf66c096458bdd5/2025/01/650x0m3.pdf) (OAIS) and with the “OAIS-Interoperability Framework” to facilitate interoperability between archives.                                                   |
 | **DPRES\#2** | Data should be appraised and properly documented before ingestion in the archives following the [CEOS Data Appraisal Procedure](https://ceos.org/ourwork/workinggroups/wgiss/documents/).                                                                                                                                                                                         |
 | **DPRES\#3** | Data and associated information should be ingested, archived and preserved following internationally recognised standards and best practices (e.g., those produced by [WGISS](https://ceos.org/ourwork/workinggroups/wgiss/documents/) and [Producer-Archive Interface Methodology Abstract Standard](https://public.ccsds.org/Pubs/651x0m1.pdf) ) with any tailoring documented. |
 | **DPRES\#4** | Periodically perform archival system/media upgrade to the most adequate proven technology to ensure data and information long term preservation. Perform migration, with an integrity check, of archived data from old to new systems.                                                                                                                                            |
@@ -47,7 +47,7 @@ This section covers the core recommendations for collection management functions
 | **DATA#5**  | A Collection of data should have all granules packaged consistently and produced with consistent quality.                                                                                                                                                                                                      |
 | **DATA#6**  | Collection-specific metadata formats may be used, but packaging should also include STAC documents at the Collection and Granule/Item level. Refer to the [CEOS EO collection and granule discovery best practices with STAC](https://github.com/ceos-org/stac-collection-and-granule-discovery-best-practices). |
 | **DATA#7**  | Checksums for all files in a packaged granule should be available, to ensure integrity.                                                                                                                                                                                                                        |
-| **DATA#8**  | Where pixel-level metadata is avaliable, such as scene quality masks, these should be clearly documented with a reference to lookup tables.                                                                                                                                                                    |
+| **DATA#8**  | Where pixel-level metadata is available, such as scene quality masks, these should be clearly documented with a reference to lookup tables.                                                                                                                                                                    |
 | **DATA#9**  | File names and folder or path structures should be consistent and include appropriate information to distinguish the specific granule. This could include the platform, time and date of aquisition, band(s), and product version.                                                                             |
 | **DATA#10** | Assign a Persistent Identifier to data archived and published to users and ensure the availability of all associated information in the relevant Landing Page following the [CEOS Persistent Identifiers Best Practice](https://ceos.org/ourwork/workinggroups/wgiss/documents/).                              |
 | **DATA#11** | The CEOS supported [Open Data Cube](https://opendatacube.org) family of software can be taken as a reference Datacube implementation.                                                                                                                                                                          |

Interface.md

@@ -21,7 +21,7 @@ services through the exploitation of standard protocols and the harmonizing of s
 | **DISC\#7** | Resource metadata including keywords should link each keyword to its URI and to the appropriate thesaurus (i.e., controlled vocabularies). |
 | **DISC\#8** | Resource metadata should contain the persistent identifier (e.g., DOI) of the corresponding resource. |
 | **DISC\#9** | Collection metadata should refer to the level of maturity with respect to the [WGISS Data Management and Stewardship Maturity Matrix](https://ceos.org/document_management/Working_Groups/WGISS/Interest_Groups/Data_Stewardship/White_Papers/WGISS%20Data%20Management%20and%20Stewardship%20Maturity%20Matrix.pdf). |
-| **DISC\#10** | For facilitating discovery and access, data shall be organised in collections according to the principles outlined in the `WGISS Data Collections Management Practices White Paper`. |
+| **DISC\#10** | For facilitating discovery and access, data shall be organised in collections according to the principles outlined in the [Shared Collection Lifecycle Management Principles for Earth Observation Data](https://ceos.org/document_management/Working_Groups/WGISS/Documents/Shared%20Collection%20Lifecycle%20Management%20Principles%20for%20Earth%20Observation%20Data_March2025.pdf). |
 
 ## Data Access
 

Policy.md

@@ -13,10 +13,10 @@ Policy is one of the most important factors and forms the basis of interoperabil
 | **POL\#2**| Identify policies in your organization/country related to data and services and conduct periodic check/audit for compliance to these policies. Identify policies which may be barriers to interoperability of data and services and flag them for resolution. Ensure the policies are clearly communicated to stakeholders. |
 | **POL\#3** | **EO Capabilities:** Publish and periodically update information about present and planned Earth observation Satellites in online databases, preferably the [CEOS MIM Database](https://ceos.org/mim-database). This will help in planning and overall coordination among different EO stakeholders. |
 | **POL\#4** | **Open Standards and Specifications:** Ensure your organizations implement open standards and specifications such as those published by the Open Geospatial Consortium [(OGC)](https://www.ogc.org/standards/) for data and services. Drafting of new specifications for data formats, metadata formats and service APIs should be preferably done along with standards organisations, or developed by the open source community. |
-| **POL\#5** | **Open Data:** Organizations should ensure that Earth observation data is discoverable, accessible and proactively made freely available for use, reuse and redistribution to users in human and machine readable form. |
+| **POL\#5** | **Open Data:** Organizations should ensure that Earth observation data is discoverable, accessible and proactively made  available for use, reuse and redistribution to users in human and machine readable form, under an open license (see **POL\#8**). |
 | **POL\#6** | **Open Source Software:** Where possible, share software applications as open source software, enabling others to use the same tools as are used internally to process or transform data products or to demonstrate the use of standards to access your data and services. An example of a preferred license is Apache 2.0. |
 | **POL\#7** | **Open Science:** Promote the concept of open science for collaborative development. Open science ensures availability of the state-of-the-art algorithms and software providing consistent products from different data providers and supporting reproducibility. |
-| **POL\#8** | **Data Licensing:** Organizations sharing open and unrestricted data should license the data using an open source license, consistent with their organisation's policy. A Custom license can restrict access for users. The [GEO data licensing Guidance](<https://gkhub.earthobservations.org/packages/p0zg8-02b56>) can be referenced for examples, including Creative Commons Zero 1.0 Universal Public Domain Dedication (CCo), Open Data Commons Public Domain Dedication and License (PDDL) v1.0, or Creative Commons Attribution 4.0 International (CC BY 4.0). CC BY 4.0 is preferred. |
+| **POL\#8** | **Data Licensing:** Organizations sharing open and unrestricted data should license the data using an open license, consistent with their organisation's policy. A Custom license can restrict access for users. The [GEO data licensing Guidance](<https://gkhub.earthobservations.org/packages/p0zg8-02b56>) can be referenced for examples, including Creative Commons Zero 1.0 Universal Public Domain Dedication (CCo), Open Data Commons Public Domain Dedication and License (PDDL) v1.0, or Creative Commons Attribution 4.0 International (CC BY 4.0). CC BY 4.0 is preferred. |
 | **POL\#9** | **Data Procurement from third party:** Organizations planning to procure/outsource Earth Observation data, to possible extent should ensure that the data complies with CEOS recommendations, including those outlined in this handbook.|
 | **POL\#10** |**Data preservation:** Organizations should ensure that Earth observation data is archived and preserved according to [CEOS best practices](https://ceos.org/ourwork/workinggroups/wgiss/documents/).|
 | **POL\#11** |**Purge Alert:** Organisations should use the [purge alert service](https://ceos.org/ourwork/workinggroups/wgiss/preservation/data-purge-alert/) provided by CEOS WGISS before data and information removal from archives.|