How does Asset relate to DataAddress?

[MoritzKeppler]

how does Asset relate to DataAddress?
see discussion started in #199
@ndr-brt @paullatzelsperger

_{Moritz Keppler moritz.keppler@daimler.com, Daimler TSS GmbH, legal info/Impressum}

[MoritzKeppler]

the discussion we had so far:

MoritzKeppler "why is DataAddress not just an attribute at Asset? From a DDD perspective: does a DataAddress has it's own identity? Don't think so - but maybe I'm wrong..."

ndr_brt "Actually looking from a DDD perspective the Asset is an entity, it has an identity, it has an history and, why not, their attributes could be modified without changing its identity.
Seems like DataAddress in this context is more of a value object, because it is just related to the Asset, and in fact it does not own an identity so I agree with your reasoning @MoritzKeppler .
Don't remember why we extracted DataAddress from Asset..."

PaulLatzelsperger "yes exactly. My intention was to mimic the behavior of a database where inserting values into two tables does not happen at the exact same time, but rather one-after-the-other. A transaction takes care of consistency.
I would not model the DataAddress as a property of the Asset, because the DataAddress will probably private information - we wouldn't want to expose where our data is stored. Thus, if the DataAddress is a property on the Asset, we would have to prevent exposing it during serialization, which I find dangerous."

MoritzKeppler "What we offer to outside is e.g. an IDS Resource or something similar. In my eyes it would be an antipattern to provide the internal model 1:1 to the world outside.
But a DataAdress can also be used in the information passed to others: it that case it would be the address under which the other participant can retrieve the data.
As soon as a consumer retrieved an asset it will be added to an internal catalog (as it now needs to be managed) and will get a DataAddress pointing to the local copy of the asset."

PaulLatzelsperger "

But a DataAdress can also be used in the information passed to others: it that case it would be the address under which the other participant can retrieve the data.

that would imply giving consumers direct access to, say, a database, right? Because I think the DataAddress would contain database name, etc...

As soon as a consumer retrieved an ...

sure, but then there will also be a different instance of the Asset within the consumer's realm, even if that may contain the same metadata."