Tutorial: Hamds on ixml

We choose which representations of our data to use, JSON, CSV, XML, or whatever, depending on habit, convenience, or the context we want to use that data in. On the other hand, having an interoperable generic toolchain such as that provided by XML to process data is of immense value. How do we resolve the conflicting requirements of convenience, habit, and context, and still enable a generic toolchain? Invisible XML (ixml) is a method for treating non-XML documents as if they were XML, enabling authors to write documents and data in a format they prefer while providing XML for processes that are more effective with XML content. For example, it can turn CSS code like

	body {color: blue; font-weight: bold}

into XML like

	<css>
	  <rule>
	    <simple-selector name="body"/>
	    <block>
	      <property>
		<name>color</name>
		<value>blue</value>
	      </property>
	      <property>
		<name>font-weight</name>
		<value>bold</value>
	      </property>
	    </block>
	  </rule>
	</css> 
      
or

	<css>
	  <rule>
	    <selector>body</selector>
	    <block>
	      <property name="color" value="blue"/>
	      <property name="font-weight" value="bold"/>
	    </block>
	  </rule>
	</css>
      
depending on choice. More details at invisiblexml.org. This tutorial provides a hands-on introduction to ixml: how to specify how documents are transformed into XML, and what choices you have.