trunk/web/index.xml

<?xml version="1.0" encoding="ISO-8859-1" standalone="yes"?>
<page name="index">

<title>Home page</title>
<banner>
  <img title="CDuce" src="img/cduce_logo.jpg" width="400" height="206"
       alt="CDuce"/>
</banner>

<left>
<p>On this page:</p>
<boxes-toc/>
<p>Under this page:</p>
<pages-toc/>
</left>

<external href="/cgi-bin/cduce" title="Online demo" name="proto"/>
<include file="download.xml"/>
<include file="bench.xml"/>
<include file="papers.xml"/>
<include file="documentation.xml"/>
<include file="examples.xml"/>
<include file="hacking.xml"/>
<include file="mailing.xml"/>
<include file="team.xml"/>
<include file="sitemap.xml"/>


<left>

<p> CDuce ("seduce") is a new typed functional language with
innovative features.</p>

<p> Although CDuce is a general programming language, it features
several characteristics that make it adapted to XML documents
manipulation (transformation, extraction of information, creation of
documents).  
<a href="http://www.w3.org/XML/">XML</a> is a syntax to
describe tree-like documents (aka semi-structured data), and XML
documents often come with a description of their type. The type is
expressed in a system like DTD, or 
<a href="http://www.w3.org/XML/Schema">XML Schema</a>.
XML types play a central role in CDuce.
  </p>

</left>

<left>
<p> All pages of this site were automatically generated from an XML description of
the content by <a href="examples.html#site">the following CDuce program</a>.
</p><p> 
<img src="img/cducepower2.jpg" alt="Powered by CDuce"/></p>
</left>

<box title="Latest News" link="news">
<section title="2003, October 26th, Sunday: New addition to papers.">
<p>
If you want a simple and basic introduction to the theoretical foundations
of CDuce, there is a new entry in the <a href="papers.html">papers page</a>.
</p>
<br/>
</section>

<section title="2003, October 17th, Friday: CVS publicly available.">
<p>
You can now download the development version directly from the cvs tree. See instructions at the <a href="download.html">usual place</a>. Be careful, it may not work, and many features are experimental and undocumented.
</p>
<br/>
</section>


<section title="2003, September 23rd, Wednesday: Volunteers sought.">
<p>
We look for volunteers to prepare an emacs mode for CDuce and to implement  a native Win32 or MinGW port. If your are interested please contact 
us.
</p>
<br/>
</section>


<section title="2003, August 16th, Saturday: Version 0.1.1 released.">
<p>
This version has several bug-fixes and encodes reference types. You can now use
<code>:=</code> and <code>;</code>. It is available at the <a href="download.html">usual place</a>. Try this
<a href="http://www.cduce.org/cgi-bin/cduce?example=reference">code</a> on
the on-line demo for an example on how to use them, and refer to the
<a href="manual_expressions.html#ref">manual pages</a> for more
information.
</p>
<br/>
</section>
</box>


<box title="What is CDuce ?" link="whatis">

<p> <b>CDuce</b> is modern programming language, adapted to the
manipulation of XML documents.  It is developed by the <a
href="http://www.di.ens.fr/~castagna/EQUIPE"><b>Languages</b></a>
group of ENS in Paris and the <a
href="http://www.lri.fr/bd"><b>Databases</b></a> group of LRI in
Orsay, two <a href="http://www.cnrs.fr">CNRS</a> labs.
See also the <local href="team">CDuce team</local> page,
our <local href="papers">technical papers</local>.
</p>

<section title="Getting more information">

<p>
If you want more information about CDuce you can send a mail to 
<tt>info_at_cduce.org</tt> (replace <tt>_at_</tt> with <tt>@</tt>), or
to the most appropriate <a href="mailing.html">CDuce mailing list</a>.
</p>

</section>

<section title="Online running prototype">
<p> To get a feeling of CDuce,
you can play with the <local href="proto">on-line prototype</local>,
try the examples and modify them. We also have some 
<local href="examples">larger examples</local>. </p>

<p>We are planning to distribute a stable release in the next
few weeks. To help us prepare this release, you can download a
<local href="download">beta version</local>, and send your comments.
</p>

</section>
</box>

<box title="Design and features" link="design">
<p> Our point of view and our guideline for the design of CDuce is
that a programming language for XML should take XML types (
DTD, XML Schema, Relax-NG, ...) seriously. The benefit are the following:</p>

