Hi all,
I’m a Technical Program Manager for the Partner Engineering (formerly Integrations) team at SDF, and for the past few months I’ve been leading an internal review of some of our protocol titles. This effort was spurred by watching teammates and partners onboard and realizing that we were defaulting to the SEP namespace, which has no meaning unto itself and can be confusing for newcomers, instead of plain language names.
We’d like to propose names that we feel are more usable and clear. As an added bonus, the work of defining each protocol in plain language also led us to consider other ways we can improve them (e.g. parity across the depth of documentation for servers and clients, SEP versioning, and SEP process documentation), so look for those updates in the next few months as well.
Here are the PRs for the new names; each has a context section and then a section where I explain why the name was chosen and what alternatives were considered. We’d love to get feedback from the Stellar community on these proposed titles, so please review and comment on the PRs and/or feel free to discuss here.
SEP-1
Current: stellar.toml
Proposed: Stellar Info File
https://github.com/stellar/stellar-protocol/pull/919SEP-6
Current: Anchor/Client interoperability
Proposed: Deposit and Withdrawal API
https://github.com/stellar/stellar-protocol/pull/920SEP-9
Current: Standard KYC / AML fields
Proposed: Standard KYC Fields
https://github.com/stellar/stellar-protocol/pull/921SEP-10
Current: Stellar Web Authentication
Proposed: Stellar Authentication
https://github.com/stellar/stellar-protocol/pull/922SEP-12
Current: Anchor/Client customer info transfer
Proposed: KYC API
https://github.com/stellar/stellar-protocol/pull/923SEP-24
Current: Interactive Anchor/Wallet Asset Transfer Server
Proposed: Hosted Deposit and Withdrawal
https://github.com/stellar/stellar-protocol/pull/924SEP-31
Current: Direct Payments
Proposed: Cross-border Payments API
https://github.com/stellar/stellar-protocol/pull/925Best, Lydia