On 3 Jul 2003 at 15:05, cdent@blueoxen.org wrote: (01)
[...]
>
> Could you provide a use case, a demo, or a narrative demo of some
> sort? I don't think I get it. (02)
OK. I don't have a concrete demo yet. But here's one possible use I'm
thinking of. (03)
Think of Jack Park's NexistWiki. Each Addressable Information
Resource (AIR) has it's own page; Each AIR has properties, components
it is linked to, subjectIdentity, and relevant information associated
with that AIR. (04)
Now say you want to pass an AIR into someone else's wiki. Because
content is copyrighted, you might not want to pass the content of the
AIR but merely transclude it in the partner wiki. So you pass a
themic representing the AIRs properties, links, etc. (05)
In NexistWiki, if I understand it correctly, the content actually
sits in a database, then an AIR aggregates it, and finally a Page
object creates the display. But the correlation between AIRs and
Pages in NexistWiki is one to one. (06)
Similarly a themic (or set of themics) is the middle tier aggregator
of content prior to presentation to the user. But a themic can
aggregate addressable content from several pages if needed. (07)
This is similar to full-on Topic Maps, but the unit of transmission
is always the single type 'themic', and I don't enforce themic merger
as part of the specification (OK, I haven't written that bit up there
yet) because I firmly believe application designers should have
complete freedom to choose how to play with the information prior to
presentation to the user. (08)
Does that help? (09)
>
> --
> Chris Dent cdent@blueoxen.org
> Once you knew, once you really, really knew,
> then you had lost your alibi. --Samantha Power
>
> --
> This message is archived at:
>
> http://collab.blueoxen.net/forums/cgi-bin/mesg.cgi?a=tools-yak&i=Pine.
> LNX.4.30.0307031504250.23373-100000@hot.burningchrome.com
>
> (010)
--
This message is archived at: (011)
http://collab.blueoxen.net/forums/cgi-bin/mesg.cgi?a=tools-yak&i=3F04B09B.27268.10C079@localhost (012)
|