When implementing the read side, we don't need to touch anything in the domain model. We will concentrate our efforts on the application side. However, this doesn't mean that we need to forget about Ubiquitous Language. In the end, read models are part of the whole model anyway; we saw them during the EventStorming sessions as green sticky notes. Read models help people and other systems make decisions, based on the data they receive by executing our queries. Just as commands indicate the intent of external parties to run some operations on our domain, read models and queries express their intent to get something in return.
For example, for our Marketplace application, we would expect shoppers to browse through published ads. Ad owners need to see a list of their ads. Everyone needs to be able to open a single ad and see everything in it that is...