- From: Rob Atkinson via GitHub <sysbot+gh@w3.org>
- Date: Wed, 15 Feb 2023 10:41:31 +0000
- To: public-dxwg-wg@w3.org
Actually, there is an issue we are looking at fixing.. the OGC document may define multiple "conformanceClasses" that are the specifications that things actually "conformTo" - so the best statement would be one that references such a conformance class. (OGC still needs to make a call whether specifications that pre-date the identification of formal conformance classes should declare the document URL as a sort of proxy conformanceClass or mint a register of conformanceClass objects that reference these legacy specifications.) For clarity, a up-to-date reference using OGC API might be better... as in this example: https://docs.opengeospatial.org/is/17-069r3/17-069r3.html#_declaration_of_conformance_classes NB OGC is about to charter a GeoDCAT profile - and I think it may make sense to define an GeoDCAT-OGC sub-profile that constrains conformsTo to include a reference to an OGC conformanceClass declaration. -- GitHub Notification of comment by rob-metalinkage Please view or discuss this issue at https://github.com/w3c/dxwg/issues/1435#issuecomment-1431122440 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 15 February 2023 10:41:33 UTC