[sldev] [META][AWG]log chat of AWG meeting Friday, Oct 5, 2007
Argent Stonecutter
secret.argent at gmail.com
Sat Oct 6 21:37:32 PDT 2007
On 06-Oct-2007, at 18:34, Callum Lerwick wrote:
> I thought we were agreeing that permissions are part of an asset
> instance. :)
OK.
> Description is a bit less clear cut. An asset creator would
> probably want to be able to set a name and a description that is
> part of
> the asset, thus part of its identity. You would then be unable to edit
> that description without ending up with a new asset.
In SL the description and name can be changed if the asset is not
read-only.
Permissions are informational only. In this case they mean "if you
change this, it will get reset if you return this asset to this domain".
> Well, we would have compound assets. An SL object would be a list of
> prims, with references to textures, scripts and whatnot that are
> stored
> as separate assets.
Yah, I mean we don't need to make ALL assets compound assets.
And prims are kind of a special case. A prim is a container, a
linkset a two-level tree. The prim itself is a compoint asset in that
it has references to textures (at least) as properties of the prim
itself, the assets inside it are references in the local domain, but
probably need to be fetched recursively or even completely serialized
for transfers.
>> I think the "instance" needs to be a long term object, as well. If
>> you edit a texture in your inventory, change its properties, its
>> identifier shouldn't change.
> Which properties? Either you're creating a new global asset, or you're
> editing instance properties. You'll have to be more specific.
If you edit instance properties of the asset inside your inventory,
the id you get when you ask for its UUID should not change, and that
instance should still be what you get when you ask for that asset
within the domain (say, rendering a prim you textured through that
instance of that asset). So within your local domain (say, within
second life... it's a domain in this context) the "instance" in your
inventory is stored in an asset server (it may be called an agent
server or an inventory server, but it answers asset server queries).
Damn, I can't see how to make that clearer. Am I making sense?
More information about the SLDev
mailing list