Integration with existing backend systems

Integration with existing backend systems

Peter Haggar 1196714082|%e %b %Y, %H:%M %Z|agohover

A merchant, such as Sears, has their existing 2D web presence and also a virtual showroom in a VW. A user is browsing the Sears 2D site and purchases a camera. This involves logging into his account which has his credit card and shipping information and making the purchase. The e-commerce backend system verifies his credit and places an order with the shipping department to ship the camera to the address listed in the account. Later, the same user is browsing the Sears VW showroom and decides to purchase a TV. The user is able to log into the same account that has his credit card and shipping information. The same backend system verifies his credit and places the order with the shipping department to ship the TV to the address listed in his account. The VW site uses the same e-commerce and customer database backend systems to complete these transactions that originated on their 2D web page.

Data exchange between virtual worlds and back-end data stores

GlennLinden 1198710410|%e %b %Y, %H:%M %Z|agohover

Data Exchange between the Virtual World and RL databases/data services
Action:
I have sensors in a Virtual World that collect data and store them externally in a web-service based database. I want a display in the Virtual World that can take some data from the database via the web service and display it in real time.

Discussion:
This requires a standard set of protocols for interacting with webservices or data content external to the virtual world (Second Life uses LSL: HTTPput and LSL: HTTPget.)

Standards: no standards already exist for the web; not clear there is really a standards opportunity here. While SOAP and similar standards exist for data interchange by back-end systems, it's not clear they are applicable to virtual worlds.