Figure 9 combines and eliminates the separate Controllable Component, Life Cycle, Property Set, Testable Object, and Component Identifier interfaces that had appeared in earlier versions. Change Figure 9 to separate interfaces as described in 10.5.2.2-10.5.2.5:
10.5.2.2 Add LifeCycle interface containing:
o APP_Initialize()
o APP_ReleaseObject()
10.5.2.3 Add PropertySet interface containing:
o APP_Query()
o APP_Configure()
10.5.2.4 Add TestableObject interface containing:
o APP_RunTest()
10.5.2.5 Add ControllableComponent interface containing:
o APP_Start()
o APP_Stop()
(Figures available.)

This Issue was not resolved in this Task Force and was automatically deferred to the next Task Force

In Table 5: Message and Instance are out of alphabetical order and should be switched. As well as TimeWrap and Timerate.

This Issue was not resolved in this Task Force and was automatically deferred to the next Task Force

Correct SysML in figure 7. Make table 3 more closely align with figure 7 by deleting unneeded items.

Original comments from Daniel Brookshier "Diagrams are slightly odd in places, but not bad (overlapping Interface Blocks) but readable as to intent (style as opposed to an error). I don’t have any other items. Sorry, should have said that the style issue was figure 7 (all the API blocks which could be converted to ports). I also just noticed a display issue with the association APP API and DATA TRANSFER API which looks weird (I think this is a display setting).
Also, since figure 7 has changed, many lines in table 3 no longer apply."

This Issue was not resolved in this Task Force and was automatically deferred to the next Task Force

BufferSize is undefined as type for nb in MessageQueueCreate calling sequence. The variable nb should be an Integer type.

This Issue was not resolved in this Task Force and was automatically deferred to the next Task Force

Missing Clock Control Interface section and methods

Missing Clock Control Interface section and methods

Add new section Clock Control Interface and corresponding methods.

Add suggested values for ellipses in 12.4. Add caveat for Declaration: “(values are examples)”.. and add constants as examples in Tables 8 -13.

Add suggested values for ellipses in 12.4.

Add suggested values for ellipses in 12.4. Add caveat for Declaration: “(values are examples)”.. and add constants as examples in Tables 8 -13.

Fix errors where “Member Details:” should be under Description, not a separate category in the tables.

Merge table fields Member Details into Description

Fix errors where “Member Details:” should be under Description, not a separate category in the tables.

Add inheritance to APP and DEV Declarations in STI-32 and STI-33

Add inheritance to APP and DEV Declarations

Add inheritance to APP and DEV Declarations in STI-32 and STI-33. Change STI-34-STI-40, Table 18 - Table 24.

In STI-20, Table 5, fix errors. Add column for index numbers in the table, labeled “N”. Change from “using the STI API” to “using the STI methods GetSeconds and GetNanoseconds”. Fill in sequential index numbers starting at 1 in column labeled “N”.

STI-20 add index numbers in table

In STI-20, Table 5, fix errors. Add column for index numbers in the table, labeled “N”. Change from “using the STI API” to “using the STI methods GetSeconds and GetNanoseconds”. Fill in sequential index numbers starting at 1 in column labeled “N”.

Remove all comments throughout the document. Comments had been left in the document as guidance to editors that are unnecessary as part of the standard. Remove comments by select Delete All Comments in Document under Delete in the Review ribbon.

*Remove comments *

Remove all comments throughout the document. Comments had been left in the document as guidance to editors that are unnecessary as part of the standard.

The second STI requirement STI-73 in paragraph 12.74 on page should be changed to STI-74. Requirement numbers must be unique.

STI-74: Change STI-73 to STI-74

The second STI requirement STI-73 in paragraph 12.74 should be changed to STI-74. Requirement numbers must be unique.

Add a preamble to STI Application Provided Software, STI Device Provided Software, and STI Infrastructure-Provided Methods sections.

Add extra introductory remarks to 12.5, 12.6, and 12.7

Add a preamble to STI Application Provided Software, STI Device Provided Software, and STI Infrastructure-Provided Methods sections.

