[
Lists Home |
Date Index |
Thread Index
]
Right on. X3D does include a gzip format (always has) and will have a
binary form as well. Sun donated some nice IP for that but I haven't
kept up with that. Robin Berjon possibly knows about that because the
Web3DC is liaisoned. OTOH, because a binary is a must-have for X3D,
they will keep pushing forward with or without consensus.
>If we use the same ingrediants as we had 10 years ago, we will come up
with the same cake.
I agree, but I'm not too certain we won't come up with a known variant
anyway. Again, the real quantum of hypermedia and multimedia is screen
refresh rate. We can escape the page metaphor, but until holography is
cheap and field effects are reliable as clickstreams, we can't escape
the window metaphor (Mac '86)
Debatable certainly. Has been debated. Maybe we are braver this time.
A next generation browser would upset a lot of Apple carts, take the
'soft-ener out of the wash, and burn up the Helios. ;-)
len
From: Rick Jelliffe [mailto:rjelliffe@allette.com.au]
Bullard, Claude L \(Len\) said:
> For X3D, an example metatag is found in the head similar to HTML:
I suspect it might be worth while looking at a ZIP packaging format for
CLAX. To allow files to be bundled with binary, and to break up the XML
into smaller documents that can be loaded more eagerly/lazily. ODF and
MS have adopted this format, and it makes a deal of sense. (I think
SCORM does too IIRC...) This independent of links and AJAX-ish
background downloads.
For the Web, you dont want metadata per se taking up room in the early
packets: what you want is informaation that can be used to start
populating the visual page/pane ASAP.
Similarly, adopting the STX streaming version of XSLT rather than real
W3C XSLT might make sense too, so that rendering can start as soon as
the stylesheet and enough data appears. If the idea is to build a new
platform (e.g. in Java) to support distros of domain-specific non-HTML
XML browsers that are not supported well by IDE frameworks or HTML
browsers (which is debatable), we don't need to be constrained to use
W3C technology like XSD or XSLT actually. If we use the same ingrediants
as we had 10 years ago, we will come up with the same cake.
|
