User talk:Dzonatas Sol/AWG Asset/Description
Is this statement about assets true? It is almost certainly incomplete. Assets are stored in asset servers, and their persistent, authoritative state probably resides there. Further, this definition refers to two terms, neither of which has been introduced before. (Agent stores and region stores) If an asset exists in multiple places, which is definitive, and which is a copy? If this is an attempt to capture the fact that some portion of an asset is likely to be used within components in the agent and region domains, then, we need a use case which exposes a need for an addressable component of the architecture which lives in these domains ans stores architecturally addressable items. If, this represents suspicion that we will use such items inside of components in those domains, then it is probably out of scope for the architecture.
We need to pay close attention to the separation between artifacts which we need to expose as part of the architecture and artifacts which will naturally exit in components of the architecture. This isn't to dismiss the importance of those artifacts, but to highlight the need to be clear as to what is the basis for inter operation and the definition of components, and what is the business of components within that architecture. - Zha 16:47 PDT October 18, 2007
- I understand your concerns. I just wasn't that fast to map it all out in one day. Forgive me.
This page is for the open architecture while what is really true is en passe on the current implementation. Anotherwords, there will be less confusion to write in terms of the now; then for us to write in terms of the future and go back and spend painful time to rewrite in terms of what became true when implemented. A proof requires statements in terms of the now. I thought about a page earlier to describe such paradigm, but I thought it was more important to organize and wikify enough to create a useful map, and I didn't know what to call the page. =)
Nevertheless, Zero has already described the Stores: Region_Domain#Region_Stores. They are a decomposition from the previous Central Databases. For example, Agent Domain stores inventory assets, and Region Domain stores rezzed assets. Dzonatas Sol 19:22, 18 October 2007 (PDT)
previous talk found in description
- An entity which can be transferred from agent to agent or from agent to region or from region to agent. It can be something like an object, texture, sound, link, landmark, and so forth.
- Architecturally, an asset consists of asset properties and asset data (also called meta data).
- (temp note): We need some clarity here, and elsewhere in the glossary between a Web Services description of resources such as an asset, and an in use description. If we view all assets as having URLs and a singular place in an asset server where the definitive copy of the asset exists, then we need to separate that from the potentially many places where copies of that set of information may be cached and used. -- Zha
- Ah.. Actually, if we wish to make a distinction between the asset's data, and its meta-data, then, we have the asset, which would be what we "get" from the URL, and the meta-data, which we seperate from the core item, in one of several ways. There was a nice bit of discussion of this in Zeros office hours on October 18 transcript -- Zha October 18, 2007, 5:42 PDT
- asset is currently under discussion on sldev -- Dr Scofield 00:19, 18 October 2007 (PDT)