How to read the change drafts for the e-ballot

(Michael: Please look at the first bullet list below and let me know whether I’m right about which issues are “TC design approved”.)

 

As you read the change drafts for the issues on the upcoming e-ballot (the first of two), you might find that they refer to properties or objects that have been renamed, deleted, etc. For example, you might find an example that refers to
instanceGuid or 
files when you know that those properties are now named 
guid and artifacts. That’s because those change drafts were based on earlier versions of the provisional draft.

 

As I prepare for the e-ballot, I am merging all the change drafts into the provisional draft, and fixing all those inconsistencies as I go. So if you see something in the change draft that you think is wrong, please first look at the corresponding
 passage in the provisional draft. If it still looks wrong, make a note of if (and please let me know).

 

There is some risk in my preemptively applying all these changes to the provisional draft; after all, the TC might reject them. But I think at this point we’re in good enough alignment that the risk is small, and IMO is outweighed by the
 benefit of having a single draft where you can see all the changes in one place.

 

For those of you keeping score, I have applied the following changes to the provisional draft since yesterday:

 

Issue #291: Logical locations for XML and JSON documents (e-ballot: review change draft; design change was previously approved)

Issue #309: “file” => “artifact” (this was a
huge change) (e-ballot: review change draft; design change was previously approved)

Issue #321: inlineExternalProperties (e-ballot: review design change
and change draft)

Issue #326: graphs changes from dictionary to array (e-ballot: review design change
and change draft)

Issue #330: Rename notification-related properties on invocation object (no change draft since it’s a simple rename)

Issue #335: Renames of external-property related properties  (e-ballot: review design change
and change draft) (combined change draft with #321)

Issue #340: Inlined logicalLocation property on the location object (NOT on-ballot: we approved the change draft at TC 33)

Issue #341: instanceGuid => guid (e-ballot: review change draft; design change was previously approved)

 

I hope to have these additional changes merged before the first e-ballot goes out tomorrow afternoon:

 

Issue #302: addresses

Issue #320: cached threadFlowLocations

Issue #179: introduce toolComponent (driver and extensions)

Issue #327: remove invocation.attachments

 

Thanks,

Larry