Remove IFI from Section 9.2 Actor

[MartinKoob]

The acronym IFI is used in Section 9.2 Actor

Section 9.2 Actor:

...

The Actor property MUST contain an account property (IFI) as defined in the xAPI specification.

...

However, that acronym is:

• not defined in Section 3.0 Definitions
• nor show in its full form in Section 3.1 Abbreviations and Acronyms.

Options are to add a definition to Section 3.0, just add the acronym and its full name to Section 3.1. or remove the one mention of IFI from Section 9.2 Actor

Background: I was not familiar with the term IFI so I searched for it to find its full name and meaning. There were not many references to it returned in the search and it appears to be a term specific to the xAPI Specification. (Actually when I first read it I thought what it was referring to was reverse Domain Name Notation. See - Reverse Domain Name Notation - Jim Nielsen's Blog https://blog.jim-nielsen.com/2021/reverse-dns/)

IFI is part of the xAPI Specification: xAPI Spec
2.4.2.3 Inverse Functional Identifier
 defines the IFI and lists all the IFI properties.

Other references to Inverse Functional Identifier (IFI)

Appendix A: Converting Statements to 1.0.0

Possible Resolutions

• If we wanted to add a definition to the cmi5 Spec we could use the definition of IFI from the xAPI xAPI Spec 2.4.2.3 Inverse Functional Identifier add a new item to cmi5 Spec Section 3.1 Abbreviations and Acronyms:

• Inverse Functional Identifier (IFI): An Inverse Functional Identifier (IFI) is a value of an Agent or Identified Group that is guaranteed to only ever refer to that Agent or Identified Group. (xAPI Specification - Section 2.3.4.3 Inverse Functional Identifier)[https://github.com/adlnet/xAPI-Spec/blob/master/xAPI-Data.md#2423-inverse-functional-identifier]

• Otherwise we could remove the reference to IFI from Section 9.2 Actor.

[MartinKoob]

After discussion at the meeting of the subgroup of the cmi5 working group the decision was made to remove the reference to IFI in the section.

[MartinKoob]

This was merged into the Main Branch on Aug 4, 2023 so this issue is closed