Adopted Specification: Proposed Charter for {Name} (ACRONYM) FTF “Name” must reflect full specification name and version number (typically, 1.0). “ACRONYM” is an identification used in the Document Directory. TC Meeting Date: {Day Month, Year} Presenter: {Name} Group email: {obtain from Juergen} WIP page (URL): {obtain from Juergen} Adopted Specification: The OMG document number of specification under consideration. Must be in ISO format (see pas/2003-03-01 for template). Members: List name and company of each person. E.g., John Doe, ABC Ltd. Only one person per OMG Member Company Anyone OMG Member in good standing above Trial may be represented. Identify chair. E.g., John Doe (Chair), ABC Ltd. Deadlines: Months should be spelled out (e.g., January, not 1 or 01). Beta Specification Publication: {day month, year} Should be set 30 calendar days after the FTF is chartered. Comments Due: {day month, year} Must be after the Beta Specification Publication date and 10 weeks before the report is due* to allow sufficient time for issue resolution. Report Due Date: {day month, year} This is the 4-week filing deadline; it reflects the 4-week rule for the meeting associated with the deadline below. Report Deadline: {day month, year} This is when the FTF expires, not the 4-week deadline. Must be no more than 14 months after the date of FTF chartering, or alternatively 14 months from the recommendation deadline of a previous FTF for this specification (if there was one).Recommended to be set to one week after the TC Meeting at which the adoption poll is initiated. If there is more than one FTF for this specification, the final FTF must deliver its report no later than 2 years from the chartering of the first one. OMG FTF Charter , Version 1.5, omg/2008-01-02