Merge pull request #1 from MobilityDB/add-lineage-credits

Add lineage credits: pg_mfserv predecessor, AUTHORS, CITATION

Author: estebanzimanyi

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.

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.

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