SBVR12 — New SBVR issue - Re-sequencing Clause 8

All, The re-sequencing of Clause 11 has initially proven quite worthwhile, so I have been encouraged to do similar work on Clause 8. As before, I made no changes to the entries themselves whatsoever. (If I did, it was purely an error and should be corrected. Also, my work should be double-checked for any entries inadvertently omitted.) I used a Word version kindly supplied by Linda Heaton, which I believe is from the latest convenience document. (It does have some styling problems, which I have noted.) I hope we can move forward with this revision expeditiously. By the way, I found this re-sequencing much harder than Clause 11, which I am much more familiar with.

Ron

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

Problem Statement: SBVR adheres to ISO 1087 as much as possible. Clearly evident in the structure of ISO 1087 is that no definition should appear until all terms within it have been defined (as needed). This best practice (rule) results in a logical, easy-to-follow presentation. Clause 8 of SBVR is clearly broken in this regard. The result is significant lack of clarity, making detection of errors unnecessarily difficult. The possibility of misinterpretation (or non-comprehension) by software engineers and other readers is high.

Resolution: Apply the ISO 1087 rule about sequencing vocabulary entries rigorously. This re-sequencing requires no changes in the entries themselves (but does suggest some). Two files containing all Clause 11 entries are attached. One file is unchanged except that entries are numbered. The other file is re-sequenced. The entry numbers reappear in the re-sequenced file indicating the original location of each entry. New subheadings are suggested.

Merger with Issue 18377