- I'm not sure that glossary entries are a good use of the template mechanism. Because Agent is defined here, now we can't reformat the glossary entry for Agent because the formatting is defined in the description in this template. And if anyone were to fix it here it would mess up other uses elsewhere. There probably isn't a solution to this, short of modifying MediaWiki code, so I guess I'll just copy your Description section out. Please revert if you find a better solution. --Morgaine Dinova 10:37, 20 October 2007 (PDT)
- I reverted my glossary edit and changed the template formatting instead. It's not ideal, but at least it avoids duplication. --Morgaine Dinova 10:47, 20 October 2007 (PDT)
An Agent is a software resource which represents some portion of a user in the virtual world. Agents are hosted in agent servers. An agent may cause an avatar to be instantiated on behalf of a user. -Zha
- Both prims and avatars use agents, and an agent may not be associated to a user. I'm confused with what you mean between "agent servers" and Agent Services. How does an agent cause an avatar to be instantiated? Dzonatas Sol 09:56, 22 October 2007 (PDT)
* Mediate the user's message traffic * Mediate the user's asset inventory * Act as a focal point for the user's access to services in other domains * Act as a focal point for the user's access to utilties * Act to report the user's avatar's location in the Virtual World to other parts of the system - Zha
- How does the agent mediate? Can you define the RESTful interface for it? Is there a design document for the actual message?
- Is there a design document for the a user's asset inventory?
- Can you be more specific on "services in other domains." It it not clear enough to understand potential implementation or what services it would not affect.
- Where are the "utilties?" Are there any design documents to describe what they are, where they are, or how they interact with other aspects of the model?
- What "part of the system" are being reported. I wouldn't know how to implement that without more exact description. Can we create more design documents to link to in order to describe them in more detail? Dzonatas Sol 09:56, 22 October 2007 (PDT)
Agents do not:
* Store persistent assets (They are stored in asset servers)
Agents are not:
* The software resource which represents a user's avatar inside a region simulator. (Tho we need a name for that.) -Zha
- Do agents hold any kind of asset information? How are assets and agents tied together? Assets are stored in Agent Stores and Region Stores and that is still confused with "asset servers" and Agent Services and Region Services. Dzonatas Sol 09:56, 22 October 2007 (PDT)
This definition is different from the current (pre agent/region domain split) use of the term agent Second Life. Currently agents are hosted on the simulator where the user's avatar resides, and handle these tasks as well as mediating the avatar's connection to the client. The term agent, in general is overloaded, and is it possible that another, more specific term would be appropriate here.
- This statement definitely belongs in another sections besides the "navigational" description. I doubt it fits in "Specifications," also. Maybe a section for "Proposed Changes" or "Proposed Formal Name"? Dzonatas Sol 09:56, 22 October 2007 (PDT)