Slideshow Transcript

1. Slide 1: Mundos virtuales
2. Slide 2: Del ciberespacio al metaverso 1992 Metaverso Cyberspacio 1984
3. Slide 3: ¿Cambio de metáfora? MATRIX
4. Slide 4: Second first – Life is life
5. Slide 5: Elementos básicos HTTP cHTTP – certified HTTP REST LSL – Linden Scripting Language LLSD – Linden Lab Structured Data http://wiki.secondlife.com/wiki/Main_Page
6. Slide 6: Funcionamiento ..Each \"sim\" or simulator of a portion of the virtual world in Second Life is created on a server running Debian GNU/Linux, Apache, Squid and MySQL; currently there are several thousand of these PC boxes. To allow for fast response times, the virtual world is sent not as pixels or even as a mesh, but as a series of 3D primitives - \"prims\". The Second Life client creates the world by converting the stream of information about prims and their position into a visual representation...
7. Slide 7: Arquitectura Grid http://wiki.secondlife.com/wiki/Main_Page
8. Slide 8: Dominios separados http://wiki.secondlife.com/wiki/Main_Page
9. Slide 9: Escalabilidad http://wiki.secondlife.com/wiki/Main_Page
10. Slide 10: Multiversos
11. Slide 11: Identidad
12. Slide 12: Laws of identity 1. User Control and Consent. Technical identity systems must only reveal information identifying a user with the user’s consent 2. Minimal Disclosure for a Constrained Use. The solution that discloses the least amount of identifying information and best limits its use is the most stable long-term solution. 3. Justifiable Parties. Digital identity systems must be designed so the disclosure of identifying information is limited to parties having a necessary and justifiable place in a given identity relationship. 4. Directed Identity. A universal identity system must support both “omni-directional” identifiers for use by public entities and “unidirectional” identifiers for use by private entities, thus facilitating discovery while preventing unnecessary release of correlation handles. 5. Pluralism of Operators and Technologies. A universal identity system must channel and enable the inter-working of multiple identity technologies run by multiple identity providers 6. Human Integration. The universal identity metasystem must define the human user to be a component of the distributed system integrated through unambiguous human-machine communication mechanisms offering protection against identity attacks. 7. Consistent Experience Across Contexts. The unifying identity metasystem must guarantee its users a simple, consistent experience while enabling separation of contexts through multiple operators and technologies. http://www.identityblog.com/stories/2004/12/09/thelaws.html
13. Slide 13: mIDm 1. A user tries to access a page on a service to which a login is required. 2. The service obtains the user's mIDm server location from the user's browser header 3. The service redirects the user to the user's mIDm server along with a secret code 4. The user logs on to the mIDm server (typically using cookies) and stores the secret code on the mIDm server 5. The mIDm server returns the user to the service 6. The service then independently checks the mIDm server to see whether the code has been stored 7. The mIDm server returns the code and requested user information to the service 8. On receiving the code, the service is satisfied, and proceeds to log in the user http://www.downes.ca/cgi-bin/page.cgi?post=32667
14. Slide 14: OpenID – ¿Qué es? OpenID es un mecanismo de SSO distribuido Es un URI antoniofumero.myopenid.com https://irss.dit.upm.es/move/users/amfumero
15. Slide 15: OpenID – Elementos Identity provider Relying party End user / user agent
16. Slide 16: OpenID – ¿Cómo funciona?
17. Slide 17: OpenID – Elementos Identity provider Relying party End user / user agent
18. Slide 18: I4U – Mobile 2.0
19. Slide 23: SPAIN IS DIFFERENT