I always use the example of E2SMs that only contain XML-encoded payload, but work on top of E2AP. It should be possible to implement xApps consuming such E2SMs without ever having to touch an ASN.1 compiler. For this we need to work on the subscription management interface RIC-80, but also have an interface that extract all E2AP-defined fields from a message received from E2T. There are two places where this translation could be done. (1) in E2T looking at the E2AP message type and extracting the respective E2AP-defined headers, translating them into some other format (protobuf) and sending them on. Or alternatively (2) have an entity on xApp side do this. (2) could e.g. be done by an API defines in xAppFrame that can be used to pick the correct fields from the E2AP-defined part of the messages received (the "API" could also be a protobuf definition). (1) doesn't sound like a low-latency operation. So we should go for (2). (2) should be implemented that given a message in a message buffer  it provides access to the E2AP-defined fields (i.e. the library in (2) requires an ASN.1 compiler).

Another aspect are E2AP messages sent from xApps to E2 nodes (like E2AP Control messages). There we'd need an encoder library that given all header fields and E2SM "octet strings" constructs a valid E2AP message. This might get quite complex.

Even if we have such a library it might be that some xApp developers prefer using a different ASN.1 parser and would still want direct access to the full messages.

That being said, this item should be mapped to xAppframe. I also don't see this as Bronze candidate anymore as more discussion is needed. So I also mark this as future (post_bronze work).