Map API VAG

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

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.

In world meetings

1. Tuesday 22nd January, 9:30am Meta Linden's Office

Members (Stakeholders)

• SignpostMarv Martin
• Hackshaven Harford
• Ice Brodie - Unable to make meeting on the 22nd