New Vocabularies - Revision history

Annevk: /* Supporting data */

2011-01-26T12:12:18Z

Supporting data

← Older revision		Revision as of 12:12, 26 January 2011
Line 78:		Line 78:
	** [http://developer.yahoo.com/yui/animation/ YUI]		** [http://developer.yahoo.com/yui/animation/ YUI]

	[[Category:~~Feature Request~~]]		[[Category:Proposals]]

Mabdul: adding Category:Feature Request

2008-12-01T11:28:05Z

adding Category:Feature Request

← Older revision		Revision as of 11:28, 1 December 2008
Line 77:		Line 77:
	** [http://wiki.script.aculo.us/scriptaculous/show/VisualEffects script.aculo.us]		** [http://wiki.script.aculo.us/scriptaculous/show/VisualEffects script.aculo.us]
	** [http://developer.yahoo.com/yui/animation/ YUI]		** [http://developer.yahoo.com/yui/animation/ YUI]

			[[Category:Feature Request]]

Hixie at 13:01, 5 April 2008

2008-04-05T13:01:02Z

← Older revision		Revision as of 13:01, 5 April 2008
Line 13:		Line 13:

	See: http://www.whatwg.org/specs/web-apps/current-work/#embedding		See: http://www.whatwg.org/specs/web-apps/current-work/#embedding

	~~== WIP ==~~

	~~See [[New Vocabularies Solution]] for notes on the solution being developed.~~

	* '''Putting an equation in a Web page.'''<br>Proposal: make <math> enter [[New Vocabularies Solution\|a new insertion mode]] in which non-HTML elements end up in the MathML namespace ([[Equations in HTML\|Other ideas...]])<br>Priorities:		* '''Putting an equation in a Web page.'''<br>Proposal: make <math> enter [[New Vocabularies Solution\|a new insertion mode]] in which non-HTML elements end up in the MathML namespace ([[Equations in HTML\|Other ideas...]])<br>Priorities:
Line 44:		Line 40:
	** Formulae that include vector graphics ✓		** Formulae that include vector graphics ✓
	** Formulae and diagrams that contain form controls ✓		** Formulae and diagrams that contain form controls ✓

			* '''Writing highly interactive, graphically intensive sites.'''<br>Proposal: SVG, SVG's SMIL, and scripting ([[Interactive Sites\|Other ideas...]])<br>Priorities:
			** Searchability ✓
			** Accessibility ✓

			== Rejected requirements ==

	* '''Animating Web page content (hypertext, vector graphics).'''<br>Proposal: Use the CSS animation proposal ([[Animation in HTML\|Other ideas...]])<br>Priorities:		* '''Animating Web page content (hypertext, vector graphics).'''<br>Proposal: Use the CSS animation proposal ([[Animation in HTML\|Other ideas...]])<br>Priorities:
Line 53:		Line 55:
	** Syndication: animation shouldn't use scripts that can't be trusted by syndicators ✓✘ ''(Somewhat.)''		** Syndication: animation shouldn't use scripts that can't be trusted by syndicators ✓✘ ''(Somewhat.)''
	** Quality: animation should adapt to the frame rate capabilities of the device, not be forced to use a particular frame rate by a script ✓		** 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.'''<br>Proposal: SVG, SVG's SMIL, and scripting ([[Interactive Sites\|Other ideas...]])<br>Priorities:
	** Searchability ✓
	** Accessibility ✓

	~~== Rejected requirements ==~~

	* '''Migrating from LaTeX to HTML.'''<br>Proposal: a tool? ([[LaTeX to HTML\|Other ideas...]])<br>Priorities:		* '''Migrating from LaTeX to HTML.'''<br>Proposal: a tool? ([[LaTeX to HTML\|Other ideas...]])<br>Priorities:

Hixie at 00:13, 5 April 2008

2008-04-05T00:13:39Z

← Older revision		Revision as of 00:13, 5 April 2008
Line 1:		Line 1:
	This page summarises the ''problems'' discussed in the e-mails that ended up in the [http://www.whatwg.org/issues/#html-parsing-rules-namespaces-discussion html-parsing-rules-namespaces-discussion] folder~~. See [[New Vocabularies Solution]] for notes on the solution being developed~~.		This page summarises the ''problems'' discussed in the e-mails that ended up in the [http://www.whatwg.org/issues/#html-parsing-rules-namespaces-discussion html-parsing-rules-namespaces-discussion] folder.

	== Specified ==		== Specified ==
Line 15:		Line 15:

	== WIP ==		== WIP ==

			See [[New Vocabularies Solution]] for notes on the solution being developed.

	* '''Putting an equation in a Web page.'''<br>Proposal: make <math> enter [[New Vocabularies Solution\|a new insertion mode]] in which non-HTML elements end up in the MathML namespace ([[Equations in HTML\|Other ideas...]])<br>Priorities:		* '''Putting an equation in a Web page.'''<br>Proposal: make <math> enter [[New Vocabularies Solution\|a new insertion mode]] in which non-HTML elements end up in the MathML namespace ([[Equations in HTML\|Other ideas...]])<br>Priorities:

Hixie at 00:09, 5 April 2008

2008-04-05T00:09:45Z

← Older revision		Revision as of 00:09, 5 April 2008
Line 1:		Line 1:
	This page summarises the ''problems'' discussed in the e-mails that ended up in the [http://www.whatwg.org/issues/#html-parsing-rules-namespaces-discussion html-parsing-rules-namespaces-discussion] folder. See [[New Vocabularies Solution]] for notes on the solution being developed.		This page summarises the ''problems'' discussed in the e-mails that ended up in the [http://www.whatwg.org/issues/#html-parsing-rules-namespaces-discussion html-parsing-rules-namespaces-discussion] folder. See [[New Vocabularies Solution]] for notes on the solution being developed.

			== Specified ==

	* '''Writing applications that contain graphics that represent custom data, while including that data for script manipulation.'''<br>Proposal: <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>Proposal: <code>data-<var>foo</var>=""</code> on any element; <code>element.dataset[<var>foo</var>]</code> for DOM access. ([[CustomData\|Other ideas...]])<br>Priorities:
Line 9:		Line 11:
	** Without trampling on the toes of others ✓‬		** 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 ✓‬		** Without being beholden to an external entity to provide the enhancements for the author on a timescale that is useful to the author ✓‬

			See: http://www.whatwg.org/specs/web-apps/current-work/#embedding

			== WIP ==

	* '''Putting an equation in a Web page.'''<br>Proposal: make <math> enter [[New Vocabularies Solution\|a new insertion mode]] in which non-HTML elements end up in the MathML namespace ([[Equations in HTML\|Other ideas...]])<br>Priorities:		* '''Putting an equation in a Web page.'''<br>Proposal: make <math> enter [[New Vocabularies Solution\|a new insertion mode]] in which non-HTML elements end up in the MathML namespace ([[Equations in HTML\|Other ideas...]])<br>Priorities:

Hixie at 22:44, 3 April 2008

2008-04-03T22:44:55Z

Hixie at 06:05, 3 April 2008

2008-04-03T06:05:10Z

← Older revision		Revision as of 06:05, 3 April 2008
Line 1:		Line 1:
	This page summarises the ''problems'' discussed in the e-mails that ended up in the [http://www.whatwg.org/issues/#html-parsing-rules-namespaces-discussion html-parsing-rules-namespaces-discussion] folder.		This page summarises the ''problems'' discussed in the e-mails that ended up in the [http://www.whatwg.org/issues/#html-parsing-rules-namespaces-discussion html-parsing-rules-namespaces-discussion] folder. See [[New Vocabularies Solution]] for notes on the solution being developed.

	* '''Writing applications that contain graphics that represent custom data, while including that data for script manipulation.'''<br>Proposal: <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>Proposal: <code>data-<var>foo</var>=""</code> on any element; <code>element.dataset[<var>foo</var>]</code> for DOM access. ([[CustomData\|Other ideas...]])<br>Priorities:

Hixie at 02:45, 3 April 2008

2008-04-03T02:45:31Z

← Older revision		Revision as of 02:45, 3 April 2008
Line 1:		Line 1:
	This page summarises the ''problems'' discussed in the e-mails that ended up in the [http://www.whatwg.org/issues/#html-parsing-rules-namespaces-discussion html-parsing-rules-namespaces-discussion] folder.		This page summarises the ''problems'' discussed in the e-mails that ended up in the [http://www.whatwg.org/issues/#html-parsing-rules-namespaces-discussion html-parsing-rules-namespaces-discussion] folder.

	~~== Requirements met ==~~

	* '''Writing applications that contain graphics that represent custom data, while including that data for script manipulation.'''<br>Proposal: <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>Proposal: <code>data-<var>foo</var>=""</code> on any element; <code>element.dataset[<var>foo</var>]</code> for DOM access. ([[CustomData\|Other ideas...]])<br>Priorities:
Line 22:		Line 20:
	** 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) ✓
	** Numbering the equation ✓ ''(Using, e.g. the <code>title</code> attribute and CSS.)''		** Numbering the equation ✓ ''(Using, e.g. the <code>title</code> attribute and CSS.)''

	~~== Still being considered ==~~

	* '''Writing a document by hand, with inline diagrams imported from a graphics package.'''<br>Proposal: allow SVG in text/html by hard-coding a bunch of SVG element tag names and attributes in the parser ([[Diagrams in HTML\|Other ideas...]])<br>Priorities:		* '''Writing a document by hand, with inline diagrams imported from a graphics package.'''<br>Proposal: allow SVG in text/html by hard-coding a bunch of SVG element tag names and attributes in the parser ([[Diagrams in HTML\|Other ideas...]])<br>Priorities:

Hixie at 02:00, 1 April 2008

2008-04-01T02:00:17Z

← Older revision		Revision as of 02:00, 1 April 2008
Line 12:		Line 12:
	** Without being beholden to an external entity to provide the enhancements for the author on a timescale that is useful to the author ✓‬		** 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.'''<br>Proposal: allow Presentational MathML in text/html by hard-coding ~~a bunch of MathML element~~ tag names in the parser, with end tags made optional where possible ([[Equations in HTML\|Other ideas...]])<br>Priorities:		* '''Putting an equation in a Web page.'''<br>Proposal: allow the 34 Presentational MathML 2.0 elements to be used in text/html by hard-coding those tag names in the parser, with end tags made optional where possible ([[Equations in HTML\|Other ideas...]])<br>Priorities:
	** Maintainability ✓ ''(Somewhat: MathML is pretty verbose, but omitting end tags helps a lot; disallowing Content MathML helps too.)''		** Maintainability ✓ ''(Somewhat: MathML is pretty verbose, but omitting end tags helps a lot; disallowing Content MathML helps too.)''
	** Searchability ✓ ''(Somewhat: more complex maths might be better handled if Content MathML was available.)		** Searchability ✓ ''(Somewhat: more complex maths might be better handled if Content MathML was available.)

Hixie at 01:59, 1 April 2008

2008-04-01T01:59:23Z

← Older revision		Revision as of 01:59, 1 April 2008
Line 1:		Line 1:
	This page summarises the ''problems'' discussed in the e-mails that ended up in the [http://www.whatwg.org/issues/#html-parsing-rules-namespaces-discussion html-parsing-rules-namespaces-discussion] folder.		This page summarises the ''problems'' discussed in the e-mails that ended up in the [http://www.whatwg.org/issues/#html-parsing-rules-namespaces-discussion html-parsing-rules-namespaces-discussion] folder.


	== Requirements met ==		== Requirements met ==
Line 58:		Line 57:

	* '''Migrating from LaTeX to HTML.'''<br>Proposal: a tool? ([[LaTeX to HTML\|Other ideas...]])<br>Priorities:		* '''Migrating from LaTeX to HTML.'''<br>Proposal: a tool? ([[LaTeX to HTML\|Other ideas...]])<br>Priorities:
	** Fidelity ✓ '''(Depends mostly on the tool, assuming CSS, SVG, and MathML support everything LaTeX does.)'''		** Fidelity ✓ ''(Depends mostly on the tool, assuming CSS, SVG, and MathML support everything LaTeX does.)''

	* '''Including XBL2 inline in a text/html document the same way CSS and JS can be included inline.'''<br>Proposal: ? ([[XBL2 in HTML\|Other ideas...]])<br>Priorities:		* '''Including XBL2 inline in a text/html document the same way CSS and JS can be included inline.'''<br>Proposal: ? ([[XBL2 in HTML\|Other ideas...]])<br>Priorities:

← Older revision		Revision as of 22:44, 3 April 2008
Line 4:		Line 4:
	** 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) ✓‬		** Forward compatible (so that future extensions don't introduce name clashes) ✓‬
	** Ability to avoid ID clashes in multiple-document transclusion		** Ability to avoid ID clashes in multiple-document transclusion ✘

	* '''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>Proposal: <code>div</code> and <code>span</code> elements, <code>class</code> and <code>data-<var>foo</var>=""</code> on any element, along with JS, CSS, and, eventually, XBL2 ([[Extensions\|Other ideas...]])<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>Proposal: <code>div</code> and <code>span</code> elements, <code>class</code> and <code>data-<var>foo</var>=""</code> on any element, along with JS, CSS, and, eventually, XBL2 ([[Extensions\|Other ideas...]])<br>Priorities:
Line 10:		Line 10:
	** Without being beholden to an external entity to provide the enhancements for the author on a timescale that is useful to the author ✓‬		** 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.'''<br>Proposal: ~~allow the 34 Presentational MathML 2.0 elements to be used~~ in ~~text/html by hard~~-~~coding those tag names~~ in the ~~parser, with end tags made optional where possible~~ ([[Equations in HTML\|Other ideas...]])<br>Priorities:		* '''Putting an equation in a Web page.'''<br>Proposal: make <math> enter [[New Vocabularies Solution\|a new insertion mode]] in which non-HTML elements end up in the MathML namespace ([[Equations in HTML\|Other ideas...]])<br>Priorities:
	** Maintainability ✓ ''(~~Somewhat:~~ MathML is ~~pretty~~ verbose~~, but omitting end tags helps a lot~~; ~~disallowing Content MathML helps too.~~)''		** Maintainability ✘‬ ''(MathML is too verbose to solve this; making the syntax less verbose makes it even more complicated)''
	** Searchability ✓ ~~''(Somewhat: more complex maths might be better handled if Content MathML was available.)~~		** Searchability ✓
	** Accessibility ✓		** Accessibility ✓
	** Typographically-sound printing ✓		** Typographically-sound printing ✓
	** Ease of authoring (are authors willing to learn new formats?) ✓ ''(Ok for MathML authors; not for LaTeX authors.)''		** Ease of authoring (are authors willing to learn new formats?) ✓✘ ''(Ok for MathML authors; not for LaTeX authors.)''
	** Ease of import from existing documents ✓ ''(Ok for MathML source documents, not for LaTeX source documents.)''		** Ease of import from existing documents ✓✘ ''(Ok for MathML source documents, not for LaTeX source documents.)''
	** Ease of implementation (are UAs willing to implement new formats?) ''(Ok for Mozilla, but not for other vendors.)''		** Ease of implementation (are UAs willing to implement new formats?) ✓✘ ''(Ok for Mozilla, but not for other vendors.)''
	** 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) ✓
	** Numbering the equation ✓ ''(Using, e.g. the <code>title</code> attribute and CSS.)''		** Numbering the equation ✓ ''(Using, e.g. the <code>title</code> attribute and CSS.)''

	* '''Writing a document by hand, with inline diagrams imported from a graphics package.'''<br>Proposal: ~~allow SVG~~ in ~~text/html by hard~~-~~coding a bunch of SVG element tag names and attributes~~ in the ~~parser~~ ([[Diagrams in HTML\|Other ideas...]])<br>Priorities:		* '''Writing a document by hand, with inline diagrams imported from a graphics package.'''<br>Proposal: make <svg> enter [[New Vocabularies Solution\|a new insertion mode]] in which non-HTML elements end up in the SVG namespace ([[Diagrams in HTML\|Other ideas...]])<br>Priorities:
	** Compatibility with existing graphics packages		** Compatibility with existing graphics packages ✓✘ ''(if they support SVG export)''
	** 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) ✓✘ ''(Somewhat, if authors are careful; tool support would make this possible easily.)''
	** 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) ✓
Line 39:		Line 39:
	* '''Animating Web page content (hypertext, vector graphics).'''<br>Proposal: Use the CSS animation proposal ([[Animation in HTML\|Other ideas...]])<br>Priorities:		* '''Animating Web page content (hypertext, vector graphics).'''<br>Proposal: Use the CSS animation proposal ([[Animation in HTML\|Other ideas...]])<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		** Time-based triggering ✓ ''(using script to trigger changes)''
	** Event-based triggering		** Event-based triggering ✓ ''(using script to trigger changes)''
	** 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 spline interpolation		** Linear and spline interpolation ''(up to the CSS animation proposal's definition)''
	** Syndication: animation shouldn't use scripts that can't be trusted by syndicators ✓		** Syndication: animation shouldn't use scripts that can't be trusted by syndicators ✓✘ ''(Somewhat.)''
	** Quality: animation should adapt to the frame rate capabilities of the device, not be forced to use a particular frame rate by a script ✓		** 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.'''<br>Proposal: ? ([[Interactive Sites\|Other ideas...]])<br>Priorities:		* '''Writing highly interactive, graphically intensive sites.'''<br>Proposal: SVG, SVG's SMIL, and scripting ([[Interactive Sites\|Other ideas...]])<br>Priorities:
	** Searchability		** Searchability ✓
	** Accessibility		** Accessibility ✓

	== Rejected requirements ==		== Rejected requirements ==
Line 56:		Line 56:

	* '''Including XBL2 inline in a text/html document the same way CSS and JS can be included inline.'''<br>Proposal: ? ([[XBL2 in HTML\|Other ideas...]])<br>Priorities:		* '''Including XBL2 inline in a text/html document the same way CSS and JS can be included inline.'''<br>Proposal: ? ([[XBL2 in HTML\|Other ideas...]])<br>Priorities:
	** Expressiveness (anything expressed in XBL2 as text/xml should be possible in text/html)		** Expressiveness (anything expressed in XBL2 as text/xml should be possible in text/html) ✘ ''(Could be revisited later.)''

	==Areas for research==		==Areas for research==