<ul>
<li> <b>static verifications</b>
(e.g.: ensure that a transformation produces a valid document 
  <footnote>

Valid with respect to validity constraints
that can be expressed by the type system (thus typically excluding 
constraints like <a
href="http://www.w3.org/TR/REC-xml#sec-attribute-types">ID</a> and
<a href="http://www.w3.org/TR/REC-xml#sec-attribute-types">IDREF</a>).

  </footnote>);</li>
<li> in particular, we aim at <b>smooth and safe</b> compositions
of XML transformations, and incremental programming;</li>
<li> static <b>optimizations</b> and <b>efficient execution model</b>
(knowing the type of a document is crucial to extract information 
efficiently).</li> 
</ul>

<p>
Some features particular to CDuce:
</p>
<ul>
<li> XML objects can be manipulated as first-class citizen values:
     elements, sequences, tags, characters and strings, attribute
     sets; sequences of XML elements can be specified by 
     <b>regular expressions</b>, which also apply to
     characters strings; </li>
<li> functions themselves are <b>first-class</b> values, they
     can be manipulated, stored in data structure, returned by
     a function,...</li>
<li> a powerful <b>pattern matching</b> operation can perform
     complex extractions from sequences of XML elements; </li>
<li> a rich <b>type algebra</b>, with recursive types and arbitrary
     boolean combinations (union, intersection, complement) allows
     precise definitions of data structures and XML types;
     <b>general purpose types</b> and types constructors are taken seriously
     (products, extensible records, arbitrary precision integers with interval
     constraints,  Unicode characters);</li>
<li> <b>polymorphism</b> through a natural notion of <b>subtyping</b>,
     and <b>overloaded functions</b> with dynamic dispatch; </li>
<li> an highly-effective <b>type-driven compilation schema</b>. </li>
</ul>

<p>CDuce is fast, functional,
type-safe, and <b>conforms to basic standards</b>: <a href="http://www.unicode.org">Unicode</a>, <a href="http://www.w3.org/XML/">XML</a>, <a href="http://www.w3.org/TR/REC-xml#dt-doctype">DTD</a>,
<a href="http://www.w3.org/TR/REC-xml-names/">Namespaces</a> are fully supported, partial support of <a href="http://www.w3.org/TR/xmlschema-1/">XML Schema</a> validation is
in alpha testing (and undocumented) while queries are being
implemented.
</p>

<p>
<local href="bench">Preliminary benchmarks</local> suggest that despite the
overhead for static type verification, a CDuce
program can run faster (30% to 60%) than an equivalent XSLT
style-sheet (we performed benchmarks with
the xsltproc tools from the Gnome libxslt library).
</p>


</box>

<box title="Research directions" link="research">

<p>Our plans concerning the design of the core language
include:</p>
<ul>
 <li>a module system to support incremental programming;</li>
 <li>parametric polymorphism;</li>
 <li>XML-friendly primitives, to mimic XSLT transformations.</li>
</ul>

<p>
Apart from the core language design and implementation, 
our research projects include:
</p>
<ul>
<li> integration of a <b>query sub-language</b> into CDuce, using
     types as a primary optimization strategy for request evaluation;</li>
<li> study of <b>security</b> (confidentiality, ...) properties in the
     setting of XML transformations.</li>
</ul>

<p>
We wrote several <local href="papers">technical papers</local> about
the language design and its theoretical foundations.
</p>
</box>

<box title="XDuce and CDuce" link="xduce">
<p>

The starting point of our work on CDuce was the
<a href="http://xduce.sourceforge.net/">XDuce</a> language developed
at the UPenn DB group. Many of CDuce features originate from XDuce.
Some of our achievements:

</p>
<ul>
<li>integration of first-class and overloaded functions, arbitrary boolean
    connectives, and extensible (or not) records, to the semantic
    definition of subtyping;</li>
<li>a subtyping algorithm without backtracking;</li>
<li>extending pattern matching to capture non consecutive
    subsequences; removing tail condition for exact matching
    (they arrived independently to another solution);</li>
<li>efficient evaluation model that takes profit of static type information;</li>
</ul>
<p>
Of course, the work on XDuce continued during our, and they
developed nice ideas: mixed attribute-element types (same
expressive power as our records, but they can sometimes avoid exponential
explosion where we cannot); powerful filter operation.
</p>

</box>

<box title="Related links" link="links">
<ul>
<li> <link url="http://www.w3.org/XML/"
title="Extensible Markup Language (XML)"> The W3C page on XML. </link>
</li>
<li> <link url="http://www.research.avayalabs.com/user/wadler/xml/"
title="XML: Some hyperlinks minus the hype"> By Philip Wadler. </link>
</li>
<li> <link url="http://xduce.sourceforge.net/"
title="XDuce"> XDuce home page. </link> </li>
</ul> </box>


