Open pvretano opened 2 years ago
Transformation scripts to/from ISO 19139 are at https://github.com/ISO-TC211/XML/tree/master/standards.iso.org/iso/19115/resources/transforms/ISO19139
We in the antipodes would be most keen if this work would be in alignment with 19115-3 rather than 19139. Gobe, I am not sure the repository you reference is up to date. The namespaces reference “http”//standards.iso.org http://standards.iso.org/” rather than the newer "https://schemas.isotc211.org https://schemas.isotc211.org/”. Perhaps Evert can comment?
Cheers, Byron
On 28/06/2022, at 5:03 AM, ghobona @.***> wrote:
Transformation scripts to/from ISO 19139 are at https://github.com/ISO-TC211/XML/tree/master/standards.iso.org/iso/19115/resources/transforms/ISO19139 https://github.com/ISO-TC211/XML/tree/master/standards.iso.org/iso/19115/resources/transforms/ISO19139 — Reply to this email directly, view it on GitHub https://github.com/opengeospatial/ogcapi-records/issues/174#issuecomment-1167461087, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAIJCPFPLXSXXPFP7IA25CLVRHNGDANCNFSM5Z65KW4Q. You are receiving this because you are subscribed to this thread.
@ejbleys Please comment about the namespaces referenced by https://github.com/ISO-TC211/XML/tree/master/standards.iso.org/iso/19115/resources/transforms/ISO19139
The namespaces referred to in the transforms for XMLs from ISO 19139 to ISO 19115-1 (XML version 1.0) uses the namespaces http://standards.iso.peg/iso (as does version 2.0) irrespective of schemas location. The more recent schemas (version 1.3) use namespaces that better align with the schema locations but there need not be a relationship between namespace and location, just consistency (including of content) Preliminary transforms from v1.0 & v2.0 to v1.3 can be found in GitHub XML … schemas.isotc211.org/…/19115/Resources/…
Note: I’m still traveling so have no access to documentation or tools Cheers Evert Evert Bleys 4 Tudor Place HUGHES ACT Australia Mob: 0411 483 876
On 14 Sep 2022, at 18:43, ghobona @.***> wrote:
@ejbleys Please comment about the namespaces referenced by https://github.com/ISO-TC211/XML/tree/master/standards.iso.org/iso/19115/resources/transforms/ISO19139
— Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you were mentioned.
12-DEC-2022: TC-211 disussed at the recent meeting (Stockholm meeting) doing an experimental JSON encoding for ISO19115 but this will take some time. It could be worthwihle waiting for that for providing input to that. There is also the automatically generate JSON encoding for ISO19115 from pycsw that could be considered too.
FYI: https://docs.ogc.org/bp/17-084r1/17-084r1.html proposes a GeoJSON (JSON-LD) encoding of a significant part of ISO19115 aligned with DCAT/GeoDCAT-AP.
Note that GeoDCAT-AP is a EU scope - and there is a significant interest in the OGC undertaking to bring this in-house as a generic (and probably much simpler) geoDCAT - see https://github.com/opengeospatial/geosemantics-dwg/tree/geoDCAT_charter.
The key will be modularity and reusability of LD contexts - i.e. a 19115 profile of GeoJSON should build on several foundation contexts: for GeoJSON, DCAT, GeoDCAT, GeoSPARQL. Possibly a FG-JSON extension as well.
09-JAN-2023: @kalxas did a quick review of https://github.com/opengeospatial/geosemantics-dwg/tree/geoDCAT_charter and it looks very promising. @cportele mentioned that at the last TC211 meeting there was disucssion about a JSON encoding for ISO19115 but nothing has started yet. Satish S. mentioned this effort: https://www.fgdc.gov/metadata/events/iso-metadata-summit-2017/alaskaconsortiummetadatatoolkit-bradleywalworthsmi.pdf and https://www.fgdc.gov/metadata/events/iso-metadata-summit-2017/alaskaconsortiummetadatatoolkit-bradleywalworthsmi.pdf. @pvretano mentioned that there are a lots of efforts to get a JSON encoding of ISO19115 but they don't seem to be coordinated. @cportele mentioned that it would probably be in out best interest to NOT start "new" work but wait and see how all these efforts pan out. Homework for next meeting is that anyone interested in this topic is to review @rob-metalinkage (and other references).
31-MAR-2023: Apparently according to emails received by @pvretano and @kalxas , ISO is starting the work on a JSON encoding for 19115. This is good new for this WIP. @pvretano and @kalxas will see if there is any publically available information and report back. There is a draft PDF "Draft ISO/TR 19115-4 Geographic information – Metadata – Part 4: JSON schema implementation of metadata fundamentals" that is being reviewed.
The CDB SWG would also be interested in Part4 - relevant to the CDB 2.0 work. CDB 2.0 recommends use of JSON for all controlled vocabularies, enumerations, and most dataset metadata. Thanks!
GeoDCAT is now active. An OGC-API Records implementation profile is being prepared at https://github.com/ogcincubator/geodcat-ogcapi-records/
08-JUL-2024: There is an ISO project (19115-4) that is supposed to deliver a JSON encoding of ISO19115 by the end of the year.
An update from the recent TC 211 meeting is that the JSON encoding will not be completed in 2024.
@ghobona - Based on what I know and what we discussed in the project team this week, the plan is to have a complete draft for the November 2024 plenary meeting. I think there is a hard ISO deadline coming up in early 2025. How complete or final the work will be is another topic.
The purpose of this issue to summarize the discussion in the SWG (27-JUN-2022) about developing a GeoJSON encoding of ISO19115 metadata as the description of a "dataset". this is related to the work understaken be @cholmes in this https://github.com/opengeospatial/ogcapi-records/pull/130 but it is not not clear yet whether the work done in for this proposed work item could also satisfy the requirements in pull request #130.
In the meeting we discussed:
So the work item is to develop the GeoJSON encoding for the dataset portion of ISO19115. We will start with OARec core queryables and expand from there to cover the dataset portion of ISO19115. We will only concentrate on the dataset part of ISO19115 since the SWG felt that the server portion is already covered in OGC APIs using OpenAPI.
There is an opportunity at the Sept. code sprint to advance this work since that code sprint is a joint sprint between OGC and ISO.