IEPPV — Additional Editorial Changes

. Annex E Scope:
Note: The terms (stereotypes) users in the two models are equivalent and provide for the one to one mapping presented below.
‘Users’ should be ‘used’. Also, I’d use ‘one-to-one’ for readability/
2. Figure E.3 – Information Exchange Specification : Text of the note at the bottom right : “Each of these data-sets can be assembled if and distributed….” Delete ‘if’.
3. Page E8: “By using a FilteredSemanticElement, only one pattern needs to be deployed and specific reporting pattern can be established at runtime.” I would add ‘the’ between ‘and’ and ‘specific reporting pattern’.
4. Page E10: (2nd paragraph)
“The Organization_Item illustrates difference between the SOPES IEDM models and the IEPPV.” – pluralize ‘difference’

“The additions of constraints assisted in the generation” - - singularize ‘additions’

“in the IEPPV can be extended, using standards UML constructs, to address specific domain requirements.” - singularize ‘standards’

5. Figure E.9 – note on left side:
“It The Stereotype (Wrapper)…” – delete ‘It’.
“The Wrapper or WrapperElements makes direct reference…” – singularize ‘makes’
“and connects the assemble rules…” - change to ‘assembly’
Fix “environement”

6. Figure E.9 - Note on right side:
“may mirror the structure of and exchange Schema” – change ‘and’ to ‘an’

Resolution:
Minor editorial changes that were modified and follows:
1. Accepted and changed
2. Accepted and changed
3. Accepted and changed
4. Accepted and changed
5. Accepted and changed
6. Accepted and changed
Revised Text:
As described in the issue summary.

Minor editorial changes that were modified and follows:
1. Accepted and changed
2. Accepted and changed
3. Accepted and changed
4. Accepted and changed
5. Accepted and changed
6. Accepted and changed