[x3d-public] Open Hyperfusion

Joseph D Williams joedwil at earthlink.net
Wed May 15 11:46:13 PDT 2019

➢ to talk openly here 

John: The components of HyperShape are control points

Control points name and define the  simulated and real aspects of observed environment. 
There is a main set of control points that provide nD+1 observer spacetime for main scene content, 
allowing importation of nD content directly into the main nD+1, or, as an embedded, but independent, nD+1. 

John: The components of HyperDocument are characters

The characters document the content addresses, elements, hierarchies, interactivities, initial and expected states, etc. in sufficient detail to allow sharing in diverse environments as expected by the author. 
These characters are available in the same form basically human-readable form to authors and users.

John: The components of HyperMovie are pixels

The pixels are either prerecorded 
(dead nD-1, like prerecorded linear) or 
interactively generated (live, like dom and sai), 
or both or anywhere in-between. 

In the simulation, there is a hypershape operating in a hypermovie as documented in the hyperdocument. 
Maybe the hypermovie always has to be -1D with respect to external hypershapes unless  the hypershape is a part of a hypermovie. 

2 – curve, sound
3 – surface, volume, shape

I think to promote surface from 3 to 2.

4 – moving human

Wow, have you ever looked at the coding for one of these things? 

I hope this leaves plenty of room to talk about details. 
I’m sure we will soon see how all levels of whatever can do can have great style when we can depend upon very basic features of time, DAG, internal/external, event cascade, def/use, and prototype. 

All Best, 

From: John Carlson
Sent: Wednesday, May 1, 2019 1:03 PM
To: X3D Graphics public mailing list
Subject: [x3d-public] Open Hyperfusion

I’m going to talk openly here about my vision of Open Hyperfusion, a combination of multisensor fusion and hypermedia, so people have a record of it, with a nod to Ted Nelson for hypermedia (Ted missed input, except for clicking on links—I don’t think the mouse was invented).
I have experience with at least 3 types of monitors in my career, the vector Textronix 4010,  character terminals, such as the DEC VT100, and today’s raster LEDs monitors (and the prior raster CRTs).   To me, these 3 terminal types epitomize the 3 types of hypermedia.  In addition, PostScript and PDF have 3 types of media, images, text, and 2D shapes (and combinations, which I may get to later).   While text has been either a shape or an image, text is treated specially by most computer programs.

The dimensions of vector or shape are
0 – point
1 – line
2 – curve, sound
3 – surface, volume, shape
3 – volume animation, still human
4 – moving human
5 – crowd of humans
6 -- hypervolume
Let’s call this category HyperShape.   X3D does this well.

The dimensions of raster, image and sound is
0 – pixel or light
1 – light bar
2 – image, sound
3 – movie, surround sound
4 – picture in picture
5 – video chat (picture in picture at multiple locations).
6 – hypermovie
Let’s call this category HyperMovie.   X3D borrows a video or image format.

The dimensions of character or text is
0 – single semaphore
1 – text
2 – table, webpage
3 – book, webapp
4 – shelf, versions of books
5 – shelves or library, website
6 – a library system
7 – hypertext, world wide web, interactive fiction
Let’s call this category HyperDocument.   X3D provides 1 or 2 dimensional text, higher dimensions are borrowed.

Additionally, there is the dimensions of hyperinput:
1 – key or button press (input data—text)
2 – mouse or implement drag, mono microphone, punched card, aperture card, scan, camera (input data—characters, sound, shape, imaging)
3 – web cam, movie camera or stereo microphone, space mouse, scans, imaging (input data--movie, stereo recording)
4 – multisensor fusion. EKG, Catscan, haptic (input data—curves, movies, BVH)
Someone can figure out the dimensionality of X3D sensors. X3D does not do Sound Sensing or  there currently is no sensor for Scanning?

For the media types, there is a variety of interaction with the user:
Still, Animated, Live (broadcast), Interactive , Editable, Configurable, Programmable, Versionable, Debuggable, Testable, Releaseable.

The components of HyperShape are control points
The components of HyperDocument are characters
The components of HyperMovie are pixels

HyperMovies and HyperDocuments are often placed on HyperShapes as textures.  Does X3D support a “HyperDocument Texture”?  If so, is the document live or editable?

Do people agree that a <DocumentTexture url='”foo.html”'> is needed?  Is it realizable today?
In addition, HyperShapes may be placed in HyperDocuments, as canvas items.

That’s all I have right now.


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://web3d.org/pipermail/x3d-public_web3d.org/attachments/20190515/c2d5a570/attachment.html>

More information about the x3d-public mailing list