In Janus, content is primarily static. The user has no way of bringing dynamic content with them into other rooms, and typically all content lacks persistence between sessions.

When we bring an AssetObject into a webspace, and later reference it, we are primarily talking about it as a single entity, with a few attributes and a model assigned to it. However, the Javascript associated with certain elements of a room is usually a completely separate component.

Currently, we can drag AssetObjects into a room from a webpage. However, we cannot drag full rooms into rooms.

My proposal is for an <Entity> markup element that allows for whole .html pages to be used as objects in rooms. However, in this form, they are not recognised as rooms, but more so as dynamic objects with associated Javascript, shaders and the likes. Essentially exactly what avatars are at the moment. Walking rooms.

Imagine being able to write a room that is a bicycle with a certain javascript, heading to a random page in Janus, and then dragging it out.

Also, entities' Javascripts could be simulated server-side. Using an Entity in your markup would essentially designate that "this object is persistent between users".

A player encounters an entity, alerts the server, and then the server accesses that XML and runs the javascript, sending the users updates on changes in its attributes. Once nobody is in the same room as the Entity, it terminates the simulation.

Of course, this has the potential for abuse, and if you look at the usage of dynamic objects in programs like SecondLife, they're obviously abused to hell. One of the ideas is that, if the content is streamed in through a player (it wasn't placed there in the room HTML), the object asks for permission before it can make changes to your attributes/ load webpages/ etc.

tl;dr Being able to drag rooms into rooms. Essentially would be "entities" that can have associated Javascript. Could also have some element of persistence between users.