Talk:Second Life Grid Glossary - Revision history

Wolt Amat: Minor spelling correction.

2008-06-09T02:09:18Z

Minor spelling correction.

← Older revision		Revision as of 19:09, 8 June 2008
Line 5:		Line 5:

	==== Agent ====		==== Agent ====
	'''content merged from ~~seperate~~ page to avoid wiki sprawl'''		'''content merged from separate page to avoid wiki sprawl'''

			This is [[User:Dzonatsas Sol]]'s material

	~~This is [[User:Dzonatsas Sol]]'s material~~
	= Specifications =		= Specifications =

Zero Linden: Talk:Architecture Working Group Glossary moved to Talk:Second Life Grid Glossary: document reorganization and clearer naming scheme

2007-11-02T23:30:23Z

Talk:Architecture Working Group Glossary moved to Talk:Second Life Grid Glossary: document reorganization and clearer naming scheme

← Older revision	Revision as of 16:30, 2 November 2007
(No difference)

Wolt Amat: /* User */

2007-11-02T05:28:52Z

User

← Older revision		Revision as of 22:28, 1 November 2007
Line 243:		Line 243:

	==== User ====		==== User ====
			'''Bold text'''Some raw materials for "User" definition from existing standards, each of which makes a valid point. This is only a short list, I found over 131 valid definitions. The key points seem to be that the user is the entity using the service, that the user has been authorized by the subscriber and is permitted acess, that the user could be human, organization or machine, and that the user is identifiable.
			- A human communicating entity, ETS 300 498-1 ed.1
			- A person delegated by the subscriber to use the CTM service, ES 201 095 V1.1.1
			- A person or machine delegated by a service subscriber to use the services and/or facilities of a telecommunication network, EN 301 175 V1.1.1
			- A 'user' is a person or other entity authorized by a subscriber to use some or all of the services subscribed to by that subscriber, ETR 309 ed.1
			- An identifiable entity whose use of resources shall be accounted, ETS 300 819 ed.1
			- entity that uses the network services requested by the subscriber, TS 102 463 V1.1.1
			- Generic term used to refer to people or organizations who use telecommunication services. ETR 301 ed.1
			- human being or an item of equipment to which a service is provided, EG 201 872 V1.2.1
			- individuals, including consumers, or organizations using or requesting publicly available services. (Copied from Directive 98/10/EC) TR 102 308 V1.1.1
			- person or process using the system in order to gain access to some system resident or system accessible service TISPAN TS 102 165-1 V4.2.1

	==== Utility ====		==== Utility ====

Wolt Amat: /* Pre 10-19-2007 content */

2007-11-02T05:14:14Z

Pre 10-19-2007 content

← Older revision		Revision as of 22:14, 1 November 2007
Line 254:		Line 254:



			Post 10-19-2007 Content
			* One good source of raw materials for terms definition is the Terms Database at ETSI - http://webapp.etsi.org/TEDDI. A lot of the issues we will face have been faced by the telecoms industry, as far as users versus agents versus customers, and having multiple commercial, national, regional, and user domains interacting.

	==== Pre 10-19-2007 content ====		==== Pre 10-19-2007 content ====

Zha Ewry: /* Avatar */ (Add discussion sections for Avatar Delegate and Avatar Delegate Child)

2007-10-26T20:53:05Z

Avatar: (Add discussion sections for Avatar Delegate and Avatar Delegate Child)

← Older revision		Revision as of 13:53, 26 October 2007
Line 210:		Line 210:
	==== Avatar ====		==== Avatar ====
	Does the Avatar represent and agent, or a user? I think a user. The agent is a software construct which permits the user to interact with other portions of the system.		Does the Avatar represent and agent, or a user? I think a user. The agent is a software construct which permits the user to interact with other portions of the system.

			==== Avatar Delegate ====

			==== Avatar Delegate Child ====

	==== Component ====		==== Component ====

Zha Ewry: /* Asset */ (avoid nested page header)

2007-10-24T15:21:31Z

Asset: (avoid nested page header)

← Older revision		Revision as of 08:21, 24 October 2007
Line 74:		Line 74:

	'''Transfered from another page, to ensure we are all on the same page'''		'''Transfered from another page, to ensure we are all on the same page'''
	~~{{:AWG/PageHeader}}~~



	= Abstract Data Structure =		= Abstract Data Structure =

Zha Ewry: /* Agent */

2007-10-24T15:18:49Z

Agent

