Difference between revisions of "Map API VAG"
Jump to navigation
Jump to search
(wiki-fu) |
|||
| Line 1: | Line 1: | ||
: | :this is an initial draft so scope and focus are still fairly open. Please add comments to the [[{{TALKPAGENAME}}]] if you have slightly different viewpoints so we can try to converge on a common view. This discussion could also expose other similar VAG that are needed in this area | ||
The Map API Viewpoint Advocacy Group exists to ... | The Map API Viewpoint Advocacy Group exists to ... | ||
| Line 7: | Line 5: | ||
See the [[Architecture Working Group]] and the [[Viewpoint Advocacy Groups]] for more information. | See the [[Architecture Working Group]] and the [[Viewpoint Advocacy Groups]] for more information. | ||
= | == Areas of concern addressed by the viewpoint == | ||
* Improving the usefulness of the Webmap API to both client, server and SL Viewer applications | |||
Areas of concern addressed by the viewpoint | * Permitting third-party developers to develop their own APIs by providing them with a data source suitable for updating their database | ||
* | ** Analysing use cases where the first party API is insufficient in order to improve the first party API | ||
* | |||
* | |||
* | |||
=Source of Viewpoint= | == Source of Viewpoint == | ||
=Use Cases= | == Use Cases == | ||
See the [[Architecture Working Group Glossary]] and [[usecase templates]] for more information on creating usecases. One liners are fine (and better than nothing) but more detail will result in a better understanding and a better architecture. | See the [[Architecture Working Group Glossary]] and [[usecase templates]] for more information on creating usecases. One liners are fine (and better than nothing) but more detail will result in a better understanding and a better architecture. | ||
== Related JIRA Issues == | |||
The following JIRA issues are known problems that this VAG would like to see resolved in any future architecture. The purpose of this list it to avoid problems that exist in the curent architecture. The more typical JIRAs that are more short term in nature or can be resolved by simple code or design change should not be listed here. | The following JIRA issues are known problems that this VAG would like to see resolved in any future architecture. The purpose of this list it to avoid problems that exist in the curent architecture. The more typical JIRAs that are more short term in nature or can be resolved by simple code or design change should not be listed here. | ||
== Organization == | |||
Anyone with an interest in this Viewpoint is welcome to join. You should join the [[AW Groupies]] group in Second Life. | |||
=== In world meetings === | |||
# [[/2008-01-22| Tuesday 22nd January, 9:30am]] [http://slurl.com/secondlife/Beaumont/42/218/35 Meta Linden's Office] | |||
: | === Members (Stakeholders) === | ||
* [[User:SignpostMarv Martin|SignpostMarv Martin]] | |||
[[Category: AW Groupies]] | [[Category: AW Groupies]] | ||
[[Category:Map API VAG]] | |||
Revision as of 16:59, 19 January 2008
- this is an initial draft so scope and focus are still fairly open. Please add comments to the Talk:Map API VAG if you have slightly different viewpoints so we can try to converge on a common view. This discussion could also expose other similar VAG that are needed in this area
The Map API Viewpoint Advocacy Group exists to ...
See the Architecture Working Group and the Viewpoint Advocacy Groups for more information.
Areas of concern addressed by the viewpoint
- Improving the usefulness of the Webmap API to both client, server and SL Viewer applications
- Permitting third-party developers to develop their own APIs by providing them with a data source suitable for updating their database
- Analysing use cases where the first party API is insufficient in order to improve the first party API
Source of Viewpoint
Use Cases
See the Architecture Working Group Glossary and usecase templates for more information on creating usecases. One liners are fine (and better than nothing) but more detail will result in a better understanding and a better architecture.
Related JIRA Issues
The following JIRA issues are known problems that this VAG would like to see resolved in any future architecture. The purpose of this list it to avoid problems that exist in the curent architecture. The more typical JIRAs that are more short term in nature or can be resolved by simple code or design change should not be listed here.
Organization
Anyone with an interest in this Viewpoint is welcome to join. You should join the AW Groupies group in Second Life.