<meta>
<p>
<a href="comeon.htm">
<img style="border:0;width:88px;height:31px"
     src="img/cducepower3.png" 
     alt="Powered by CDuce"/>
</a>

<a href="http://validator.w3.org/check?uri=http%3A%2F%2Fwww.cduce.org">
<img style="border:0;width:88px;height:31px"
     src="http://www.w3.org/Icons/valid-xhtml10"
     alt="Valid XHTML 1.0!"/>
</a>

<a href="http://jigsaw.w3.org/css-validator/">
<img style="border:0;width:88px;height:31px"
     src="http://jigsaw.w3.org/css-validator/images/vcss" 
     alt="Valid CSS!"/>
</a>

<a href="http://www.ens.fr">
<img style="border:0"
     src="img//symbENSmio.gif"
     alt="ENS" title="ENS"/>
</a>

<a href="http://www.u-psud.fr">
<img style="border:0" 
     src="img//symbP11mio.gif" 
     alt="Paris 11" title="Paris 11"/>
</a>

<a href="http://www.cnrs.fr">
<img style="border:0" 
     src="img//symbCNRSmio.gif" 
     alt="CNRS" title="CNRS"/>
</a>
</p>
<p>
<a href="mailto:Alain.Frisch@ens.fr">Webmaster</a> -
<local href="sitemap">Site map</local>
</p>
</meta>

