Second Life Wiki - User contributions [en]

LSL HTTP server

2009-11-15T23:27:46Z

Hugo Dalgleish:

{{LSL Header|ml=*}}
== Introduction ==
This is the counterpart to [[llHTTPRequest]]. While llHTTPRequest enables LSL scripts request data from HTTP-accessible sources, HTTP-in enables outside sources to request data from scripts in Second Life. The key difference is that llHTTPRequest exchanges data when the script in SL wants; HTTP-in allows outside sources to determine when they need to communicate with scripts in SL.

Prior to HTTP-in, similar functionality could be achieved by polling with [[llHTTPRequest]], [[llEmail]] and [[:Category:LSL_XML-RPC|XML-RPC]]. All three are cumbersome and the latter two have serious scalability bottlenecks.

It is important to note that LSL HTTP servers cannot use HTML. See [[#Other_Limitations|Other Limitations]] for details.

== Uses ==
* Easily get data from LSL scripts to outside viewers, scripts or servers.
** Web front end for a visitor counter or other statistics accumulator.
* Easily get data into LSL scripts from outside viewers, scripts or servers.
** A store with a web front end that communicates to an in-world object to exchange L$ and inventory items.
** Inworld game for which an external program handles the primary game logic that needs to manipulate inworld items.

Gory Technical Details follow. Or jump straight to the [[LSL_http_server/examples | Script Examples]].

== Script API ==
* '''[[LlRequestURL|key llRequestURL()]]'''
: Request a new LSL Server public URL.
: An http_request event will be triggered with success or failure and include the returned key
<lsl>request_id = llRequestURL();</lsl>
* '''[[LlRequestSecureURL|key llRequestSecureURL()]]'''
: Similar to ''llRequestURL'' except requests an HTTPS / SSL URL.
: An http_request event will be triggered with success or failure and include the returned key
<lsl>request_id = llRequestSecureURL();</lsl>
* '''[[LlReleaseURL|llReleaseURL(string url)]]'''
: Clear the specific URL, used for both secure and non-secure URLs.
<lsl>llReleaseURL("http://sim3015.aditi.lindenlab.com:12046/cap/3ff4f3f2-ea08-76c1-cef6-a22b4a573a7c");</lsl>
* '''[[Http_request|http_request(key id, string method, string body)]]'''
: Event triggered when an URL is hit:
:* id is unique to this request
:* Supported methods are GET/POST/PUT/DELETE
:* body: The body of the request.
: Event also triggered with response to ''llRequestURL'' and ''llRequestSecureURL''
:* id matches the key returned by ''llRequestURL'' or ''llRequestSecureURL''
:* method == [[URL_REQUEST_GRANTED]] for success, [[URL_REQUEST_DENIED]] for failure to get an URL
:* body is the public URL. If unable to get a public URL body will be empty.
* '''[[LlHTTPResponse|llHTTPResponse(key id, integer status, string body)]]'''
: Send ''body'' to the requester with status code ''status''
:* id is the id from http_request that maps to the specific request
:* sending a response to the requestor will clear the request and delete information associated with it
* '''[[LlGetHTTPHeader|string llGetHTTPHeader(key id, string header)]]'''
: Returns the string for the specified header in the specified request. All received headers are converted to lower case and this function is case-sensitive. The returned string is limited to 255 characters.
:* Supported headers are:
::* "x-script-url": The base url, as originally received from [[llRequestURL]] or [[llRequestSecureURL]].
::* "x-path-info": Any trailing path information from the requested url
::* "x-query-string": Any query arguments, the text past a ? in the url
::* "x-remote-ip": IP address of the host that made the request
::* "user-agent": The user-agent header as reported by the requester
:* Supported headers sent by '''[[LlHTTPRequest|llHTTPRequest()]]'''
::* "x-secondlife-shard"
::* "x-secondlife-object-name"
::* "x-secondlife-object-key"
::* "x-secondlife-region"
::* "x-secondlife-local-position"
::* "x-secondlife-local-rotation"
::* "x-secondlife-local-velocity"
::* "x-secondlife-owner-name"
::* "x-secondlife-owner-key"
requested url: ''https://sim3015.aditi.lindenlab.com:12043/cap/a7717681-2c04-e4ac-35e3-1f01c9861322/foo/bar?arg=gra''
x-script-url: ''https://sim3015.aditi.lindenlab.com:12043/cap/a7717681-2c04-e4ac-35e3-1f01c9861322''
x-path-info: ''/foo/bar''
x-query-string: ''arg=gra''
: This header information is valid for 30 seconds, or until [[llHTTPResponse]] is called.
* '''[[Changed|changed(integer change)]]'''
:* [[CHANGED_REGION_START]]: New changed() event triggered on region startup.
* '''[[LlGetFreeURLs|integer llGetFreeURLs()]]'''
: Returns the number of URLs available to this script.

== URL Lifetime Limitations ==
* URLs are '''temporary'''!
* URLs will be lost in the following cases, all detectable by the script events listed with them.
** On object derez/rez: [[on_rez]]
** On script save/reset: ''[[default]] [[state_entry]]() (trickier in multi-state scripts)
** On region cross or TP(attachments): [[changed]]() {{LSLGC|Events|event}}, [[CHANGED_REGION]] and [[CHANGED_TELEPORT]]
** On region restart: [[changed]]() event, ''new'' flag [[CHANGED_REGION_START]]
* When urls are 'lost' it means that all public urls for that script are gone, new ones will need to be requested and the new urls will '''''not''''' resemble the old ones.
* Maintaining persistent URLs will require building or using an external service similar to how [http://en.wikipedia.org/wiki/Dynamic_DNS Dynamic DNS] services work for tying domain names to dynamic IP addresses.

Contributed HTTP-in URL mapping implementations and services:
* A Dynamic DNS service running on Google App Engine (contributed as an example) can be found in the forums here: http://forums.secondlife.com/showthread.php?t=323981
* Static URL service for HTTP-Server with API (under development),can be found [http://lsl.sltools.biz/ here]. (free by SLTools)
* The [http://wiki.apez.biz/URLMap_API Virtual ID URLMap service] provides mapping from a static subdomain of your choice via a REST API (part of the free [http://www.apez.biz Apez Corp] [http://wiki.apez.biz/Development web-services API]).
* Yet another one, running on GAE, with password protected and private domains. http://wiki.secondlife.com/wiki/Public_Object_DNS
* An advanced and extensively featured Dynamic DNS service: [http://lslurl.com LSLurl].
** Second Life Wiki article: [[Lslurl|LSLurl]]

== Resource Limitations ==
* There are a limited number of URLs available in each region, split by land ownership exactly like prim limits.
** Use [[llGetFreeURLs]] to get the exact number of available URLs for the script.
** The number of allowed URLs is the same as the number of allowed prims on the parcel the object is over.
**: ''Object owner does not matter, all objects over a parcel will use the resource pool for that parcel.''
**: ''Like prims, all the parcels owned by the same owner and in the same region share the same pool of resources.''
**: ''If you have two parcels in a region that each support 100 URLs, then you could use all 200 in object(s) on a single parcel.''
** The region's object bonus factor does not apply to available URLs.
**: ''If a parcel has a max of 300 prims in a region with a 2x bonus factor there will only be 150 urls allowed.''
* Each resident has their own unique pool of available URLs with a max of 38 URLs per resident.
** This is 1 per attachment point, but all 38 could be used by a single attachment for example.
* Vehicles are special and lazily moved to resident pools by the following logic:
** Any object that has a resident sitting on it is a 'vehicle'
** Vehicles will use the url resources from the parcel they are over until the cross a parcel border.
**: ''Specifically this prevents anyone from breaking your vending machine by sitting on it and making it a 'vehicle'.''
** When any object using URL resources with a resident sitting on it crosses a parcel boundary the resources will switch to the first sitting resident with enough resources. If no sitting agents have enough resources then the resources from the parcel being moved onto will be used. If even then there are not enough resources to use then the vehicle will be blocked from moving.
**: ''In short we do everything we can to find a pool to host the resources needed by the vehicle, but will block movement if we can't.''
* Parcel Sale: When a parcel is sold such that it changes the total available URLs in the region for either resident (seller or buyer) such that more URLs are being used than are available some objects will be returned.
** The objects returned will be from youngest object to oldest object of those using URLs in each category in order of object category: Temporary, Other, Group, Owner, Selected/Sat upon.
**: ''The '''only''' time objects are possibly returned is when parcels change owner, and only if more resources are being used than allowed.''
**: ''We return youngest temporary objects before older temporary objects before younger 'other' (owned by non-group, non-parcel-owner) objects etc.''

== Other Limitations ==
* Size of the body of the requests will be [[limit]]ed to 2k [[bytes]].
* Size of headers of requests will be limited to 255 bytes. This is per header, not total.
* The size of responses to requests is not currently limited, but this is subject to review during testing.
* The content type of the returned data is always 'text/plain; utf-8'
*: ''Allowing more content type options is a possibility for the future, but not guaranteed.''
* There is a cap of 64 in flight requests per script. This is based on the maximum number of pending events in LSL. After hitting the 64 request limit, the simulator cap server returns '503 Service Unavailable' to the inbound request.
* ''We may throttle the rate we accept hits at the CAP server level as well. This is possible, but has not yet been decided.''
* HTML cannot be used without an external parser, as all output is plain text only. If making such a parser, remember that you should probably restrict access to only Linden Lab HTML URLs as to not have your bandwith stolen.
* It is important to note that when appending a query string to a cap URL there MUST be a trailing slash between the cap guid and the query string token '?'. IE https://sim123.agni.lindenlab.com/cap/f73b4b94-012d-44f2-bd0c-16c328321221?arg=gra will return an HTTP 500, but https://sim123.agni.lindenlab.com/cap/f73b4b94-012d-44f2-bd0c-16c328321221/?arg=gra will succeed.

== Links ==
* [[LSL_http_server/examples | Script Examples]]
* [[LSL_http_server/design | Design Document]]
* Design Jira:{{jira|SVC-1086}}

{{LSLC|HTTP}}
{{LSLC|Communications}}

LSL Alternate Editors

2009-08-05T15:59:32Z

Hugo Dalgleish: /* Windows Editors */ Adding the e editor in, as it can use the lsl textmate bundle

{{LSL Header|ml=*}}
There are several off-world editors available for free or purchase. Some have syntax highlighting for LSL that will make your code easier to follow. At least two will compile and execute a large subset of LSL. Below are some of the more popular editors for use with LSL.

If you have a favorite that is missing from the list, '''please''' feel free to add it.

Projects trying to create and store LSL highlighting files:
*[http://adammarker.org/shill Shill] project
*[http://hilitelsl.googlecode.com HiLiteLSL.GoogleCode.com]

==LSL Integrated Development Environments (coding and testing environments) ==

===[[LSL-Editor]]===

* [http://www.lsleditor.org/ http://www.lsleditor.org/]

LSL-Editor '''for Windows''' is a standalone LSL script '''editor, compiler and debugger'''. Binary code only (not open source).

Its compiler and debugger are already now reasonably accurate, but yet quite totally perfect. Please blog any LSL-Editor bugs you find into such places as our [[LSLEditorBugs|LSL-Editor Bugs]] article.

=== [[LSL-Plus]] ===

[http://lslplus.sourceforge.net/ LSL PLus Eclipse Plugin]

'''For Windows, Mac, and Linux''', the LSL Plus Eclipse plugin is a Editor/Unit Test environment for LSL implemented in Eclipse. It is a FLOSS project (Free/Libre Open Source Software). The latest release (0.11.0 - 2009-05-20) features multi-script execution with '''source level debugging''' (setting breakpoints, single stepping through code, examining variables on the call stack, etc.), making it unique among LSL IDEs. It now supports both multi-script execution in a simulated environment (with avatars, prims, inventory, (limited) physics, etc.) and '''unit''' testing - allowing you to test individual handlers and functions by precisely controlling the setup/teardown and interaction with the execution environment (including support for 'mocking' the LL function call that interact with the script environment). It also has some additional code management features that encourage code re-use without having to cut-and-paste, as well as code '''optimization''' (inlining, constant folding).

By using the Eclipse IDE you get features such as integration with source code control systems like CVS or Subversion, task management, integration with 3rd party bug tracking software, and so on. It supports development on Windows, Mac, and Linux platforms.

==Off-world syntax checker==
You can build a syntax checker yourself and hook it into whatever editor you fancy if you have the viewer source installed and compiled on your machine. The C++ source to build one yourself is [[User:JB_Kraft#Offline_LSL_Syntax_Checker|here (JB Kraft)]].

==Multi-platform Editors==
===ByronStar SL===
Based on [http://eclipse.org Eclipse], the [http://byronstar-sl.sourceforge.net/ ByronStar SL IDE] includes most modern program editor features. It also includes custom features for LSL, such as variable checking, error markers, and code formatting. Eclipse is available for Macintosh, Linux, Windows, and many UNIX flavors.

===Emacs===
There's an [[Emacs LSL Mode]] available on this wiki, which provides syntax highlighting and indentation features. If you want some tips on writing LSL in emacs, read [http://xahlee.org/sl/ls-emacs.html Xah Lee's page]. Emacs is available for many Unix flavors, Macintosh and Windows.

You may come across (and attempt to use) Gary Evan's [http://www.cs.iastate.edu/~leavens/emacs/lsl-mode.el LSL major mode]. It won't work with the Linden Scripting Language, as Gary wrote it for the [http://www.cs.iastate.edu/larch-faq-webboy.html Larch Shared Language].

===vim===
[http://www.vim.org/ vim:] vi improved. A multi-platform evolution of the most classical of the editors: vi. GPL code.
 [http://www.secondlifelab.it/index.php?option=com_remository&Itemid=77&func=select&id=7 Plugins for VIM] for install the syntax, autocompletion, autoident for LSL script into vim

===JOE===
[http://joe-editor.sourceforge.net/ Joe's Own Editor (a.k.a. Joe)] is a comand line editor for unixoid systems. See [[User:Zai Lynch/LSL highlighting in Joe]] for a manual and syntax file download.

===SciTE===
Easy to use, features syntax highlighting, folding, auto complete, help that opens the appropriate wiki page, and is setup to use the c preprocessor, and lslint. 
Windows only [http://sl.sdfjkl.org/secondlife/scite/ SciTE-ez] 
Files for Linux or Windows [http://forums.secondlife.com/showthread.php?t=209219 Forum thread] [http://dimension128.homelinux.net/scite_lsl.tar.gz scite_lsl.tar.gz]

===jEdit===
Developed in Java, this mature, cross-platform editor runs on any operating system with a Java 2 version 1.3 or higher virtual machine. It has all the features you'd expect from a full-GUI text editor. Syntax highlighting and tailored editing behavior is supported through "modes." (You can get the LSL 'modes' file [http://nonbaryonic.no-ip.org/repository/SL/lsl-edit.xml here] {{WFont|fstyle=italic|color=orange|text=updated 5-Feb-09}}.) The editor supports a rich plug-in API; many third-party plug-ins exist to facility editing, formatting, communications, etc. 
You can find jEdit [http://www.jedit.org/ here].

===Shill - LSL Language Files for a Variety of Editors===
Here is a page listing the various LSL language files for a variety of editors: [http://adammarker.org/shill/index.html Shill]. There could be something here for your editor. Links are provided on the page for all files. (Most of the files there will be updated to 1.18.4.3 keywords in the next week or so. I'll update this note when that's done. --[[AdamMarker]])

===Midnight Commander===
[http://www.midnight-commander.org/ GNU Midnight Commander (mc)] is a free cross-platform orthodox file manager and a clone of Norton Commander. 
Midnight Commander is a console application with a text user interface. 
OS: Unix-like, Microsoft Windows 
For Linux see [[User:Kuraiko_Yoshikawa/sandbox/LSL_Goodies/mc]] for a manual and syntax file download.

==Windows Editors==

===e===
The [http://www.e-texteditor.com/ e Editor] is a port of TextMate to Windows, and can use the TextMate LSL bundle listed below.
===Notepad++===
[http://notepad-plus.sourceforge.net/uk/site.htm Notepad++] is probably one of the best Windows editor around. Packed with features, extremely powerful and easy to use for beginners too. Best of all, it is GPL code.

===ConTEXT===
[http://www.context.cx/component/option,com_frontpage/Itemid,1/ ConTEXT] is a small, fast and powerful freeware text editor, developed mainly to serve as secondary tool for software developers.

The following syntax files are available for ConTEXT.
* [http://forum.context.cx/index.php?action=dlattach;topic=1775.0;id=359 Shyan Graves] Last updated March 01, 2007.
* [http://adammarker.org/shill/context/lsl.chl Sir.Grelling] Last updated July 10, 2006.

===Crimson Editor===
[http://www.crimsoneditor.com/ Crimson Editor] is a professional source code editor for Windows.
The following syntax files are available for Crimson Editor.
* [http://www.crimsoneditor.com/english/board/CrazyWWWBoard.cgi?db=file3&mode=read&num=1791 Aakanaar] Last updated September 10, 2006 for Second Life version 1.10.0.

===[[LSL-Editor]]===

* [http://www.lsleditor.org/ http://www.lsleditor.org/]

[[LSL-Editor]] is a standalone Windows LSL '''editor, compiler and debugger'''.
All the usual editing, plus you can compile and execute.

===TextPad [{{HoverText|''C''|Commercial Software}}]===
[http://www.textpad.com/products/textpad/index.html TextPad] is a powerful, but easy to use general purpose text editor. It is a commercial product, but there is a 30 day trial version available for free on the website.

The following syntax files are available for TextPad.
* [[LSL_Editor_TextPad_Syntax | Prodigal Maeterlinck & Patrick2 Chama]] Last updated February 20, 2007. Extracted from the Second Life viewer source code.
* [http://www.textpad.com/add-ons/files/syntax/lsl_.zip Ben Gray] Last updated August 23, 2006. As of version 1.12.0, with the deprecated functions in a separate keyword list.
* [http://www.textpad.com/add-ons/files/syntax/lsl.zip Matthias Huber] Last updated September 23, 2004.
* [[LSL_Editor_TextPad_ClipBook_Events | Events ClipBook]] Last updated March 5, 2007. Based on the LSL Portal event entries.

===UltraEdit-32/UEStudio [{{HoverText|''C''|Commercial Software}}]===
[http://www.ultraedit.com/ UltraEdit-32/UEStudio] is a powerful text, HTML, and HEX editor. It is a commercial editor with a 30 day trial version available at the website. Important features:
* column/block mode editing
* brackets/braces matching
* code-folding
* configurable syntax highlighting via custom [http://www.ultraedit.com/index.php?name=Content&pa=showpage&pid=40#wordfiles wordfiles]
* autocomplete (using keywords defined in the wordfile)
* bookmarks, incremental searching, CTAG support
* automatic conversion between Unix/Dos/MAC/UTF-8, etc
* built-in FTP/SFTP client

The following syntax files are available for UltraEdit
* [[User:Lum Pfohl/LSL Syntax Highlighting For UltraEdit]] Last updated November 28th, 2007.
* [http://podryk.googlepages.com/LSL_Wordfile.txt Podryck Sands] Last updated April 12, 2007.
* [[User:Stryfe Lowell|Stryfe Lowell]] Currently at SL Viewer v1.20.16. Last updated October 3, 2008.

==Macintosh Editors==
===TextMate [{{HoverText|''C''|Commercial Software}}]===

TextMate is a commercial text/program editor from [http://macromates.com/ Macromates] (30 day trial available). You can find details about Piero Padar's well-maintained LSL bundle in the [http://forums.secondlife.com/showthread.php?p=1041958#post1041958 Scripting Tips forum].

===SubEthaEdit [{{HoverText|''C''|Commercial Software}}]===
This a great text editor with extensible language support. It also happens to be an incredible collaborative editor. Info at: http://www.subethaedit.net/

There is a contributed LSL mode by Zarf Vantongerloo. The mode is a little out of date and could use some love. But in general works great, doing syntax hilighting of LSL funcitons and adding a pop-up menu of all functions, states and event handlers to the top of the window.

An updated LSL mode by Mark Lentczner is available now from the SubEthaEditor [http://www.subethaedit.net/modes.html User contributed modes Repository].

===BBEdit and TextWrangler ===
You can get a LSL language plugin for all versions of BBEdit and TextWrangler at [http://blog.elitecoderz.net/wp-trackback.php?p=7 http://blog.elitecoderz.net/]

For older versions of BBEdit (7.0 or less) and TextWrangler, there is additionally a great module available at [http://adammarker.org/bbedit.html http://adammarker.org/bbedit.html]

==Linux Editors==
===Kate===
[http://kate-editor.org/ Kate] is an advanced text editor for KDE. Usually included in all KDE based distributions. 
A [[Kate LSL Mode]] is available on this wiki.
===Gedit===
[http://www.gnome.org/projects/gedit/ Gedit] is an advanced text editor for GNOME. 
See [[User:Kuraiko_Yoshikawa/sandbox/LSL_Goodies/gedit]] for a manual, syntax file and Color Theme download.
===Nano===
Nano is a curses-based text editor for Unix and Unix-like systems. 
Since February 2001, nano is an official part of the GNU Project. 
See [[User:Kuraiko_Yoshikawa/sandbox/LSL_Goodies/nano]] for a manual and syntax file download.

Core Grid Services, Protocols, and Structures VAG

2007-10-26T21:15:00Z

Hugo Dalgleish: /* Members (Stakeholders) */

(this is an initial draft so scope and focus are still fairly open. Please add comments to the [[Talk: 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 --[[User:Zha Ewry|Zah]] 15:20, 23 October 2007 (PDT) )

=Purpose=

The Core Grid Services, Protocols and structure VAG focuses on the grid and web services, the protocols and the overall structure of the AWG's work. Particular attention is focused on creating designs and architecture which is consistent with the nature and approaches of the World Wide Web.

See the [[Architecture Working Group]] and the [[Viewpoint Advocacy Groups]] for more information.

=List of concerns addressed by this viewpoint=
* Modeling services via REST
* Best practices in Web Services Design
* Appropriate uses of C-hhtp, Escrow, and capabilities
* How to handle continuing streams of events (pub/sub) in the architecture
* The overall shape of the design, including concepts such as domains, proxies and computational boundaries.

=Areas not addressed by this viewpoint=

* Implementation of core components behind the architectural boundaries. We will examine such items only to the extent that they drive our core concerns.

* Underlying representations of 3d objects. We may examine efficient encodings, but we will defer 3d issues to the [[Geometry and Physics VAG]]

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

* Category 1
** Use case a
** Use case b

* Category 2
** use case c
** use case d

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

* JIRA1
* JIRA2

=Organization=

== Joining ==

Anyone with an interest in this Viewpoint is welcome to join. You should join the [[AW_Groupies]] group in Second Life.

== In world meetings ==

We meet once a week in-world and more if people are available.

Also members are active on the wiki and in the SLDEV mailing list.

Meetings are scheduled via the "[http://www.google.com/calendar/embed?src=pdd5mpktklo89bgmfgi076mcc4%40group.calendar.google.com SL AW Groupies" google calendar]"

===Meeting Agendas===

* TBD

===Chat Logs===

* TBD

== Modeling Techniques used to express viewpoint ==

None decided.

=External Links=

=Members (Stakeholders)=

:[[User: Zha Ewry| Zha]] - Founder
:[[User: Gareth Ellison| Gareth]] - Generic hacker - you design, i code!
:[[User: Morgaine Dinova|Morg]] - Analyst, interest from [[Scalability VAG|scalability]] and [[Quality Assurance VAG|QA]] viewpoints.
:[[User:Dr Scofield|DrS]] - security, hacker researcher
:[[User:Jesrad Seraph|Jesrad]] - engineer - I solve problems for a living
:[[User:Neas Bade|Neas]] - engineer, developer on OpenSim
:[[User:Hugo Dalgleish|Hugo]] - architect (of sorts)

[[Category: AW Groupies]]

SL Certification

2007-04-23T22:46:27Z

Hugo Dalgleish: /* Resident Participants */

==Overarching Goal==
* Create Second Life Certification as an in-world resource for Residents
==Immediate Goal==
* Develop certification criteria for modeling and scripting
** We are looking for members of the Developer, Instructor, and Volunteer communities to work with Lindens in creating the skills list and certification tasks for those skills in Modeling and in Scripting.
==Description==
Linden Lab is developing certification for the use of key Second Life tools. We’ll begin with in-world building tools and LSL. We believe this will benefit Residents, Developers, and anyone who wishes to use Second Life by clearly identifying both key skills and the holders of those skills. This will also enable the creation of training to build the skills required for certification.
It is Linden Lab's intent to work with an external certification provider to offer certification testing and maintain a list of those Residents who have been certified.
==Linden Participants==
* Glenn Linden
* Eric Linden
* Blue Linden
* Heretic Linden
==Resident Participants==
If you are interested in participating, please add your name below.

* Ceera Murakami (Fox and Ground Construction Company) Texture Artist

* Elle74 Zaftig (Bellissima!/Shoppe74) build/model/textures

* Keiki Lemieux (HUDDLES Games & Gadgets) Building, Scripting, Animations, Textures

* Tre Giles (GiTech/Action Village Paintball) Building, Scripting, Animation, Photography

* Alexander Regent (MageTech LLC) Scripting, website integration, cellphone integration, in-world building

* Sitearm Madonna (Siterma): Sim Scale Project Planning and Management; Structural Builds and Simulator Performance Management; Social Builds and Community Growth Management; Modeling - Architecture, Terraforming, Waterscaping, Landscaping, Soundscaping

* Hugo Dalgleish

==Target Date==
Ready to launch by fall, 2007

==Certification Categories==
Initially, we plan to develop certification for Modeling and Scripting. If these two categories are successful, we will develop, in accordance with your feedback, future areas including but not limited to: Avatar Customization, Terrain/Land Editing, and Land/Estate Management.
===Modeling===
* Architecture
* Furnishings/Interior Design
* Objects
* Weapons and Vehicles
Note: Includes using scripts to animate objects and textures but no writing of scripts
===Scripting===
* Animation
** Note: Animation includes object animation, texture animation and particle systems
* Attachments
* Movement
* Physics & Collisions
* Detection & Sensing
* Asset Management
* Setting Properties
* Communications
* Interacting with external data stores & web content
* Media Management