[ARC-80] Querying blockchain information using a URI format

[SudoWeezy]

URI Scheme for Blockchain Information Querying (ARC-80)

This ARC proposes a standardized URI scheme for querying blockchain information.

It introduces new URI formats for retrieving data on application states and asset fields directly, supporting read-only queries.
Inspired by ARC-26, it provides a consistent method for accessing blockchain data without using an SDK.

[emg110]

Hello @SudoWeezy, great and much-needed ARC.

Just a humble suggestion given the fact that proposed URI format (e.g. algorand:app:// or algorand:asset://) is not completely compliant to RFC 3986.

I suggest making this small change and move App and Asset to URI authority in URI scheme, like:

algorand://app/12345?global=Z2xvYmFsX2tleQ==

• Scheme: algorand.
• Authority: app or asset.
• Path: /12345 — A hierarchical path.
• Query: global=Z2xvYmFsX2tleQ== — A properly formatted query.

Rational:

• RFC 3986 full compliance (scheme:[//authority]path[?query][#fragment])
• ARC 26 compliance and no breaking changes in Algorand scheme
• Scheme is ususally the ontology root of the system (Algorand in this case) and does not accept fragmentation.
• app or asset are best considered different ontology authorities (subjective system territories) as Account (EOA), ASC and ASA are to Algorand. As ARC-26 already covers Account Authority, by proposing App and Asset Authorities ARC80 extends ARC26 in most effective and RFC compliant way.

I humbly believe that this way we will have ARC80:

• 100% compliant with RFC 3986
• Extending and 100% inheriting from and compliant to ARC26

[SudoWeezy]

Hello @SudoWeezy, great and much-needed ARC.

Just a humble suggestion given the fact that proposed URI format (e.g. algorand:app:// or algorand:asset://) is not completely compliant to RFC 3986.

I suggest making this small change and move App and Asset to URI authority in URI scheme, like:

algorand://app/12345?global=Z2xvYmFsX2tleQ==

• Scheme: algorand.
• Authority: app or asset.
• Path: /12345 — A hierarchical path.
• Query: global=Z2xvYmFsX2tleQ== — A properly formatted query.

Rational:

• RFC 3986 full compliance (scheme:[//authority]path[?query][#fragment])
• ARC 26 compliance and no breaking changes in Algorand scheme
• Scheme is ususally the ontology root of the system (Algorand in this case) and does not accept fragmentation.
• app or asset are best considered different ontology authorities (subjective system territories) as Account (EOA), ASC and ASA are to Algorand. As ARC-26 already covers Account Authority, by proposing App and Asset Authorities ARC80 extends ARC26 in most effective and RFC compliant way.

I humbly believe that this way we will have ARC80:

• 100% compliant with RFC 3986
• Extending and 100% inheriting from and compliant to ARC26

Thanks, I made the update based on your wise comment!