This repository has been archived by the owner on Jun 22, 2023. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 73
Redesign: 1. Interested Parties
Joe Amenta edited this page Feb 14, 2019
·
1 revision
Represented by:
Interests:
- Standards conformance
- Consistency across platforms
Represented by:
- @bricelam
- others from the outreach e-mail thread whose names / e-mails I'm not comfortable writing down in this public space
Interests:
- Straightforward API usage patterns that can be easily recognized
- APIs that correspond to commonly used spatial queries and aggregates available in RDBMS solutions, especially Microsoft SQL Server
Represented by:
Interests:
- Clean API
- Low cost to maintain
Represented by:
- @FObermaier (NetTopologySuite)
Interests:
- Stable API
- Semantic versioning
- Straightforward to implement (not necessarily "easy")
- (NetTopologySuite specific) Nothing that requires breaking things in NTS that work in JTS
Represented by:
- @xivk (OsmSharp + Itinero)
Interests:
- Stable API
- Semantic versioning
- Large catalog of APIs "in-the-box" (i.e., few reasons to force a dependency on a particular implementation)
Represented by:
- @roji (npgsql)
- @airbreather (some proprietary software whose name I haven't disclosed yet)
Interests:
- Stable API
- Large catalog of APIs
- Performance (CPU, memory, and I/O)
- Discoverable via IntelliSense
- Well-documented