Talk:HDi (interactivity)

From Wikipedia, the free encyclopedia

[edit] iHD name change

Microsoft has changed the name of their Interacive HD interface from iHD to HDi. --(Anonymous)

Apparently the official name is "Advanced Navigation" and the internal code names have been "iHD" and "HDi". Unfortunately this fact is difficult to cite with certainty. EngadgetHD had MS's Kevin Collins talk about the name changes on their podcast (theres a news post about it) but blogs and podcasts aren't exactly encyclopedia-strength sources. The only thing that can be proven with some certainty is that the original name of the standard was "iHD". In the official XML Namespace for HDi, it is called "iHD". --208.242.14.101 06:10, 3 February 2007 (UTC)

[edit] Open Spec?

Article says that it is an open specification, which I believe is incorrect. Microsoft published some tools for authoring HDi, and maintains a forum and a blog concerning it. The only way to get the complete specification, however, is to sign a NDA and pay $5000 to the DVD Forum. The open parts are css, Javascript, and SMIL, which are all approved by w3c. The important parts, though, such as Javascript methods and xml syntax, are only available through the spec that requires an NDA. 75.100.252.46 04:56, 14 April 2007 (UTC)

It depends on your definition of "open." The HD DVD specification is created by the DVD Forum (which is comprised of many different companies) and not by any individual company, although of course any given section of the specificaion originiated from a proposal made by one or more individual companies. Case in point: the interactive layer was proposed by Microsoft and Disney, but it was accepted by all companies and the final version in the specification has had contributions from other companies such as Sonic Solutions and Toshiba. The point being that no single company controls the format; the other member companies must agree to the proposal in order for it to pass. Clearly this doesn't meet some definitions of "open" since the specification is still covered by copyright and implementing it requires paying royalties, etc. but it is also not wholly proprietary, either. Peter Torr (MSFT) 17:10, 28 October 2007 (UTC)

[edit] Proposal to move information to new "Advanced Content" page

Since HDi is a Microsoft trademark, I propose moving the non-trademark-related information into a new page for Advanced Content and linking to that from here. Additionally, I would probably want to re-write some of the content to be clearer in the process. Failing that, we will have to duplicate all the content from here on that page and make sure that the separation is clean. Any thoughts or objections? Peter Torr (MSFT) 17:20, 28 October 2007 (UTC)

IMO, you should go ahead with the split. Or at least propose a structure. With that in place, it will be much easier to judge the merits of the two versions. --soum talk 16:43, 29 October 2007 (UTC)
I see that Advanced Content has been created now. I'm happy with the split. --Harumphy 12:27, 31 October 2007 (UTC)
(slightly off topic) Regarding the actual split of the content, the Advanced Content article should get information about the specification, this one regarding the leading implementation (HDi). What can be done should be ddetailed in the Advanced Content page; how it is achieved in the HDi article. No one interested in the spec should be overwhelmed with information like whether the JS is interpreted or compiled in HDi. That should be in the HDi article. Much content duplication won't be necessary. We can refer to either article as necessary (probably a one liner summarized clarification may be included if necessary).
Whichever way you (Peter) structure the articles, I would like the HDi article to answer the following questions, apart from the markup and JS API details:
  1. Does the markup language have any name?
  2. Is the JS interpreted or JITted?
And the Advanced Content article providing details about the networking (protocols usable: only HTTP(S?) and persistent storage capabilities (any limitations on what can be locally stored?). --soum talk 12:53, 31 October 2007 (UTC)
All agreed. I've cut and pasted the generic stuff into the new article and done a few tweaks to get us started. There's plenty of room for improvement--Harumphy 10:24, 4 November 2007 (UTC)