Aha from the capabilities newbie

I had the hardest time figuring out the object capability model, coming from UNIX and Java/C/C++, but I think I finally figured the model out by trying to map JSON onto a file system.  Minecraft might be thought of as almost the opposite of the object capability model, That is, ambient authority.

Classes are objects.  Objects link to class scope items.  Objects may have methods which override the class methods.  Capabilities are granted on object methods—-at least.
Object attribute names are filenames.
Object attribute values are values or “files"
Objects are folders.
Array indexes are "filenames", or integer indexes into a stream, folder, image, window, window server or network of displays.
One dimensional arrays are monoaural sounds or streams or c-list or machine code methods.
Two dimensional arrays are folders, image files a snapshot of a window, or non-monoaural sounds
I'm not sure the next three can be in a capability model.  What do you think?
Three dimensional arrays are windows or video streams or a snapshot of a Minecraft world.
Four dimensional arrays are window systems or window servers or one Minecraft world.
Five dimensional arrays are multiple display or networked displays or multiple Minecraft worlds.

Unforgeable references are links pointing somewhere in the filesystem, which makes the "JSON" a DAG.
Capabilities are integers which assign an authority (read, write, execute, put, get, create, remove, post, delete, head, grant, revoke)  to a value.
Forgeable references are symbolic links.

Values can be integer, number, string, boolean, method, stream, socket, object, array, capability to a value, unforgeable reference, or forgeable reference all of which are in descriptor (capability?) referenced files in the file system.

Here are my questions:
Does anyone have a shell or GUI where I can peruse a file system like this on Mac OS X or Windows?   Does scoopfs have all of this?
What are formal and actual parameters to execute and other authorities called?  Are these classes and objects as well?
Would it be possible to have only REST authorities?
What about non-rectangular shapes on the screen?  How are those handled in the file system?  Probably as objects, I know.  Whither holography?  Is this the best approach for a GUI object capability model?
What's an i-node in object capability terms?
I'm trying to avoid ambient authority or identity in this description, except for forgeable references and Minecraft.  Have I been successful?  What would be an example of a game that represents best the object-capability model?

_______________________________________________
cap-talk mailing list
[email protected]
http://www.eros-os.org/mailman/listinfo/cap-talk