PSP categorization schema

[bernardoaraujor]

I've been studying the Core EIPs and got curious:

Is there any schema classifying PSPs in terms of:

• Runtime Standards: runtime logic composed by multiple pallets
• Smart Contract Standards: ABI level standards tailored for pallet-contracts or pallet-evm (which could also be another form of subcategorization)

in case there isn't, wouldn't it make sense for us to introduce some?

The rationale would be the argument that Smart Contract and Runtime are fundamentally different layers of execution under the Polkadot protocol, so it would make sense to have the PSP structure reflect that in some way or another. That would also help the audience assimilate those fundamental differences from the PSP structure itself.

The way they are structured now, the PSPs give some descriptive context, frequently on the Motivation section.
But it would be useful to help the reader assimilate inherently foundational concepts about the PSP even before they start reading it, because they already know the PSP belongs to a certain category.

[bernardoaraujor]

One suggestion of a subcategorisation schema could be to slighlty modify the current numbering system.

Appending a letter to the right side could be used to indicate the context which the PSP is operating upon.

Something like:

• PSP-S-*: Substrate Standards. E.g.: PSP-S-20 (Substrate Uniform Resource Identifier), PSP-S- (Fungible Asset Wallet Metadata)
• PSP-R-*: Runtime Standards. E.g.: PSP-R-32 (Paratoken Standard)
• PSP-C-*: Smart Contract Standards. E.g.: PSP-C-22 (Fungible Token Standard for Substrate's contracts pallet), PSP-C-35 (Multi Token Standard for Substrate's contracts pallet)
• PSP-X-*: Cross-Consensus Standards
• PSP-G-*: Governance Standards
• Other subcategories?

[bernardoaraujor]

@xgreenx also suggested on our AmsterDOT discussion:

• having separate repositories for different categories, which could potentially improve and accelerate the reviewing processes, since engineers with different skillsets would focus their attention on specialized contexts. Ultimately, the each PSP subcategory repo is free from the noise generated in the other subcategories.
• different PSP schemas for each category, so that meaningful information can be properly contextualized