Remove "etc." from Tables in Annex A.

Remove “etc.” from Tables

Remove "etc." from Tables 91, 93, and 94 in Annex A

Change local to localTime and LOCAL to LOCAL_TIME

• local is a reserved word in IDL, change local to localTime and LOCAL to LOCAL_TIME.*

Change local to localTime and LOCAL to LOCAL_TIME.

Editorial changes:
1. Template preamble had old URLs with http rather than https and needed to be updated.
2. Fix references, URLs were inconsistently non-linking.
3. Figure numbers changed and text needs to be updated to correspond.
4. Error occurred when tables were renumbered. “Error! Reference source not found “ should have been a reference to the following figure 12.
6. Declaration text is unnecessarily embedded in a blue box in an inconsistent fashion.
7. Change title page
8. Remove extra "-", add "." at the end of the Description lines
9. Switch sections
10. Make tables sequential, renumber
11. Remove field in tables
12. Change space in front of Provided to dash where needed
13. Add a space in title of 12.4.5 and 12.4.6.
14. Change "Component Identifier” to “Instance” in two places. 
15. Change caption in Figures 3, 4, and 5
16. Change "unload…to" "to unload…from" in Table 29

Editorial: correct English usage, fix typos, links, and appearance

Editorial changes:
1. Template preamble had old URLs with http rather than https and needed to be updated.
2. Fix references, URLs were inconsistently non-linking.
3. Fix grammar issues
4. Figure numbers changed and text needs to be updated to correspond.
5. Error occurred when tables were renumbered. “Error! Reference source not found “ should have been a reference to the following figure 12.
6. Declaration text is unnecessarily embedded in a blue box in an inconsistent fashion.
7. Missing "s" in title page
8. Remove extra "-", add "." at the end of the Description lines
9. Switch sections 10.5.3 and 10.5.4
10. Renumber sections in Section 12
11. Make tables sequential
12. Fix references in normative and non-normative sections
13. Renumber tables
14. Change "unload…to" "to unload…from" in Table 29
15. Change space in front of Provided to dash where needed
16. Add a space in title of 12.4.5 and 12.4.6.
17. Change "Component Identifier” to “Instance” in two places. 
18. Change caption in Figures 3, 4, and 5
19. Missing/update information on table 87
20. For consistency change Return field
21. For clarification change section 12.7.46
22. Update Notes field in sections 12.96 and 12.7.49
23. Fix wording in tables in sections 12.5.1 and 12.5.2
24. Missing "alternative" option
25. Change string to Result
26. Add Clock Interface
27. Fix section 12.4.5, 12.9.6, and 12.9.3 to remove "const", "CLK_timeSynch", and "in HandleID to ID"

Change "constants" to "predefined values"

Change “constants” to “predefined values”

Change “constants” to “predefined values”

Add missing argument to calling sequence. The third argument to method AddressWrite was inadvertently omitted in the declaration portion of table 59.

*Calling sequence is inconsistent Key: STI-8 *

Add missing argument to calling sequence. The third argument to method AddressWrite was inadvertently omitted in the declaration portion of table 59.

Reset CalendarValuCivil back to earlier version that included octet. Octet is actually an IDL type and therefore may be used. It is translatable to a byte in Java

*Update calendar format *

Reset CalendarValuCivil back to earlier version that included octet. Octet is actually an IDL type and therefore may be used. It is translatable to a byte in Java. Update Figure 14

BufferSize is undefined type for the variable nb in the calling sequence for MessageQueueCreate. The variable nb should be an Integer.

Change BufferSize to Integer

BufferSize is undefined type for the variable nb in the calling sequence for MessageQueueCreate. The variable nb should be an Integer.

Add and correct information in Appendices pertaining to Perl, Ruby, Java, and Lua language-specific implementation. Additional information is needed for transformation to platform-specific model. For example, in Perl, the namespace is called a package. Need more information to allow additional languages for consistency, clarity, and portability.

Update Perl, Ruby, Java, and Lua Sections

