Change draft for #204: Separate line/column from offset/length text region properties

I pushed a change draft for 
Issue #204, “Clearly separate start/end vs. charOffset/length region property domains.” This greatly simplifies the job of a SARIF consumer that needs to interpret a
region object that specifies only a subset of text-related properties.

 

Documents/ChangeDrafts/Active/sarif-v2.0-issue-204-region-text-property-separation.docx

 

We’ll move approval of this change at the next TC meeting on Wednesday 8/29.

 

Thanks,

Larry