</page>
1	<?xml version="1.0" encoding="ISO-8859-1" standalone="yes"?>
2	<page name="index">
3
4	<title>Home page</title>
5	<banner>
6	<img title="CDuce" src="img/cduce_logo.jpg" width="400" height="206"
7	alt="CDuce"/>
8	</banner>
9
10	<left>
11	<p>On this page:</p>
12	<boxes-toc/>
13	<p>Under this page:</p>
14	<pages-toc/>
15	</left>
16
17	<external href="/cgi-bin/cduce" title="Online demo" name="proto"/>
18	<include file="download.xml"/>
19	<include file="bench.xml"/>
20	<include file="papers.xml"/>
21	<include file="documentation.xml"/>
22	<include file="examples.xml"/>
23	<include file="hacking.xml"/>
24	<include file="mailing.xml"/>
25	<include file="team.xml"/>
26	<include file="sitemap.xml"/>
27
28
29	<left>
30
31	<p> CDuce ("seduce") is a new typed functional language with
32	innovative features.</p>
33
34	<p> Although CDuce is a general programming language, it features
35	several characteristics that make it adapted to XML documents
36	manipulation (transformation, extraction of information, creation of
37	documents).
38	<a href="http://www.w3.org/XML/">XML</a> is a syntax to
39	describe tree-like documents (aka semi-structured data), and XML
40	documents often come with a description of their type. The type is
41	expressed in a system like DTD, or
42	<a href="http://www.w3.org/XML/Schema">XML Schema</a>.
43	XML types play a central role in CDuce.
44	</p>
45
46	</left>
47
48	<left>
49	<p> All pages of this site were automatically generated from an XML description of
50	the content by <a href="examples.html#site">the following CDuce program</a>.
51	</p><p>
52	<img src="img/cducepower2.jpg" alt="Powered by CDuce"/></p>
53	</left>
54
55	<box title="Latest News" link="news">
56	<section title="2003, October 26th, Sunday: New addition to papers.">
57	<p>
58	If you want a simple and basic introduction to the theoretical foundations
59	of CDuce, there is a new entry in the <a href="papers.html">papers page</a>.
60	</p>
61	<br/>
62	</section>
63
64	<section title="2003, October 17th, Friday: CVS publicly available.">
65	<p>
66	You can now download the development version directly from the cvs tree. See instructions at the <a href="download.html">usual place</a>. Be careful, it may not work, and many features are experimental and undocumented.
67	</p>
68	<br/>
69	</section>
70
71
72	<section title="2003, September 23rd, Wednesday: Volunteers sought.">
73	<p>
74	We look for volunteers to prepare an emacs mode for CDuce and to implement a native Win32 or MinGW port. If your are interested please contact
75	us.
76	</p>
77	<br/>
78	</section>
79
80
81	<section title="2003, August 16th, Saturday: Version 0.1.1 released.">
82	<p>
83	This version has several bug-fixes and encodes reference types. You can now use
84	<code>:=</code> and <code>;</code>. It is available at the <a href="download.html">usual place</a>. Try this
85	<a href="http://www.cduce.org/cgi-bin/cduce?example=reference">code</a> on
86	the on-line demo for an example on how to use them, and refer to the
87	<a href="manual_expressions.html#ref">manual pages</a> for more
88	information.
89	</p>
90	<br/>
91	</section>
92	</box>
93
94
95	<box title="What is CDuce ?" link="whatis">
96
97	<p> <b>CDuce</b> is modern programming language, adapted to the
98	manipulation of XML documents. It is developed by the <a
99	href="http://www.di.ens.fr/~castagna/EQUIPE"><b>Languages</b></a>
100	group of ENS in Paris and the <a
101	href="http://www.lri.fr/bd"><b>Databases</b></a> group of LRI in
102	Orsay, two <a href="http://www.cnrs.fr">CNRS</a> labs.
103	See also the <local href="team">CDuce team</local> page,
104	our <local href="papers">technical papers</local>.
105	</p>
106
107	<section title="Getting more information">
108
109	<p>
110	If you want more information about CDuce you can send a mail to
111	<tt>info_at_cduce.org</tt> (replace <tt>_at_</tt> with <tt>@</tt>), or
112	to the most appropriate <a href="mailing.html">CDuce mailing list</a>.
113	</p>
114
115	</section>
116
117	<section title="Online running prototype">
118	<p> To get a feeling of CDuce,
119	you can play with the <local href="proto">on-line prototype</local>,
120	try the examples and modify them. We also have some
121	<local href="examples">larger examples</local>. </p>
122
123	<p>We are planning to distribute a stable release in the next
124	few weeks. To help us prepare this release, you can download a
125	<local href="download">beta version</local>, and send your comments.
126	</p>
127
128	</section>
129	</box>
130
131	<box title="Design and features" link="design">
132	<p> Our point of view and our guideline for the design of CDuce is
133	that a programming language for XML should take XML types (
134	DTD, XML Schema, Relax-NG, ...) seriously. The benefit are the following:</p>
135
136	<ul>
137	<li> <b>static verifications</b>
138	(e.g.: ensure that a transformation produces a valid document
139	<footnote>
140
141	Valid with respect to validity constraints
142	that can be expressed by the type system (thus typically excluding
143	constraints like <a
144	href="http://www.w3.org/TR/REC-xml#sec-attribute-types">ID</a> and
145	<a href="http://www.w3.org/TR/REC-xml#sec-attribute-types">IDREF</a>).
146
147	</footnote>);</li>
148	<li> in particular, we aim at <b>smooth and safe</b> compositions
149	of XML transformations, and incremental programming;</li>
150	<li> static <b>optimizations</b> and <b>efficient execution model</b>
151	(knowing the type of a document is crucial to extract information
152	efficiently).</li>
153	</ul>
154
155	<p>
156	Some features particular to CDuce:
157	</p>
158	<ul>
159	<li> XML objects can be manipulated as first-class citizen values:
160	elements, sequences, tags, characters and strings, attribute
161	sets; sequences of XML elements can be specified by
162	<b>regular expressions</b>, which also apply to
163	characters strings; </li>
164	<li> functions themselves are <b>first-class</b> values, they
165	can be manipulated, stored in data structure, returned by
166	a function,...</li>
167	<li> a powerful <b>pattern matching</b> operation can perform
168	complex extractions from sequences of XML elements; </li>
169	<li> a rich <b>type algebra</b>, with recursive types and arbitrary
170	boolean combinations (union, intersection, complement) allows
171	precise definitions of data structures and XML types;
172	<b>general purpose types</b> and types constructors are taken seriously
173	(products, extensible records, arbitrary precision integers with interval
174	constraints, Unicode characters);</li>
175	<li> <b>polymorphism</b> through a natural notion of <b>subtyping</b>,
176	and <b>overloaded functions</b> with dynamic dispatch; </li>
177	<li> an highly-effective <b>type-driven compilation schema</b>. </li>
178	</ul>
179
180	<p>CDuce is fast, functional,
181	type-safe, and <b>conforms to basic standards</b>: <a href="http://www.unicode.org">Unicode</a>, <a href="http://www.w3.org/XML/">XML</a>, <a href="http://www.w3.org/TR/REC-xml#dt-doctype">DTD</a>,
182	<a href="http://www.w3.org/TR/REC-xml-names/">Namespaces</a> are fully supported, partial support of <a href="http://www.w3.org/TR/xmlschema-1/">XML Schema</a> validation is
183	in alpha testing (and undocumented) while queries are being
184	implemented.
185	</p>
186
187	<p>
188	<local href="bench">Preliminary benchmarks</local> suggest that despite the
189	overhead for static type verification, a CDuce
190	program can run faster (30% to 60%) than an equivalent XSLT
191	style-sheet (we performed benchmarks with
192	the xsltproc tools from the Gnome libxslt library).
193	</p>
194
195
196	</box>
197
198	<box title="Research directions" link="research">
199
200	<p>Our plans concerning the design of the core language
201	include:</p>
202	<ul>
203	<li>a module system to support incremental programming;</li>
204	<li>parametric polymorphism;</li>
205	<li>XML-friendly primitives, to mimic XSLT transformations.</li>
206	</ul>
207
208	<p>
209	Apart from the core language design and implementation,
210	our research projects include:
211	</p>
212	<ul>
213	<li> integration of a <b>query sub-language</b> into CDuce, using
214	types as a primary optimization strategy for request evaluation;</li>
215	<li> study of <b>security</b> (confidentiality, ...) properties in the
216	setting of XML transformations.</li>
217	</ul>
218
219	<p>
220	We wrote several <local href="papers">technical papers</local> about
221	the language design and its theoretical foundations.
222	</p>
223	</box>
224
225	<box title="XDuce and CDuce" link="xduce">
226	<p>
227
228	The starting point of our work on CDuce was the
229	<a href="http://xduce.sourceforge.net/">XDuce</a> language developed
230	at the UPenn DB group. Many of CDuce features originate from XDuce.
231	Some of our achievements:
232
233	</p>
234	<ul>
235	<li>integration of first-class and overloaded functions, arbitrary boolean
236	connectives, and extensible (or not) records, to the semantic
237	definition of subtyping;</li>
238	<li>a subtyping algorithm without backtracking;</li>
239	<li>extending pattern matching to capture non consecutive
240	subsequences; removing tail condition for exact matching
241	(they arrived independently to another solution);</li>
242	<li>efficient evaluation model that takes profit of static type information;</li>
243	</ul>
244	<p>
245	Of course, the work on XDuce continued during our, and they
246	developed nice ideas: mixed attribute-element types (same
247	expressive power as our records, but they can sometimes avoid exponential
248	explosion where we cannot); powerful filter operation.
249	</p>
250
251	</box>
252
253	<box title="Related links" link="links">
254	<ul>
255	<li> <link url="http://www.w3.org/XML/"
256	title="Extensible Markup Language (XML)"> The W3C page on XML. </link>
257	</li>
258	<li> <link url="http://www.research.avayalabs.com/user/wadler/xml/"
259	title="XML: Some hyperlinks minus the hype"> By Philip Wadler. </link>
260	</li>
261	<li> <link url="http://xduce.sourceforge.net/"
262	title="XDuce"> XDuce home page. </link> </li>
263	</ul> </box>
264
265
266	<meta>
267	<p>
268	<a href="comeon.htm">
269	<img style="border:0;width:88px;height:31px"
270	src="img/cducepower3.png"
271	alt="Powered by CDuce"/>
272	</a>
273
274	<a href="http://validator.w3.org/check?uri=http%3A%2F%2Fwww.cduce.org">
275	<img style="border:0;width:88px;height:31px"
276	src="http://www.w3.org/Icons/valid-xhtml10"
277	alt="Valid XHTML 1.0!"/>
278	</a>
279
280	<a href="http://jigsaw.w3.org/css-validator/">
281	<img style="border:0;width:88px;height:31px"
282	src="http://jigsaw.w3.org/css-validator/images/vcss"
283	alt="Valid CSS!"/>
284	</a>
285
286	<a href="http://www.ens.fr">
287	<img style="border:0"
288	src="img//symbENSmio.gif"
289	alt="ENS" title="ENS"/>
290	</a>
291
292	<a href="http://www.u-psud.fr">
293	<img style="border:0"
294	src="img//symbP11mio.gif"
295	alt="Paris 11" title="Paris 11"/>
296	</a>
297
298	<a href="http://www.cnrs.fr">
299	<img style="border:0"
300	src="img//symbCNRSmio.gif"
301	alt="CNRS" title="CNRS"/>
302	</a>
303	</p>
304	<p>
305	<a href="mailto:Alain.Frisch@ens.fr">Webmaster</a> -
306	<local href="sitemap">Site map</local>
307	</p>
308	</meta>
309
310	</page>