<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<div class="moz-cite-prefix">Hi all,<br>
<br>
OGC API Records has landed in master today.<br>
<a class="moz-txt-link-freetext" href="https://github.com/geopython/pycsw/pull/686">https://github.com/geopython/pycsw/pull/686</a><br>
<br>
Best,<br>
Angelos<br>
<br>
On 3/21/21 8:34 PM, Tom Kralidis wrote:<br>
</div>
<blockquote type="cite"
cite="mid:CAFWXLWVZxLy+HLDYaCFJPKCC6FYc-U+R95seAYEf3qiHSuYRRw@mail.gmail.com">
<pre class="moz-quote-pre" wrap="">Hi all: hope everything is well with you during these times.
We'd like to provide an update on pycsw status and the emerging
OGC API - Records specification. For those who may not be aware,
OARec is part of the OGC API effort [1] to modernize API standards
in order to help lower the barrier to implementation. OARec is the natural
successor to OGC CSW (similar to OGC API - Feature being the
same for OGC WFS) and fits into the pycsw scope and roadmap.
OARec has seen considerable progress in the last 6 months in
support of moving ahead for public comment as well as the
eventual formal specification (note that Angelos and myself are
part of the OARec Standards Working Group).
Given the current state of OARec (endpoints, core record model)
we have decided that the time is right to move ahead and implement
in pycsw proper.
We have started implementing the feature branch in [2] and have a
working product based on the existing pycsw architecture (configuration,
repository, etc.). Note that the goal here would be for pycsw to support
all its current interfaces so a user can support both OARec and the
current interfaces (CSW, OpenSearch, etc.) as part of their deployment.
As with CSW2/3, we will also target pycsw as an OARec Reference
Implementation.
For those who are interested, we are tracking this feature in [3]. Note
that we will also put forth an RFC for PSC review/vote.
This feature is a long time coming, and now is the right time to start
to implement and harden in pycsw. OARec will be a core part of
the OGC geospatial search capability, and is critical path for the pycsw
roadmap and functionality for the long term.
If you have any questions or comments, please feel free to reach out
here, IRC or Gitter.
Thanks
..Tom
[1] <a class="moz-txt-link-freetext" href="https://ogcapi.ogc.org">https://ogcapi.ogc.org</a>
[2] <a class="moz-txt-link-freetext" href="https://github.com/geopython/pycsw/tree/oarec">https://github.com/geopython/pycsw/tree/oarec</a>
[3] <a class="moz-txt-link-freetext" href="https://github.com/geopython/pycsw/issues/670">https://github.com/geopython/pycsw/issues/670</a>
</pre>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<pre class="moz-quote-pre" wrap="">_______________________________________________
pycsw-devel mailing list
<a class="moz-txt-link-abbreviated" href="mailto:pycsw-devel@lists.osgeo.org">pycsw-devel@lists.osgeo.org</a>
<a class="moz-txt-link-freetext" href="https://lists.osgeo.org/mailman/listinfo/pycsw-devel">https://lists.osgeo.org/mailman/listinfo/pycsw-devel</a>
</pre>
</blockquote>
<br>
<br>
<pre class="moz-signature" cols="72">--
Angelos Tzotsos, PhD
President
Open Source Geospatial Foundation
<a class="moz-txt-link-freetext" href="http://users.ntua.gr/tzotsos">http://users.ntua.gr/tzotsos</a></pre>
</body>
</html>