Asset based XDMs are too content management centric.

## What are the schemas that are affected by the issue
https://github.com/adobe/xdm/blob/master/schemas/assets/asset.schema.json
https://github.com/adobe/xdm/blob/master/schemas/assets/video.schema.json
https://github.com/adobe/xdm/blob/master/schemas/assets/image.schema.json

## What are examples of products that are impacted by the issue:
AdCloud, Video Analytics

Video
Image
These all have inherited Asset required fields which do not easily translate to how AdCloud categorizes videos:
AssetID – this has a very specific format requirement not currently implemented in AdCloud or the ad industry. Can we be more flexible on this field?
eTag – information not currently available at event stream capture time
format, lastModifiedDate, name, path, size, version – these are currently stored in our facts tables and not relevant at event processing time.

For consumption based processes the required fields are not as relevant and the information is not available in many cases.

We need to review if it makes sense for some of these required and strongly structured fields, or if we should use a different schema doe the consumption aspects of assets.