← Older revision		Revision as of 08:18, 24 October 2007
Line 5:		Line 5:

	==== Agent ====		==== Agent ====
			'''content merged from seperate page to avoid wiki sprawl'''

			This is [[User:Dzonatsas Sol]]'s material
			= Specifications =

			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.

			Agents:

			* 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


			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.)

			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.


			= Brainstorming =

			* The envisaged [[Project_Motivation\|massive scaling]] requires new forms of item organization, search, and access to cope with vast expansion. The current inventory mechanism is already stretched right now, so this issue needs early design attention.
			* it should be possible to manage inventories of all your agents under one identity. The idea is to e.g. being able to move items from one inventory to another
			* some organisation providing agents should be able to define on which regions an agent is allowed to connect, what he/she can do with object in their inventory
			* an agent domain should be able to have certain inventory pools which might be shared among agents (like the library in SL today)
			* it should be possible to import and export friends lists or groups of friends
			* it should be possible to maintain a friends list among various agent domains (related to import/export maybe but as protocol function)
			* it should be possible to copy inventory from one agent domain from another if the object structure is compatible.
			* an agent needs to provide various methods of verification
			* an agent domain needs to define presence information among an agent's friends list. This should even be possible among various agent domains.
			* Each agent needs to be able to define certain permissions on what other agents or groups of agents are allowed to see about him (online status, identity information, etc.)

			==== possible restrictions between regions and agents ====

			* An agent domain should be able to define on which regions an agent is allowed to connect
			* An agent domain should be able to define which objects are allowed to be rezzed on which region (e.g. company objects only on company regions etc. This might be related to object pools as described above).
			* A region might allow only certain agent domains to connect
			* A region might allow anybody to connect but the rights of that agent might be limited depending from where it comes and e.g. which verification mechanism the agent provides.
			* Standard specification of rights/permissions in a serialisable form that can be edited by the viewer and uploaded to an authorative per-domain server?

	==== Architecture ====		==== Architecture ====

Zha Ewry: /* Asset */ (Captured Thoughs from personal perspective page to share page for consensus building)

2007-10-24T15:05:27Z

Asset: (Captured Thoughs from personal perspective page to share page for consensus building)

Show changes

Dr Scofield: ~ moved discussion items from main glossary page to talk page, fixed zha's URL typo,

2007-10-23T10:18:16Z

~ moved discussion items from main glossary page to talk page, fixed zha's URL typo,

← Older revision		Revision as of 03:18, 23 October 2007
Line 11:		Line 11:

	==== Asset ====		==== Asset ====

			* (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 October 18 [[User:Zero Linden/Office Hours/2007 Oct 18\|transcript]] -- [[User:Zha Ewry\|Zha]] October 18, 2007, 5:42 PDT

			* you meant Oct 18, i think. corrected to that effect [[User:Dr Scofield\|Dr Scofield]] 03:18, 23 October 2007 (PDT)

			* updated the asset entry. question: how does an asset reference come into existence? we need to get the flow for that. [[User:Dr Scofield\|Dr Scofield]] 03:18, 23 October 2007 (PDT)

			* ''asset is currently under discussion on sldev'' -- [[User:Dr Scofield\|Dr Scofield]] 00:19, 18 October 2007 (PDT)

	==== Avatar ====		==== Avatar ====

Morgaine Dinova: /* Domain */

2007-10-20T17:11:00Z

Domain

← Older revision		Revision as of 10:11, 20 October 2007
Line 19:		Line 19:
	==== Domain ====		==== Domain ====
	* I replaced the label of the link to "AWG Domain rationale discussion" by "Domain rationale discussion". The use of "AWG Domain" creates terrible confusion and also conflicts with LL's use of the term. The page itself should be renamed too, but that's better done by its creator. --[[User:Morgaine Dinova\|Morgaine Dinova]] 09:49, 20 October 2007 (PDT)		* I replaced the label of the link to "AWG Domain rationale discussion" by "Domain rationale discussion". The use of "AWG Domain" creates terrible confusion and also conflicts with LL's use of the term. The page itself should be renamed too, but that's better done by its creator. --[[User:Morgaine Dinova\|Morgaine Dinova]] 09:49, 20 October 2007 (PDT)

			* The architecture proposed by LL also created a point of confusion in its use of "Organization Domains" ... there's some sort of dimensional incompatibility there with the use of "Domain" in "Agent Domain" and "Region Domain". [[Talk:Multiple_Domains\|I wrote a little about this topic]] back in September when I looked at the diagrams from the first meeting. Organization is better thought of as an attribute within this architecture, because it is so orthogonal to the other domains. What's more, it's a composite attribute with many aspects: for example, a server could belong to company A, provide resources for the group B, and be located in colo C. Which is the Organization domain? There is no single answer. "Organization Domain" isn't a very cohesive concept. --[[User:Morgaine Dinova\|Morgaine Dinova]] 10:11, 20 October 2007 (PDT)

	==== Meta Data ====		==== Meta Data ====