From cdd8d29349de5766618a99a1e19b8b99e38a5097 Mon Sep 17 00:00:00 2001 From: Esteban Zimanyi Date: Fri, 1 May 2026 17:37:12 +0200 Subject: [PATCH] Add lineage credits: pg_mfserv predecessor, AUTHORS, CITATION MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit MobilityAPI's working tree is the result of two distinct contribution phases that today's repo doesn't make visible: 1. **pg_mfserv (March 2024)** — the founding OGC API – Moving Features Python server for MobilityDB, authored at ULB. - Maxime Schoemans (@mschoema) — initial commit, endpoint design. - Victor Morabito (@MrMaxime1er) — main developer of the pg_mfserv codebase: column discovery, request handling, exception handling, route refactors. 2. **MobilityAPI (2025–)** — the current production-grade implementation, also at ULB. - Sirine Meraoui (@sirimeraoui) — current maintainer; structured resource layout, tests, OGC conformance, documentation. This commit adds three artefacts that surface the lineage: - **README.md** — new `## History and Acknowledgements` section before `## License` crediting all three contributors and pointing to pg_mfserv as the archived predecessor. - **AUTHORS.md** (new) — structured contributor list per phase. - **CITATION.cff** (new) — machine-readable citation metadata for Zenodo / GitHub citation widget, including a `references:` block citing pg_mfserv as predecessor work. License declared in CITATION.cff: PostgreSQL (matching the MobilityDB main project's license posture). The lineage credit is symmetric: pg_mfserv's README will gain an archive banner pointing forward to MobilityAPI in the companion PR on the pg_mfserv repository. Co-Authored-By: Claude Opus 4.7 (1M context) --- AUTHORS.md | 26 ++++++++++++++++++++++++++ CITATION.cff | 49 +++++++++++++++++++++++++++++++++++++++++++++++++ README.md | 15 +++++++++++++++ 3 files changed, 90 insertions(+) create mode 100644 AUTHORS.md create mode 100644 CITATION.cff diff --git a/AUTHORS.md b/AUTHORS.md new file mode 100644 index 0000000..50b69a3 --- /dev/null +++ b/AUTHORS.md @@ -0,0 +1,26 @@ +# Authors + +MobilityAPI is the result of contributions from several individuals across two phases. The project's lineage starts with **pg_mfserv** (2024), an OGC API – Moving Features prototype that established the Python-server skeleton and the PyMEOS-based MobilityDB integration pattern. **MobilityAPI** (2025–) extends that foundation into a production-grade implementation with a structured resource layout, comprehensive tests, and OGC conformance. + +## Founding phase (2024) — as `pg_mfserv` + +Affiliated with [Université libre de Bruxelles (ULB)](https://www.ulb.be/). + +- **Maxime Schoemans** ([@mschoema](https://github.com/mschoema)) — initial commit, OGC API – Moving Features endpoint design, project skeleton. +- **Victor Morabito** ([@MrMaxime1er](https://github.com/MrMaxime1er)) — main developer of pg_mfserv: column discovery, request/response handling, exception handling, route refactors, feature endpoints (collections, items, temporal geometry, temporal properties). + +The pg_mfserv repository is preserved at [`MobilityDB/pg_mfserv`](https://github.com/MobilityDB/pg_mfserv) in archived form. + +## Current phase (2025–) — as `MobilityAPI` + +Affiliated with [Université libre de Bruxelles (ULB)](https://www.ulb.be/). + +- **Sirine Meraoui** ([@sirimeraoui](https://github.com/sirimeraoui)) — current maintainer; structured resource layout (`resource/` tree); test infrastructure; OGC conformance; HTTP-status-code translation; documentation; demo notebooks; AIS dataset integration. + +## Acknowledgements + +The project benefits from the broader [MEOS ecosystem](https://libmeos.org/), in particular: + +- **[PyMEOS](https://github.com/MobilityDB/PyMEOS)** — the Python binding of MEOS that MobilityAPI consumes today. +- **[MobilityDB](https://github.com/MobilityDB/MobilityDB)** — the PostgreSQL extension providing the SQL surface backing MobilityAPI. +- **[OGC API – Moving Features Standard](https://docs.ogc.org/is/22-003r3/22-003r3.html)** — the standard MobilityAPI implements. diff --git a/CITATION.cff b/CITATION.cff new file mode 100644 index 0000000..9050189 --- /dev/null +++ b/CITATION.cff @@ -0,0 +1,49 @@ +cff-version: 1.2.0 +title: MobilityAPI +type: software +message: "If you use MobilityAPI in academic or technical work, please cite it using the metadata below." +abstract: >- + MobilityAPI is an OGC API – Moving Features Standard reference + implementation for MEOS-stored mobility data. It provides REST + endpoints (GET / POST / PUT / DELETE) over collections of moving + features, suitable for HTTP-driven clients consuming MobilityDB + trajectories. + +authors: + - family-names: Meraoui + given-names: Sirine + affiliation: Université libre de Bruxelles (ULB) + +repository-code: "https://github.com/MobilityDB/MobilityAPI" +url: "https://libmeos.org/bindings/mobilityapi/" + +keywords: + - mobility + - trajectory + - ogc-api + - moving-features + - mobilitydb + - meos + - rest-api + +license: PostgreSQL + +references: + - type: software + title: pg_mfserv + abstract: >- + Founding OGC API – Moving Features Python server for + MobilityDB. The initial implementation that MobilityAPI + extends. + authors: + - family-names: Schoemans + given-names: Maxime + affiliation: Université libre de Bruxelles (ULB) + - family-names: Morabito + given-names: Victor + affiliation: Université libre de Bruxelles (ULB) + repository-code: "https://github.com/MobilityDB/pg_mfserv" + notes: >- + Predecessor implementation; archived at + MobilityDB/pg_mfserv. MobilityAPI builds on its OGC endpoint + design and PyMEOS integration pattern. diff --git a/README.md b/README.md index a689348..8f8dafa 100644 --- a/README.md +++ b/README.md @@ -39,6 +39,21 @@ To do that you will have to change the path in the script to the path of your .c Here is a link to download ships datasets: [Denmark Ships DataSets](http://aisdata.ais.dk/?prefix=2024/) ## Developement This project is in progress. + +## History and Acknowledgements + +MobilityAPI builds on the foundation laid by **[pg_mfserv](https://github.com/MobilityDB/pg_mfserv)**, an OGC API – Moving Features prototype authored at ULB in early 2024. The pg_mfserv initial implementation provided the Python-server skeleton, the OGC endpoint shape, and the PyMEOS-based MobilityDB integration pattern that MobilityAPI extends with a structured resource layout, comprehensive test coverage, and OGC-conformant request/response handling. + +**pg_mfserv** is preserved in archived form at [`MobilityDB/pg_mfserv`](https://github.com/MobilityDB/pg_mfserv) for historical reference and scholarly attribution; active development continues in this repository. + +Contributors to the lineage, in chronological order: + +- **Maxime Schoemans** ([@mschoema](https://github.com/mschoema)) — pg_mfserv founding author (initial commit, OGC-API endpoint design). +- **Victor Morabito** ([@MrMaxime1er](https://github.com/MrMaxime1er)) — pg_mfserv main developer (column-discovery, request handling, exception handling, route refactors — March 2024). +- **Sirine Meraoui** ([@sirimeraoui](https://github.com/sirimeraoui)) — current MobilityAPI maintainer (structured resource layout, test infrastructure, OGC conformance, documentation). + +See [`AUTHORS.md`](AUTHORS.md) for the complete contributor list. + ## License ##Poetry poetry install