This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
syntax [2011/09/27 10:21] Patrick Michel |
syntax [2012/07/25 12:14] (current) Patrick Michel |
||
|---|---|---|---|
| Line 1: | Line 1: | ||
| ====== XCend File Syntax ====== | ====== XCend File Syntax ====== | ||
| + | |||
| + | <fs 150%>The page is incomplete and outdated</fs>. | ||
| A XCend file consists mainly of a ''pattern'', which has to be an ''element'' at the root: | A XCend file consists mainly of a ''pattern'', which has to be an ''element'' at the root: | ||
| Line 9: | Line 11: | ||
| </code> | </code> | ||
| - | In general a pattern is a sequence of ''element'' and ''attribute'' declarations: | + | In general, a pattern is a sequence of ''element'' and ''attribute'' declarations: |
| <code xcend> | <code xcend> | ||
| Line 23: | Line 25: | ||
| </code> | </code> | ||
| - | Elements can be //optional// or //repeated//, attributes can only be optional. For repeated elements, the implicit disambiguation identifier can be renamed and accesses like a normal attribute. | + | Elements can be //optional// or //repeated//, attributes can only be optional. For repeated elements, the implicit disambiguation identifier can be renamed and accessed like a normal attribute. |
| You can also specify choices between elements and attributes, which means that only one has to exist. | You can also specify choices between elements and attributes, which means that only one has to exist. | ||