Peter Amstutz wrote: > > Online > Collaborative
By virtue of being Online and Collaborative, this means that changes to objects are communicated quickly (except when specificaly buffered or batched for particular reason) allowing users to work together in real time, and to avoid temporary files, managing copies in different places, etc. > > Platform for ... 3D applications > Interreality 3D will not be limited by focusing on a > single-purpose application but rather will be an > "engine" or "platform" that enables development of many > types of 3D applications. This will include 3D games, > social spaces, scientific visualization and education. Visualization doesn't have to be scentific though. > _________________________________________________________ > > 1.2. Multiuser Requirements > > > Users shall be able to use VOIP to communicate in the 3D Change VOIP to "live audio streams" or something, since it won't neccesarily be a current VOIP product being used (on the other hand it might be better to simply provide SIP or other identifiers and let a companion VOIP application do the talking? Then you could hook in to existing systems. Does anyone know what the limitations are for "conference calls" in Skype and others?) > > Users shall be able to establish accounts which persist when > the user is not logged in. > Where "account" means an Identity on some site?. This identity is important for developing reputation and trust, as well as determining capabilities and permissions. ... Users shall be able to save references to other users, group them, and view them in a seperate friends list in the client UI. Users shall be able to subscribe to externally defined groups of users. Friends shall be identified by secure, aunthentic Identities, through UI in the friends list as well as near avatar representations in the 3D world [rephrase that better?] > > At the discretion of the server administrator, the system > shall be able to log all chat messages. > All kinds of events can be logged, not just chat messages. E.g. the fact that user with identity I changed object V at time T resulting in revision R23. This is important for people who need a record of actions for acountability and auditing purposes. > At the discretion of the server administrator, users may be > disconnected and/or banned. The system shall support blocking > based on IP address. ... based on Identity and IP address. > _________________________________________________________ > > 1.4. Platform Requirements > > 1.4.1. Scripts > Scripts shall be subject to the same permissions system as > users, with additional restrictions on cpu and memory usage. Scripts shall access objects through the (remote?) VOS/Vobject API. [neccesary to state that here? it's useful info i think. i.e. it's not some ad-hoc api for scripts, it's pretty general/powerful] > _________________________________________________________ > > 1.4.2. Interactivity > > The virtual world shall be able to specify "clickable" > objects. Users who click on this object in the 3D view will > either send a message to the object or activate a client-side > script. Also hypercards-- objects that link to external resources such as web pages, or include text and/or images to display seperately from the world. > > 1.4.3. Authoring > Users shall be able to create new 3D objects. This shall > include loading meshes from supported file formats, cloning or > instancing existing 3D objects, or by creating and assemblinga > "prims" that represent the desired geometry. Changes "prims" to: geometric primitive shapes. > > Users shall be able to import from a variety of standard 3D > file formats, including X3D and Collada. Should we specify any other formats for import from files? > > X3D (and VRML) shall be supported including the full immersive > profile. There shall be a bidirectional mapping between X3D > and Interreality 3D capabilities and semantics. Should we specify in what situations what parts of X3D and VRML are supported? I.e. are scripts and animations used when you want to create a new object in the world by loading it from a file using the end-user client? Or only when loaded into a server or server plugin designed to run a "Live" vrml world? ... How about something like, all objects (including people/avatars) should have some kind of signature or fingerprint that can be used to authenticate it against external records, e.g. to validate authorship. Can also be later used for stuff like micropayments. Also for caching. ... Users shall be able to edit both 3D and non-3D aspects of world objects using a GUI. This GUI will be available within the Interreality/3D client and as a stand-alone application (not requiring 3D graphics capability). > > The system shall support playing streaming back movies on a > texture. Minimum supported file formats? MPEG? MNG? ... The system shall support rendering of text (both "plain" and formatted using HTML, PostScript or PDF??) on a texture. ... What image file formats are supported at minimum for textures? PNG, GIF, JPEG? SVG? > > 1.5.2. Avatars > > Users shall be given an avatar to represent them in the 3D > space. > ? On connection to a world, right ? (i.e. via a factory) > Users shall be able to select from multiple avatars, and > configure the appearance of their avatar. > This is selecting from multiple options given by the factory? ... What about sound effects in the world? I think we need to have those eventually (i.e. objects that emit discrete sounds or loops from a spatialized 3d position and direction). Reed _______________________________________________ vos-d mailing list [email protected] http://www.interreality.org/cgi-bin/mailman/listinfo/vos-d
