User:Zha Ewry/Scoping - Revision history

Saijanai Kuhn: /* Out of scope things */

2008-10-01T15:47:20Z

Out of scope things

← Older revision		Revision as of 08:47, 1 October 2008
Line 57:		Line 57:
	[[User:Zha Ewry\| Zha Ewry]] Added Profiles, and Reference Implementations, October 10, 2007, 8:36 AM PDT		[[User:Zha Ewry\| Zha Ewry]] Added Profiles, and Reference Implementations, October 10, 2007, 8:36 AM PDT

	[[Category: AW Groupies]]		[[Category:AW Groupies]]
			[[Category:AW Groupies User Pages]]

Liana Linden at 21:41, 7 November 2007

2007-11-07T21:41:53Z

← Older revision		Revision as of 14:41, 7 November 2007
Line 57:		Line 57:
	[[User:Zha Ewry\| Zha Ewry]] Added Profiles, and Reference Implementations, October 10, 2007, 8:36 AM PDT		[[User:Zha Ewry\| Zha Ewry]] Added Profiles, and Reference Implementations, October 10, 2007, 8:36 AM PDT

	~~[[Category:Architecture Working Group]]~~
	[[Category: AW Groupies]]		[[Category: AW Groupies]]

Liana Linden: Scoping moved to User:Zha Ewry/Scoping: AWG wiki restructuring edit

2007-11-07T21:41:00Z

Scoping moved to User:Zha Ewry/Scoping: AWG wiki restructuring edit

← Older revision	Revision as of 14:41, 7 November 2007
(No difference)

Saijanai Kuhn: added gropuies tag

2007-10-23T23:30:39Z

added gropuies tag

← Older revision		Revision as of 16:30, 23 October 2007
Line 58:		Line 58:

	[[Category:Architecture Working Group]]		[[Category:Architecture Working Group]]
			[[Category: AW Groupies]]

Morgaine Dinova: /* Normative work products */

2007-10-14T08:54:19Z

Normative work products

← Older revision		Revision as of 01:54, 14 October 2007
Line 13:		Line 13:
	## it is prescriptive on the highly central goal of "Making the grid a scalable place"		## it is prescriptive on the highly central goal of "Making the grid a scalable place"
	## it is prescriptive on addressing the motivators expressed in Project Motivation		## it is prescriptive on addressing the motivators expressed in Project Motivation
			## it provides the single most important constraint for all other normative work products
	# The core REST web services plumbing, including c-http, the escrow pattern, and a publish/subscribe pattern for continuing messages		# The core REST web services plumbing, including c-http, the escrow pattern, and a publish/subscribe pattern for continuing messages
	## prescriptive by ''fiat'': worldwide use shows this approach has numerous benefits, ride on the shoulders of giants		## prescriptive by ''fiat'': worldwide use shows this approach has numerous benefits, ride on the shoulders of giants

Morgaine Dinova: /* Normative work products */

2007-10-14T08:52:51Z

Normative work products

← Older revision		Revision as of 01:52, 14 October 2007
Line 10:		Line 10:
	Here is a tentative list of the definitional, normative work products		Here is a tentative list of the definitional, normative work products

	# A core model with highly scalable resources and mechanisms. This model is core and ~~normative~~ because:		# A core model with highly scalable resources and mechanisms. This model is core, normative and primary because:
	::* it is prescriptive on the highly central goal of "Making the grid a scalable place"		## it is prescriptive on the highly central goal of "Making the grid a scalable place"
	::* it is prescriptive on addressing the motivators expressed in Project Motivation		## it is prescriptive on addressing the motivators expressed in Project Motivation
	# The core REST web services plumbing, including c-http, the escrow pattern, and a publish/subscribe pattern for continuing messages		# The core REST web services plumbing, including c-http, the escrow pattern, and a publish/subscribe pattern for continuing messages
	~~::* normative~~ by ''fiat'': worldwide ~~experience has demonstrated~~ this approach ~~to have~~ numerous benefits		## prescriptive by ''fiat'': worldwide use shows this approach has numerous benefits, ride on the shoulders of giants
	# A set of web services define in terms of 1		## prescriptive by internal experience of suitability for Second Life architecture, and consistent with need for evolution
	::* implied		# A set of web services define in terms of 2
	# A set of messages sent as a result of an invocation of one of the web services in 1 and 2		#:* implied
	::* implied		# A set of messages sent as a result of an invocation of one of the web services in 2 and 3
	# A set of interaction patterns using the services defined in 1, 2 and 3 to achieve specific effects		#:* implied
	::* implied, and the non-specific parts cannot be normative		# A set of interaction patterns using the services defined in 2, 3 and 4 to achieve specific effects
	# A set of things we find which exist which we cannot describe through items 1-4		#:* implied, and the non-specific parts cannot be normative
	::* How can you have an undefined normative work product????		# A set of things we find which exist which we cannot describe through items 2-5
			#:* How can you have an undefined normative work product????

	==== Informative work products ====		==== Informative work products ====

Morgaine Dinova: /* Normative work products */

