RE: hypermedia affordances
This is dr;tl for some of you. Sorry... so I am trimming the reply list out of respect for your time. That is usually the problem of a one size fits all, but because I am not involved with HTML5 nor do I understand its raison d'etre, I defer to those who are and do. Noodling is the royal road to innovation but with Google and Apple slugging it out in court, I am unsure of what will become of HTML5. XML doesn't need hypermedia affordances to succeed in the tasks for which it was specified. Does JSON? Now that is quite a different argument from there being a useful set of hypermedia affordances that become the norm for all hypermedia applications on the web including those using XML or MicroXML. I would understand John's reluctance to include them because he and James have envisioned different goals. Selah. For example, VRML97 did not use XML syntax. It could have but XML was not ready when it was spec'd and SGML was too heavy for a real-time 3D application. It was interoperable through the container API and that was quite limited. It did have the concept of click and go but it worked very differently at the technical level of the control. What it shared was http syntax which meant it could open a window with a contained resource. On the other hand, traversing to a different part of the world was not an HTML style hyperlink. It is a jump cut (different medium; different affordance; it inherited movie argot and style for valid reasons (objects in motion)). Then X3D was created to make it possible to use XML syntax and namespaces for real-time 3D. It has namespaces but once again, it still interoperates with different media through the container API, eg, the browser although originally VRML worked in a VRML browser not an HTML browser and they were both web browsers. The idea here is a web browser is not an HTML browser; it is a framework of objects that any application accessing the web can use and HTML is just one. That is how hypermedia worked prior to the web: it IS the operating system GUI. Now WebGL is attempting to side step that to put the 3D affordances lower in the application stack or "closer to the metal" to take advantage of late breaking display technology (hardware and firmware). It may get an XML language on top and it may be X3D but likely not because of the personal and company politics among those writing the specs. Life among the mammals. A compelling reason for SGML, architectural forms and so on was/is to keep semantics from being captured **by a language or company**. Otherwise putting it in the language A) Inhibits innovation, the treacle effect of distribution. B) Inhibits access, see the Patent Wars. There are some long brutal threads on that topic somewhere in the W3C archives. This is why what Liam is suggesting is good advice. Study all the examples you can find, not just HTML and find the best way to express those requirements without adopting something owned or locked up. As Liam says you aren't likely to get more support than that from this community precisely because we do have experience. We aren't antithetical; but that is the way to get it accepted and it may be a slow long slog. We have learned from hard experience that attempting to standardize or create outside the legal umbrella of a consortium or other organization with transparent norms guarantees capture if the affordances have value. Again, life among the mammals. You can't leave gold in the village square without a wall or guards. For something as important as this if successful you absolutely must have that legal umbrella. Otherwise it will be captured or it will die and then be resurrected under different norms, scrubbed of the names of the originators and a new army of orcs will arise. Remember what orcs are made of. Their souls aren't happy about it. len -----Original Message----- From: Rushforth, Peter [mailto:Peter.Rushforth@NRCan-RNCan.gc.ca] Sent: Friday, July 06, 2012 1:42 PM To: Len Bullard; John Cowan; Mike Sokolov Cc: David Lee; Michael Kay; firstname.lastname@example.org Subject: RE: hypermedia affordances > HTML5 appears ready > to cast off all other applications to become "the one true Ark" On The > Web. I think that makes it an easier target for sinking but.... I think the problem with html is that it is trying to swallow the semantics of the world inside text/html. I think the problem with xml is that it doesn't have hypermedia affordances. XML is complex because it needs to be in every environment where semantics are necessary. The solution is to cooperate, IMHO. Hypermedia affordances that we can all live with would be a good start. Where is Gandalf when you need him?! Peter
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index]
PURCHASE STYLUS STUDIO ONLINE TODAY!
Purchasing Stylus Studio from our online shop is Easy, Secure and Value Priced!
Download The World's Best XML IDE!
Accelerate XML development with our award-winning XML IDE - Download a free trial today!
Subscribe in XML format