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 Chat (such as one of these permanent autoconfirmed members).
New Vocabularies: Difference between revisions
Jump to navigation
Jump to search
m (Highlight use case titles) |
No edit summary |
||
| Line 10: | Line 10: | ||
** Ease of implementation (are UAs willing to implement new formats?) | ** Ease of implementation (are UAs willing to implement new formats?) | ||
** Resistance to errors (e.g. not brittle in the face of syntax errors) | ** Resistance to errors (e.g. not brittle in the face of syntax errors) | ||
* '''Migrating from LaTeX to HTML'''<br>Priorities: | * '''Migrating from LaTeX to HTML'''<br>Priorities: | ||
| Line 17: | Line 16: | ||
* '''Writing a document by hand, with inline diagrams imported from a graphics package'''<br>Priorities: | * '''Writing a document by hand, with inline diagrams imported from a graphics package'''<br>Priorities: | ||
** Compatibility with existing graphics packages | ** Compatibility with existing graphics packages | ||
** Scriptable (retained-mode, with DOM support, without requiring cross-frame scripting) | ** 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) | ** 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 documents that include diagrams that include typographically-correct mathematics''' | * '''Writing documents that include diagrams that include typographically-correct mathematics''' | ||
* ''' | * '''Animating Web page content (hypertext, vector graphics) without using script'''<br>Priorities: | ||
** Set or animate sizes, positions, opacities, colors, transforms (basically most attributes and properties) | ** 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) | ** Inlined (for simple web pages) and non-inlined animations (to promote separation of content and presentation) | ||
** Linear and | ** Linear and spline interpolation | ||
* '''Writing highly interactive, graphically intensive sites'''<br>Priorities: | |||
** Searchability | |||
** Accessibility | |||
Philip also wrote [http://www.w3.org/mid/[email protected] a detailed story], which touches on several of the points above, of what we want to enable. In addition to the points above, his requirements include a solution for ID clashes in multiple-document transclution, and a solution for embedding custom non-visible data in an HTML document for scripting purposes. | Philip also wrote [http://www.w3.org/mid/[email protected] a detailed story], which touches on several of the points above, of what we want to enable. In addition to the points above, his requirements include a solution for ID clashes in multiple-document transclution, and a solution for embedding custom non-visible data in an HTML document for scripting purposes. | ||
Revision as of 18:07, 25 March 2008
This page summarises the problems discussed in the e-mails that ended up in the html-parsing-rules-namespaces-discussion folder.
- 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 documents that include diagrams that include typographically-correct mathematics
- Animating Web page content (hypertext, vector graphics) without using script
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
- Writing highly interactive, graphically intensive sites
Priorities:- Searchability
- Accessibility
Philip also wrote a detailed story, which touches on several of the points above, of what we want to enable. In addition to the points above, his requirements include a solution for ID clashes in multiple-document transclution, and a solution for embedding custom non-visible data in an HTML document for scripting purposes.
Supporting data and research
- What is the most widely known way of authoring mathematics?
- What human-editable source language are equations mostly serialised in today?
- Animation is a desired capability for web authors of Rich Internet Applications. Of the top Ajax Javascript toolkits listed on Wikipedia, all support some level of animation, each in a different, and possibly incompatible, way: