Difference between revisions of "Xml"

From HaskellWiki
Jump to navigation Jump to search
(Added markup, Category:Packages, template Stub, section headings and section "Blog articles" with a link to "Parking in Westminster: An Analysis in Haskell")
(More markup; removed link to blog article; added section heading "Introduction")
 
Line 1: Line 1:
 
{{Stub}}
 
{{Stub}}
  +
  +
== Introduction ==
  +
   
 
== Packages ==
 
== Packages ==
Line 10: Line 13:
   
 
Types:
 
Types:
Content, Element, CData, Attr are all instances of typeclass Node
+
<hask>Content, Element, CData, Attr</hask> are all instances of <hask>typeclass Node</hask>
   
 
A Node instance is anything which has some convention for generating an Element out of it.
 
A Node instance is anything which has some convention for generating an Element out of it.
   
Useful notes: Content has constructors for Elem and Text. CData can be of kind CDataText. The type QName (qualified name) denotes a name with its qualifying namespace attached to it.
+
Useful notes: <hask>Content</hask> has constructors for <hask>Elem</hask> and <hask>Text</hask>. <hask>CData</hask> can be of kind <hask>CDataText</hask>. The type <hask>QName</hask> (qualified name) denotes a name with its qualifying namespace attached to it.
   
   
Line 20: Line 23:
   
 
Read the few [[https://github.com/GaloisInc/xml/tree/master/tests test cases]]
 
Read the few [[https://github.com/GaloisInc/xml/tree/master/tests test cases]]
  +
   
 
Constructing
 
Constructing
Line 30: Line 34:
 
</haskell>
 
</haskell>
   
using node qn _, generally expands to node qn ([attrs], [content]), where it lifts any child data provided into a content list and ensures any attribute provided is lifted into an attribute list. unode just makes a name out of an unqualified name before calling node.
+
using node <hask>qn _</hask>, generally expands to node <hask>qn ([attrs], [content])</hask>, where it lifts any child data provided into a content list and ensures any attribute provided is lifted into an attribute list. <hask>unode</hask> just makes a name out of an unqualified name before calling node.
   
 
<haskell>
 
<haskell>
Line 66: Line 70:
 
== Blog articles ==
 
== Blog articles ==
   
  +
* []
* [http://idontgetoutmuch.wordpress.com/2013/10/23/parking-in-westminster-an-analysis-in-haskell/ Parking in Westminster: An Analysis in Haskell]
 
   
   

Latest revision as of 08:14, 20 February 2014

This article is a stub. You can help by expanding it.

Introduction

Packages

Packages on Hackage in the category XML

xml

Module name: Text.XML.Light

Types: Content, Element, CData, Attr are all instances of typeclass Node

A Node instance is anything which has some convention for generating an Element out of it.

Useful notes: Content has constructors for Elem and Text. CData can be of kind CDataText. The type QName (qualified name) denotes a name with its qualifying namespace attached to it.


Snippets of essentials:

Read the few [test cases]


Constructing

let n = blank_name{qName = "td"}
let n2 = unqual "td"
let d = blank_cdata{cdData = "some data here"}
blank_element {elName = n, elContent = [Text d]}

using node qn _, generally expands to node qn ([attrs], [content]), where it lifts any child data provided into a content list and ensures any attribute provided is lifted into an attribute list. unode just makes a name out of an unqualified name before calling node.

unode "td" () 
unode "td" $ Attr (unqual "width") "10"
unode "td" $ "some data"
unode "tr" [Elem $ unode "td" "some data", Text $ blank_cdata{cdData = "free text"}]


Input

parseXMLDoc "<tr><td>some data here</td></tr>"
parseXML "<car><color>red</color></car><car><color>orange</color></car>"


Output

showContent $ head $ parseXML "<car><color>black</color></car>"
ppContent $ head $ parseXML "<car><color>black</color></car>"


Searching

findChildren blank_name{qName="td"}  $ fromJust $ parseXMLDoc "<tr><td>child1<td>inside</td></td><skip></skip><td>child2</td></tr>"
filterChildren (\e -> (qName $ elName e) == "skip")  $ fromJust $ parseXMLDoc "<tr><td>child1<td>inside</td></td><skip></skip><td>child2</td></tr>"
findAttr (blank_name{qName = "width"}) $ fromJust $ parseXMLDoc "<tr width=10><td>child1<td>inside</td></td><skip></skip><td>child2</td></tr>"


Blog articles

  • []