User:Annie Obscure

Flubber World Entity/Properties

Flubber World had a notion of additional areas of interest - leaving an AOI marker behind made that area local for things like chat.

Entities

• Users- the representations of the real people making use of Flubber World
• Layers - sets of other entities. An entity can be in any number of layers. Layers

are themselves entities.

• Topology - underlying world is spherical WGS-84
• Services - imagine WSDL, a definition of what 'services' an entity provides.
• 'entities' (map lines and markings, basicly - in subclasses)
• POI - a defined point
• a balloon - a piece of chatted HTML text in a balloon

Ubiquitous properties

These are properties that every entity has.

• key
• owner
• permissions
• z depth (not height, draw order)
• a 2.5D flag
• height
• existance time, with a complex crontab like '3am to 5pm on tuesdays' type syntax
• arbitrary metadata
• Services

Common properties

These are properties that some entities have.

• merge object (how the object is represented if you zoom way the heck out)
• behavior ( definition of how the object 'behaves' - think LSL)
• physical state (velocity, mostly)

Shared properties

These are properties that have similar meaning for seperate entities, but aren't common or ubiquitous.

Some of the metadata is meaningful to parts of the system.

Special properties

These are properties that only exist for individual entities.

Users

• email, etc.
• owned entities

Layers

• set of entities - (note that a layer of users is a group)
• permissions (who can modify membership in the layer)
• owner

Topology

this is unique and not really an entity, but I thought it was importnat to say the world's not flat.

Services

• tags (like, hamburgers are a service of a restaurant)
• reviews

'Entities'

• Have a distributed existance (possibly over a very large area, e.g. North America)
• might not have volume or area
• in classes that have special per class p

POI

• actually an 'Entity', but POI's have services

balloons

• HTML text content
• speaker (which could be any sort of entity, pretty much)

in practice of course there are some combinations that don't occur. There's no way to make a layer or a service emit a balloon.