[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Operation Definition Template
Allow me to summarize and extend what we have discussed today:|
Each operation is only an abbreviation for a change (or transition) of a document state.
We will define an operation in the ODF 1.3 specification by the change of the ODF XML.
We have four possible types of operations
"Move" & "Replace" are only listed for efficiency reason of
the application and can be substituted by a combination of "add"
and "delete". (Currently I have not ever used "replace" uncertain
if we ever need it).
When defining the add/delete for a component, the definition of
the location by path would be made only once in the spec. The
definition of the add/delete of every component the operation
description would be quite similar.
For an attribute as the @style:name
Adding the element, would describe the attribute for this
The most important part would be the XML change.
The schema is sometimes hard and time consuming to read, a short
ODF reference in HTML would be nice, but unfortunately the one I
know, the one generated by the Apache ODF
Toolkit (incubating) still lacks BNF as choice and sequence.
I have taken the time this evening to fix the generation of the
ODF reference in HTML, but the addition of Backus–Naur Form (BNF)
is hardly to be done aside.