2007-10-14T08:42:59Z

Normative work products

← Older revision		Revision as of 01:42, 14 October 2007
Line 10:		Line 10:
	Here is a tentative list of the definitional, normative work products		Here is a tentative list of the definitional, normative work products

	# The core REST web services plumbing, including c-http, the escrow pattern, and a publish/subscribe pattern for continuing messages		# A core model with highly scalable resources and mechanisms. This model is core and normative because:
			::* it is prescriptive on the highly central goal of "Making the grid a scalable place"
			::* it is prescriptive on addressing the motivators expressed in Project Motivation
			# The core REST web services plumbing, including c-http, the escrow pattern, and a publish/subscribe pattern for continuing messages
			::* normative by ''fiat'': worldwide experience has demonstrated this approach to have numerous benefits
	# A set of web services define in terms of 1		# A set of web services define in terms of 1
			::* implied
	# A set of messages sent as a result of an invocation of one of the web services in 1 and 2		# A set of messages sent as a result of an invocation of one of the web services in 1 and 2
			::* implied
	# A set of interaction patterns using the services defined in 1, 2 and 3 to achieve specific effects		# A set of interaction patterns using the services defined in 1, 2 and 3 to achieve specific effects
			::* implied, and the non-specific parts cannot be normative
	# A set of things we find which exist which we cannot describe through items 1-4		# A set of things we find which exist which we cannot describe through items 1-4
			::* How can you have an undefined normative work product????

	==== Informative work products ====		==== Informative work products ====

Strife Onizuka: /* Informative work products */ screwed up rendering in firefox

2007-10-10T16:33:41Z

Informative work products: screwed up rendering in firefox

← Older revision		Revision as of 09:33, 10 October 2007
Line 29:		Line 29:
	## Private asset stores (internal to clients, or co-located on client boxes)		## Private asset stores (internal to clients, or co-located on client boxes)
	## Private local sims (internal to clients, or co-located on client boxes, and not publically accessible)		## Private local sims (internal to clients, or co-located on client boxes, and not publically accessible)
	##
	# Profiles, describing useful, coherent subsets of the services and optional pluggable components		# Profiles, describing useful, coherent subsets of the services and optional pluggable components
	## This cluster of services defines a "Linden Style Agent Domain"		## This cluster of services defines a "Linden Style Agent Domain"

Zha Ewry: /* Informative work products */

2007-10-10T15:39:14Z

Informative work products

← Older revision		Revision as of 08:39, 10 October 2007
Line 21:		Line 21:
	# A set of detailed use cases describing the requirements of the architecture		# A set of detailed use cases describing the requirements of the architecture
	# A set of scalability and interoperability analysis, informing the normative documents		# A set of scalability and interoperability analysis, informing the normative documents

	# A set of pluggable components and plug points. (Note most of these happen inside components, but matter)		# A set of pluggable components and plug points. (Note most of these happen inside components, but matter)
	## Physics engines		## Physics engines
Line 38:		Line 37:
	## Reference implementation(s) of a specific service		## Reference implementation(s) of a specific service
	## Reference implementation(s) of a specific profile		## Reference implementation(s) of a specific profile

	# More?		# More?

Zha Ewry: /* Scope of the AWG's work */

2007-10-10T15:37:43Z

Scope of the AWG's work

← Older revision		Revision as of 08:37, 10 October 2007
Line 7:		Line 7:
	One way to define the scope of the project is by its work products. In particular, the normative, definitional work products which define conformance to the architecture, and the informative work products which inform the architecture, explain it, and often drive it, but are not part of its formal specification.		One way to define the scope of the project is by its work products. In particular, the normative, definitional work products which define conformance to the architecture, and the informative work products which inform the architecture, explain it, and often drive it, but are not part of its formal specification.

			==== Normative work products ====
	Here is a tentative list of the definitional, normative work products		Here is a tentative list of the definitional, normative work products

Line 15:		Line 16:
	# A set of things we find which exist which we cannot describe through items 1-4		# A set of things we find which exist which we cannot describe through items 1-4


			==== Informative work products ====
	Here is a tentative, less complete list of informative work products		Here is a tentative, less complete list of informative work products
	# A set of detailed use cases describing the requirements of the architecture		# A set of detailed use cases describing the requirements of the architecture
Line 37:		Line 40:

	# More?		# More?

			==== Out of scope things ====

	Here is a list of things which I think are not our business at all:		Here is a list of things which I think are not our business at all:
Line 43:		Line 48:

	[[User:Zha Ewry\|- Zha]] Tuesday, October 9, 2007, 10:28 PM PDT		[[User:Zha Ewry\|- Zha]] Tuesday, October 9, 2007, 10:28 PM PDT
	[[User:Zha Ewry] Zha Ewry]] Added Profiles, and Reference Implementations, October 10, 2007, 8:36 AM PDT
			[[User:Zha Ewry\| Zha Ewry]] Added Profiles, and Reference Implementations, October 10, 2007, 8:36 AM PDT

	[[Category:Architecture Working Group]]		[[Category:Architecture Working Group]]