Hyv was originally short for Hypervideo when I coined it 6 years ago. It became an architectural (both content architecture and technical architecture) term for the teams I work with for use of and implementation of interactive tv/film/transmedia interface… …where in the data/metadata that would be in the hypervideo would be transportable/interoperable. Further taking it to be “layerable” We have pushed for half a decade for browsers to implement transparent synced layers. The “hyv” layer then would have metadata etc for implementation both with HTML5 & the Hyv layers…making it transferrable to other medium and artifacts. It makes it easier in our specific implementation for interactive film/television, game development that is heavily based on video and platforms outside the screen including augmented reality, transmedia and multi-platform and artifacts in the real world. It has lead to us creating what we call portkeys, wormholes, & horcruxes (artifacts that are keys in the real world)…That are portals within and into and between stories and productions, that link to the outside world and that link to integrated retail. It has also raised the spectre of varying timecodes/timeclocks in story/audience worlds.
We also have been lately using the term in naming an initiative we have been forming between game developers, filmmakers, journalists, web development etc… to Innovate Storycube content architecture via Transmedia and more integrated forms of Content with geo-location, the cloud, the browser, augmented reality and inventing a new writing format for story inception.
What is Hyv?
Advertisement
