A user account is required in order to edit this wiki, but we've had to disable public user registrations due to spam.

To request an account, ask an autoconfirmed user on IRC (such as one of these permanent autoconfirmed members).

Difference between revisions of "New Vocabularies"

From WHATWG Wiki
Jump to: navigation, search
Line 3: Line 3:
 
* '''Writing applications that contain graphics that represent custom data, while including that data for script manipulation.'''<br><code>data-<var>foo</var>=""</code> on any element; <code>element.dataset[<var>foo</var>]</code> for DOM access. ([[CustomData|Other ideas...]])<br>Priorities:
 
* '''Writing applications that contain graphics that represent custom data, while including that data for script manipulation.'''<br><code>data-<var>foo</var>=""</code> on any element; <code>element.dataset[<var>foo</var>]</code> for DOM access. ([[CustomData|Other ideas...]])<br>Priorities:
 
** Embedding custom non-visible data in an HTML document for scripting purposes ✓‬
 
** Embedding custom non-visible data in an HTML document for scripting purposes ✓‬
 +
** Forward compatible (so that future extensions don't introduce name clashes) ✓‬
 
** Ability to avoid ID clashes in multiple-document transclution
 
** Ability to avoid ID clashes in multiple-document transclution
** Forward compatible (so that future extensions don't introduce name clashes)
 
  
 
* '''Ability for an author to unilaterally extend the language to address problems we are currently unaware of and that therefore are not covered by existing functionality.'''<br>Priorities:
 
* '''Ability for an author to unilaterally extend the language to address problems we are currently unaware of and that therefore are not covered by existing functionality.'''<br>Priorities:

Revision as of 06:35, 28 March 2008

This page summarises the problems discussed in the e-mails that ended up in the html-parsing-rules-namespaces-discussion folder.

  • Writing applications that contain graphics that represent custom data, while including that data for script manipulation.
    data-foo="" on any element; element.dataset[foo] for DOM access. (Other ideas...)
    Priorities:
    • Embedding custom non-visible data in an HTML document for scripting purposes ✓‬
    • Forward compatible (so that future extensions don't introduce name clashes) ✓‬
    • Ability to avoid ID clashes in multiple-document transclution
  • Ability for an author to unilaterally extend the language to address problems we are currently unaware of and that therefore are not covered by existing functionality.
    Priorities:
    • Without trampling on the toes of others
    • Without being beholden to an external entity to provide the enhancements for the author on a timescale that is useful to the author
  • Putting an equation in a Web page.
    Priorities:
    • Maintainability
    • Searchability
    • Accessibility
    • Typographically-sound printing
    • Ease of authoring (are authors willing to learn new formats?)
    • Ease of import from existing documents
    • Ease of implementation (are UAs willing to implement new formats?)
    • Resistance to errors (e.g. not brittle in the face of syntax errors)
  • Migrating from LaTeX to HTML.
    Priorities:
    • Fidelity
  • Writing a document by hand, with inline diagrams imported from a graphics package.
    Priorities:
    • Compatibility with existing graphics packages
    • Scriptable (retained-mode, with DOM support, without requiring cross-frame scripting)
    • Round-tripping (the ability to take image fragments from a Web page and edit them)
    • Ease of implementation (are UAs willing to implement new formats?)
    • Resistance to errors (e.g. not brittle in the face of syntax errors)
  • Writing a document by hand, with vector graphic icons.
    Priorities:
    • Maintainability
    • Good caching behaviour
  • Mixing vector graphics, mathematics, and other features.
    Priorities:
    • Diagrams that include typographically-correct mathematics
    • Formulae that include vector graphics
    • Formulae and diagrams that contain form controls
  • Animating Web page content (hypertext, vector graphics).
    Priorities:
    • Set or animate sizes, positions, opacities, colors, transforms (basically most attributes and properties)
    • Time-based triggering, event-based triggering
    • Inlined (for simple web pages) and non-inlined animations (to promote separation of content and presentation)
    • Linear and spline interpolation
    • Syndication: animation shouldn't use scripts that can't be trusted by syndicators
    • Quality: animation should adapt to the frame rate capabilities of the device, not be forced to use a particular frame rate by a script
  • Writing highly interactive, graphically intensive sites.
    Priorities:
    • Searchability
    • Accessibility
  • Including XBL2 inline in a text/html document the same way CSS and JS can be included inline.
    Priorities:
    • Expressiveness (anything expressed in XBL2 as text/xml should be possible in text/html)

Areas for research

  • What is the most widely known way of authoring mathematics?
  • What human-editable source language are equations mostly serialised in today?

Supporting data