Hi Patrick,
I try to keep my answer as simple as possible: I want the same functionality as bookmarks [since thats what developers
currently abusing. So fieldmarks are bookmarks with some syntactic sugar:
a) Fieldmarks do not only have a name, but instead a name and (propName, propValue) pairs. This allows developers
to get rid of the string encoding they are currently using. E.g. in OOXML you have to use "fieldmark /param1 value1
/param2 value2, etc...".
b) With bookmarks you can [in theory] do things like
...
...
...
...
thats disallowed in fieldmarks since you can only say
...
...
...
...
which would transform into
...
...
...
...
so getting not allowing a name attribute at the field-mark end always causes fieldmarks to be properly nested.
This has nothing to do with XML well-formedness.
c) is an abbreviation for