Difference between revisions of "User:Dzonatas Sol/AWG Asset/Description"
Jump to navigation
Jump to search
Dzonatas Sol (talk | contribs) m (Project:AWG/Asset/Description moved to AWG Asset/Description: moved from "Project:AWG/" to "AWG " per guideline and in the likeness of LSL pages) |
|||
| Line 3: | Line 3: | ||
::* (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.'' -- [[User:Zha Ewry|Zha]] | ::* (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.'' -- [[User:Zha Ewry|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 | ::* 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 [[User:Zero Linden/Office Hours/2007 Oct 16|transcript]] -- [[User:Zha Ewry|Zha]] October 18, 2007, 5:42 PDT | ||
October 18 [[User:Zero Linden/Office Hours/2007 Oct 16|transcript]] | |||
-- [[User:Zha Ewry|Zha]] October 18, 2007, 5:42 PDT | |||
::* ''asset is currently under discussion on sldev'' -- [[User:Dr Scofield|Dr Scofield]] 00:19, 18 October 2007 (PDT) | ::* ''asset is currently under discussion on sldev'' -- [[User:Dr Scofield|Dr Scofield]] 00:19, 18 October 2007 (PDT) | ||
* Assets exist in the {{AWG|Agent Stores}} of the {{AWG|Agent Domain}} or in the {{AWG|Region Stores}} of the {{AWG|Region Domain}}. | * Assets exist in the {{AWG|Agent Stores}} of the {{AWG|Agent Domain}} or in the {{AWG|Region Stores}} of the {{AWG|Region Domain}}. | ||
Revision as of 10:48, 20 October 2007
- 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)
- Assets exist in the Agent Stores of the Agent Domain or in the Region Stores of the Region Domain.