Add and correct information in Appendices pertaining to Perl, Ruby, Java, and Lua language-specific implementation. Additional information is needed for transformation to platform-specific model. For example, in Perl, the namespace is called a package. Need more information to allow additional languages for consistency, clarity, and portability.

In the Notes, in section 12.103, “TIME_INTERVAL_MAX” should be “TIME_INTERVAL_UNLIMITED” to correct the sentence "The constant TIME_INTERVAL_MAX may be specified to indicate no limit to the step size, permitting the target device to be directly set to any value" to "The constant TIME_INTERVAL_UNLIMITED may be specified to indicate no limit to the step size, permitting the target device to be directly set to any value." Only TIME_INTERVAL_UNLIMITED is defined in section 12.29.

*Typo “TIME_INTERVAL_MAX” should be “TIME_INTERVAL_UNLIMITED” *

In the Notes, in section 12.103, “TIME_INTERVAL_MAX” should be “TIME_INTERVAL_UNLIMITED” to correct the sentence "The constant TIME_INTERVAL_MAX may be specified to indicate no limit to the step size, permitting the target device to be directly set to any value" to "The constant TIME_INTERVAL_UNLIMITED may be specified to indicate no limit to the step size, permitting the target device to be directly set to any value." Only TIME_INTERVAL_UNLIMITED is defined in section 12.29.

Need to replace CalendarValueWeekSeconds in union CalendarTime. Global Positioning System time, is the atomic time scale implemented by the atomic clocks in the GPS ground control stations and the GPS satellites themselves. GPS time was zero at 0h 6-Jan-1980 and since it is not perturbed by leap seconds GPS is now ahead of UTC by 18 seconds.

*STI-100: CalendarValueWeekSeconds is undefined *

Need to replace CalendarValueWeekSeconds in union CalendarTime. Global Positioning System time, is the atomic time scale implemented by the atomic clocks in the GPS ground control stations and the GPS satellites themselves. GPS time was zero at 0h 6-Jan-1980 and since it is not perturbed by leap seconds GPS is now ahead of UTC by 18 seconds.

Many systems need to distinguish between text and binary file types on file open. There was such a parameter in the calling sequence in an earlier version but it was removed for unknown reasons.

*Add file type parameter to the FileOpen method. *

Many systems need to distinguish between text and binary file types on file open. There was such a parameter in the calling sequence in an earlier version but it was removed for unknown reasons.

Parameters are shown in the calling sequence for Table 16, 17, and 22 but are not described.

*There are items in the calling sequence but the parameters are not described   *

Parameters are shown in the calling sequence for Table 16, 17, and 22 but are not described.

Change STI method GetCalendarTime to POSIX method strftime and remove localtime() in Table 4.

*STI Proposal: Change GetCalendarTime to strftime in Table 4 *

Change STI method GetCalendarTime to POSIX method strftime and remove localtime() in Table 4.

Inconsistency in signature between Log and Write/APP_Write. Calling sequence of Log doesn't match Write.

*Inconsistency in signature between Log and Write/APP_Write. *

Inconsistency in signature between Log and Write/APP_Write. Calling sequence of Log doesn’t match Write.

Remove “Provided By” line. Remove “Implemented By” line. Remove “Invoked By” line.

Remove Unnecessary Table Fields

Remove “Provided By” line. Remove “Implemented By” line. Remove “Invoked By” line.

Clarify definition vs implementation

*Clarify definition vs implementation *

Clarify definition vs implementation

Repeat 3 column headers for Table 5 at top of each continuation page:
Type Name
Semantics
Usage/Description

Repeat column header at top of each page

Repeat 3 column headers for Table 5 at top of each continuation page:
Type Name
Semantics
Usage/Description

Update figures for correct SysML. Change Figure 1, 7, 9, 16. Make table 3 more closely align with figure 7 by deleting unneeded items.

Correct SysML in figures

Update figures for correct SysML. Change Figure 1, 7, 9, 16. Make table 3 more closely align with figure 7 by deleting unneeded items.