RE: [office-collab] Location of text:tracked-changes element

["Dennis E. Hamilton" <dennis.hamilton@acm.org>]

There's a scope issue.  Moving where the <text:tracked-changes> element is permitted has scope consequences with regard to where change-marks may appear as descendants and there may also be complications related to how the <text:changed-region> elements are identified and referenced from within the scope of the <text:tracked-changes> material.

There are a number of consequences that must be dealt with before simply changing the schema to locate <text:tracked-changes> higher in the hierarchy of <office:body> element descendants.

 - Dennis

PS: This does not address where generic ct would put its equivalent of <text:tracked-changes>.  This observation applies to the ODF 1.2 schema as it is.  Perhaps, to keep things straight among ourselves, we should refer to <gct:tracked-changes> rather than <text:tracked-changes> until we know what the alignment is (or is not).

DETAILS

 1. Note that, according to ODF 1.2 Part 1 section 5.5.1, and the RNG Schema, <text:tracked-changes> can appear in an <office:text> element or in a <style:header[-left]> or <style:footer[-left]> element.

 2. The appearance of change-marks as descendants of a header-footer-content pattern are, one must presume, in the scope of the <text:tracked-changes> element of the parent <style:header[-left]> or <style:footer[-left]>.    If there is no such <text:tracked-changes> element, the change-marks are to be ignored.

  2.1 Note that those particular <text:tracked-changes> are under a <style:master-page> element that is under an <office:master-styles> element.  

 2.2 The <office:master-styles> element may appear in a <office:document-styles> element (and hence in a styles.xml package part) or in an <office:document> element representing a single ODF (sub-)document.  Because of the use of xml:id and attributes of type IDREF to tie change marks and <text:changed-region> elements together, the resolution of the scope is particularly important, along with the requirement that all xml:id attribute values (and all other attribute values of type ID) in a single XML document be mutually distinct.

 2.3 The appearance of change-marks in a paragraph-content or text-content pattern within the scope of an <office:master-styles> are disjoint from those that are within the scope of an <office:text> element.

 3. An <office:text> element is always the single element child of an <office:body> element.  The optional children of <office:body> are mutually exclusive.

  3.1 When the <office:body> element is a child of an <office:document-content> element, it is near the root of a content.xml file (generally) and the <office:text> has as its scope all children of the <office:text> except for any interior occurrences of an <office:text> element.  There can be multiple <office:text> elements subordinate to an <office:text>, either by in-line occurrence of an <office:document> (e.g., in a <draw:object>) or indirectly via inclusion of a subdocument by reference (in which case the scopes are disjoint).

 3.2 When the <office:body> element is a child of an <office:document>, its <office:text> element, if any, introduces a new scope for a <text:tracked-changes> element.  The rules for omission of a <text:tracked-changes> element suggest that the interior <office:text> cannot have change-mark occurrences that are interpreted in any scope at all.

 3.3 There's a possible edge case where an internal <office:body> element has a child other than <office:text> might have change-marks that are resolved to an outer <office:text> in the same XML document (in a package or not).  I haven't worked through that prospect.




-----Original Message-----
From: monkeyiq [mailto:monkeyiq@gmail.com] 
<http://lists.oasis-open.org/archives/office-collab/201104/msg00051.html>
Sent: Tuesday, April 12, 2011 17:33
To: office-collab@lists.oasis-open.org
Subject: [office-collab] Location of text:tracked-changes element

Hi,
  In the Generic CT, should text:tracked-changes exist as the first child of office:text or as a sibling of office:automatic-styles. ie, in the later perhaps after the automatic styles but before the office:body.

  FWIW the relaxng schema odt-delta.rng 6836 2010-07-30 14:15:03Z nigelw validates the first case location and not as the second.

  As an aside, I started with using the second placement as it seemed the ct element related to content inside the office:body. In KOffice gct it is expected to be inside the office:text (ie, koffice validates placement ok with the rng schema).

  Although I now have abiword able to place in either/both location and read from either I thought it best to clarify where exactly it is desired to have this element appear: inside office:text or at a sibling level with automatic-styles, or somewhere else?



---------------------------------------------------------------------
To unsubscribe from this mail list, you must leave the OASIS TC that generates this mail.  Follow this link to all your TCs in OASIS at:
https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php