By data content, I meant information such as address, length/size, data, type, etc. Upon further review, your short list of the other signals actually can be captured in the transaction (e.g. ARQOS - I assume Quality of Service - would be a quantity that should be stored in the transaction). I’m not very familiar with AXI, but I was trying to make general points applicable to any bus protocol.
All signals should be included in the interface, along with specified parameters. Signals that represent quantities should be modeled in the transaction. Signals strictly for controlling the protocol and timing should be used by the driver/monitor, and do not need to be included in the transaction model.
Sorry for being unclear previously.