The recent EU regulation on Markets in Crypto Assets Regulation (MiCA) represents significant progress in establishing a multi-jurisdiction framework for crypto-assets that will enable the greater participation of consumers in the digital assets industry. One type of token recognized by MiCA is the asset-referenced token, where the value-bearing physical asset being referenced by the token is external to the token. We discuss several design considerations for the on-chain and off- chain metadata for the asset-referenced token that represents physical real-world assets. The EU Data Spaces provides an interesting data management framework for the off-chain metadata underpinning the MiCA asset-referenced tokens, including asset definition schemas, asset profiles, digitized asset records, and tokenized asset records. The Web3 decentralized registries for assets-related metadata should be a promising application of the data spaces framework in the EU.

A software process model is a complex entity describing activities, products and quality aspects of the "real" software-production process. The ever-changing nature of the software process imposes a continuous control of its evolution; maintenance should adapt the process model to accurately reflect the state of the real process. Presently, process model maintainers have to make evolve these complex models under time pressure and with very little assistance. In this paper we present a preliminary approach for improving maintainability of Petri-net-based process models using the concept of view. A view can be seen as the sub-model capturing the perception a participant has about the process. We show how views can structure a model as a set of more abstract modules which are easy to make evolve. After evolution, views can be composed using a set of formally defined operators to obtain a new process model in an automatic way. Our study is applied to the Process Weaver modelling language. After a short presentation of the Process Weaver formalism, we illustrate view definition with an example of a review process model. View evolution and view composition are also introduced through a scenario of process model change based on the above example.