Re: [-empyre-] archiving + preservation
Instead of commenting point by point regarding below, I just want to
say CAW has, in terms of software art, a strong sense of an unspoken
intuitive direction of the dynamic evolution of 'this genre.' It is not
unlike music and art genres where some people start to get it and
explore it, express it, develop it, and exhaust it (some genres are
quickly exhausted, others persist). You know, when a new knowledge
object is created I want my RSS reader to know about it. I want an
instant message that a node has just qualified for persistence-hood in
the knowledge domain of digital arts. I want to feel the presence of my
non-local community - the people who's minds are undergoing a similar
transformative process as a result of the presence of a shared memetic
There are technical aspects of this discussion (IM talking to rdf/xml
you probably know about this: http://space.frot.org/
and more: http://www.zooleika.org.uk/
and foundational aspects:
There was an interesting conference a while back on knowledge
visualization, using cartographic techniques to visualize knowledge
papers from that conference:
In general CAW is creating its knowledge base in a 'quasi-conscious'
way - we are simply participating in discussion (like this note), while
the result of our discussion extends/enhances the map a bit more. This
project might share all the aspects of new gaming techniques/technology
without the feeling that you are simply killing your time, that you are
not 'playing' just to 'win.' Entertainment applications are driving one
sector of the economy, but that's for a limited age group. CAW is a
more substantial application, indeed a research space.
One more thing, for the future: the web is the repository, but a
distributed knowledge base is also a fact of life. Might the critical
os go in the direction of P2P. where do your key interests lie, the
(meta)map or the territory... the conversation or the xml
representation of it. I'm really impressed that you have put the
listserv (discussion space) and wiki together, but my/our email clients
are where the action is happening. you need a 'critical client.' If we
each ran our own 'critical server' and could mark each email received
and sent as private or public than we'd have a really rich (too rich)
distributed knowledge base. The challenge than is mining and mapping.
See google's latest 'feature' of text mining email.
But I'm getting way too far ahead.
I have tried a MUTE (multi-user text environment) as an ontology
I think we discussed MUDs and MOOs when we were first imagining the
online presence of criticalartware, but really, the idea of a scalable
architecture that could be viewed on a cell phone or in real-time 3D
was too attractive.
Would you have plans to use more 'push' techniques - realtime - in
the development of CAW.
Definitely, probably as an outrigger to the current system. That is,
there might be a realtime plug-in. That would allow people to create
3D games that depict other users' movements, etc. I'm also looking at
RSS. It would be great to add the subscription model as well as the
push model, so that you could browse liken on the web, on your
cellphone, as a Playstation game, or as a blog subscription.
That all sounds ridiculously ambitious, but the reality is that most
of the work to support those forms is done (and you can already browse
on a cellphone). The architecture was the hard part. You mention the
Criticalartware OS, and that's something we're looking at for the near
future. I'd like the whole site to run in its own windows (within the
browser), and behave like a "real" OS, with applications, menus and
I downloaded your xml page of nodes, stripped it down, and imported
it into the Protege software. I thank you for this resource and I
hope to utilize that. As you said, the xml file can by used to create
immersive or 3d interfaces and operating systems. I hope to work on
the Mute first. Also, thanks for your visualizations of the node
space - instead of id numbers for your node map, might you put in the
node names (or both, use short names if needed) .
Awesome! I really look forward to seeing what comes out of your
experiments. Although no one has designed a 3rd party interface yet, I
think there are a multitude of interesting possibilities there. And as
we mention within liken, we [welcome/support] critical imaginations of
criticalartware/liken as well...
The nodemap is not likely to change, simply because it's part of a
timelapse now, and I don't want to mess with the code while it's
clicking off frames. I think my concern with putting names (or
shortened names) was that it would become even messier and harder to
read. However, maybe we could do something with putting the name in
the browser's "status" bar, so you could get a sense of what was what.
Powered by MessageSoft SMG SPAM, virus-free and secure email
Powered by MessageSoft SMG
SPAM, virus-free and secure email
This archive was generated by a fusion of
Pipermail 0.09 (Mailman edition) and