> At the risk of devaluing the currency, I really have to interject my
> 2 cents here.
> > > Both data and code are fossilized behavior. One cannot
> > > specify behavior in a static medium any more than one can
> > > identify data in a dynamic medium.
> I beg to differ here. While XML and SGML are primarily oriented
> towards static data, HyTime is not. The basic premise in HyTime is
> that if you can address it, you can identify it. Using HyTime there
> is no reason why you cannot identify data in a dynamic medium. It is
> perfectly feasible to identify segments of a sound fragment, frames
> of a video or the results of computations.
> HyTime rules!
1. SMIL, the Synchronized Multimedia Intergation Language,
http://www.w3.org/TR/WD-smil.html , in conjunction with the XLL link model
encompasses a wide swath of HyTime functionality. It promises to deal
reasonably with temporal "documents" by making multimedia elements logically
adressable "the scene with the shoe" vs. "35.43 seconds in")
2. I'm not sure what's static or dynamic about XML/SMIL or HyTime (also an
SGML application, btw). The actual event logs can be static or generated
dynamcially; the logical timelines seem to be equally expressive. But, I'll
confess to never having properly understood HyTime. Perhaps you can