n140502
nfoWorks
nfoNote
ODF 1.2
Change-Tracking Complexity
Diary & Job Jar
|
|
n140502
nfoWorks
nfoNote |
0.00 2014-07-08 14:27 -0700 |
Status |
Date |
Description |
|
| done | 2014-05-05 |
|
|
| 2014-07-08 | For the analysis, we are going to treat the provisions of ODF 1.2 as correct and that producing tracked-change cases that are not correctly presentable/reversible even by the producer's consumer side as deviations of the implementation. Use cases can cover the desirability of what the implementations attempt, and this is something that RCT will address by providing a way to express it. In some cases, this will lead to better behavior even for RCT-unaware consumers. (See treatment in n140501.) | ||
| 2014-07-04 | An observation about tacit knowledge and the point about interoperable specifications not requiring consultation not requiring consultation of implementations could go here and in all the way down to the conformance requirements discussion. | ||
| 2014-07-04 | At this level, the concern is for what is allowed by the specification and the schema. This includes widows and orphans of many flavors, because they are not addressed in the specification. Although there may well be implementation-specific behavior in what is actually producible by an implementation, a consumer needs to accept such documents, however it interprets them. This analysis does not stipulate the interpretation, just that there will be something. There is also the problem of what an implementation preserves that it "does not interpret." This applies to d140503 and is emerges from n140602 as well. | ||
| 2014-07-04 | There is an opportunity in the data model to distinguish where there are differences among ODF 1.0/1.1/1.2. This is not the critical path, but in some cases analysis appeals to earlier specifications for definitions that have been omitted/abbreviated/deviated in 1.2 relative to an earlier specification. | ||
| 2014-07-04 | The introduction of the data models might belong at d140503. The explanation of data models might need its own place, simply because it can be shared in other cases, beside text documents. The formulation could be at TROSTing or it could be an implementation-pattern case here specifically for ODF 1.0/1.1/1.2. | ||
| 2014-07-04 | The navigation model needs to account for broken links. That is because there are widows and orphans and their handling in practice needs to be pointed out. In particular, there is no referential integrity requirement in ODF 1.2 and implementations must be robust in this context. | ||
| 2014-07-04 | There needs to be a means to crank navigation model diagrams in this analysis. This may be the most-important thing I need to develop next. Most of the situations of change-tracking can be described in terms of navigation data models. | ||
| 2014-07-04 | It is not clear that ironOffice needs to be appealed to at this level. It might be. It might better be in terms of the navigational data model. | ||
| 2014-07-04 | The cases analyzed here may be liinked to from RCT. If the linkage is made bidirectional, it is for concordance purposes and it need not be exclusive. There could be link to other approaches, to implementation details, and also to test cases. | ||
| 2014-07-04 | Emphasize that this is a reference for approaches, such as RCT, but does not resolve it. | ||
| 2014-07-04 | Emphasize that this is about deconstruction of the ODF 1.2 provisions. | ||
| 2014-07-04 | n140502d: Explain the set-offs in bold of JIRA issues. | ||
| 2014-07-04 | n140502d: Correct link in the version progression block to self (not n140502c). | ||
| 2014-07-03 | n140502d: Link to the public comments for JIRA issues when that is their origin(?). | ||
| 2014-07-02 | n140502-cache: Capture/Embargo JIRA issues as backup (?) | ||
| in progress 2014-07-02 |
2014-06-10 | Capture (embargoed if necessary) OASIS materials on ODF change-tracking and ECT proposals - Also any JIRA issues and test documents, defect demonstrations. [dh:2014-07-01 These may be more appropriate here at n140502 on the complexity of change-tracking.] | |
| 2014-06-10 | Recover my spreadsheet attempting to do a transitive closure on the schema elements in which change-tracking is involved. | ||
| 2014-05-06 | I should find the original proposal at OASIS and what it had about change-tracking, and then how the current structure, in essence, was introduced. This will be in the email and document archives of the ODF TC. | ||
| 2014-05-06 | n140503: Once the ODF 1.2 schema is available for linking and the specification for quotation, it is worth looking at the ODF 1.0/1.1 treatment also. [dh:2014-06-10 This might indicate the extent to which RCT could also be applied to ODF 1.0/1.1 documents but it is a very strange case since there are no new producers and the existence of ODF 1.0-only consumers that could avail themselves of this seems particularly murky. On the other hand, the status of ODF 1.2 as an official ISO/IEC International Standard is not yet resolved and an RCT-extension supplement might well be applicable to all of ODF 1.0/1.1/1.2 except for the flip-over on extensions and the MCE prospect.] | ||
| 2014-05-05 | n140502: Go back through from #71.96 as part of capturing notes and considerations for n140502, n140501 (RCT), and n130301 (SCT) | ||
| 2014-05-05 | n140502: This can provide a summary based on all of the places where change-tracked markings can appear and what the change-tracking elements are like. This is how one finds what kinds of things can be caught up in tracking. [dh:2014-07-04 The new synopsis captures the sense of this.] | ||
| 2014-05-05 | Check the "diary" here too. | ||
| 2014-05-05 | See if I can get ODF JIRA materials that I had posted in the past. [These may go better in the n140501 activity] | ||
| 2014-05-05 | Dig through my ODF WHS materials to see what should be captured here or can be used here. | ||
| 2014-05-05 | Start bringing over notes from notebooks, starting backwards from #71. | ||
| done | 2014-07-04 | n140502: Correct broken link to n140502d | |
| done | 2014-07-03 | n140502d: Change to "Background" and allow for information about the original contribution | |
|
done 2014-07-03 |
2014-07-02 | n140502d: Continue classification and preservation of the JIRA issues | |
| done | 2014-07-02 | n140502d: Catalog JIRA issues about change tracking, and possibly about additional features. | |
| done | 2014-07-02 | n140502b: rename to Change-Tracking Analysis, as part of diversification form the folio title. We want to get to the bottom of the complexity. | |
| done | 2014-06-10 | n140502: Add n140602, Conformant ODF 1.2 Documents as additional related material when available. | |
| done | 2014-06-10 | n140502: Refer to n130301 | |
| done | 2014-06-10 | n140502: Add n140503 as related material. | |
| done | 2014-05-05 | Publish material to the hosted site | |
| done | 2014-05-05 | Bring over relevant notes from n000000. | |
|
done |
2014-05-05 | Setup n140502-cache for resource and historical material on this activity | |
| done | 2014-05-05 | Make placeholders for n140502, n140502a, n140502b, and n140502c | |
| done | 2014-05-05 | Add to the catalog | |
| done | 2014-05-05 |
Create this page ready for recording Diary & Job Jar items of this nfoNote. |
|
created 2014-05-05-15:32 -0700 (pdt) by
orcmid |
