XML Events

In computer science and web development, XML Events is a W3C standard[1] for handling events that occur in an XML document. These events are typically caused by users interacting with the web page using a device, such as a web browser on a personal computer or mobile phone.

Formal definition

An XML Event is the representation of some asynchronous occurrence (such as a mouse button click) that gets associated with a data element in an XML document. XML Events provides a static, syntactic binding to the DOM Events interface, allowing the event to be handled.

Motivation

The XML Events standard is defined to provide XML-based languages with the ability to uniformly integrate event listeners and associated event handlers with Document Object Model (DOM) Level 2 event interfaces. The result is to provide a declarative, interoperable way of associating behaviors with XML-based documents such as XHTML.

Advantages of XML Events

XML Events uses a separation of concerns design pattern, and is technology-neutral with regard to handlers. It gives authors freedom in organizing their code and allows separation of document content from scripting.

Legacy HTML and early SVG versions bind events to presentation elements by encoding the event name in an attribute name, such that the value of the attribute is the action for that event at that element. For example, (with JavaScript’s onclick attribute):

Stay <a href="http://www.example.org" onclick="window.alert('Hello!'); return false;">here</a>!

This design has three drawbacks:

  1. it hard-wires the events into the language, so that adding new event types requires changes to the language
  2. it forces authors to mix the content of the document with the specifications of the scripting and event handling, rather than allowing them to separate them.
  3. it restricts authors to a single scripting language per document.

Relationship to other standards

Unlike DOM Events, which are usually associated with HTML documents, XML events are designed to be independent of specific devices. XML Events are used extensively in XForms and in version 1.2 of the SVG specification, as of July 2006, which is still a working draft.

Example of XML Events using a listener in XForms

The following is an example of how XML events are used in the XForms specification:

<html
   xmlns="http://www.w3.org/1999/xhtml"
   xmlns:ev="http://www.w3.org/2001/xml-events"
   xmlns:xf="http://www.w3.org/2002/xforms">
   <head>
      <ev:listener event="DOMActivate" observer="myButton" 
          handler="#doit"/>
   </head>
   
<xf:trigger xml:id="myButton"><xf:label>Do it!</xf:label></xf:trigger>
<script xml:id="doit" type="application/ecmascript">
alert("test");
</script>
</html>

In this example, when the DOMActivate event occurs on the data element with an id attribute of myButton, the handler doit (for example, a JavaScript element) is executed.

gollark: It does need pretty heavy lua meddling though, for sandboxing and all that.
gollark: Good idea.
gollark: no, contribute to potatOS.
gollark: My thing:- redefines FS functions in new env table- deep-copies a bunch of permitted APIs/libraries into it- redefines getfenv, load in env table- runs init file in new environment via `load`
gollark: And I think it's defaulting to the environment outside the sandbox, somehow.

See also

References
  1. "XML Events: An Events Syntax for XML". World Wide Web Consortium. 2003-10-14. Retrieved 2008-11-19.
This article is issued from Wikipedia. The text is licensed under Creative Commons - Attribution - Sharealike. Additional terms may apply for the media files.