-
Key: IEFRA_-42
-
Status: closed
-
Source: Technical Director Emeritus ( Andrew Watson)
-
Summary:
As a specification, this document should be definitional ("XYZ is ...") not aspirational ("XYZ will be ..."). Pretend you're reading the specification 5 years in the future, when all the component specifications that make up IEF have been written. Sentences cst in the future tense like "The IEF will provide the ability and capacity for people, processes, and systems to work together efficiently ..." will not then make sense.
There are 78 sentences containing the word "will" in the specification, and I'll wager that at least 70 of them should be recast as definitions ("IEF specifies X") instead of aspirations ("IEF will do X when it's finished"). There are also two sentences containing the word "seeks" that should be considered for rephrasing.
(This issue was rainsed at the specification's pre-adoption AB review).
-
Reported: IEF-RA 1.0b1 — Thu, 27 Jul 2017 15:22 GMT
-
Disposition: Deferred — IEF-RA 1.0
-
Disposition Summary:
Correction to IEFRA-42
Deferred to RTF - the documents have been submitted - and a stable version is required for NAT0 evaluation and Testing in June
Requires minor correction for typographical errors
-
Updated: Tue, 8 Oct 2019 17:56 GMT
IEFRA_ — Use definitional language
- Key: IEFRA_-42
- OMG Task Force: IEF Reference Architecture 1.0 FTF 2