Should ALDRs be provided for non-DASL CIDs, for blake3 CIDs, and/or for forcetyping non-string map keys?

[bumblefudge]

none of the three seem important to review by CBOR librarians and tool builders, but might be useful to add later if app-level folks are reading this

[vmx]

I don't know what ALDRs are and it's also not explained in the spec.

[bumblefudge]

It's a later CBOR WG template format for describing userland things (like the bignum workaround you're proposing DASL should write instead of using CBOR bignums 😉 ). The exact template seems to be iterating, so i'm never sure it's a good time to start, i'm eternally waiting for the next RFC from the WG 😅

[bumblefudge]

the newest draft of the BCP on determinism and profiling has an appendix describing (but not really specifying) the app-level profiling formerly known as ALDRs; we should figure out if this belongs in the internet-draft or in, e.g., ATP docs, DASL's website, etc. My intuition is that at least something (BIGNUM and datetime for example) should be here, actually, if the goal is to have DAG-CBOR supported as a profile/configurable setting in mainstream CBOR libraries...

NB @darobin