Document FAPI specification status

[fergus-dall]

Currently the implementation of the FAPI here deviates from the latest published specification in at least a few different ways. For example, the callbacks take an additional parameter for the path of the object they operate on, object types appear to allow a broader range of attributes to be set, and several validity requirements on entity paths don't seem to be checked (and don't obviously need to exist in the first place).

What is the status of this document, and the FAPI more broadly, supposed to be? The current version number is 0.94 r9, which leads me to think it's effectively an outdated draft, but I wasn't able to find anything else indicating that.

[williamcroberts]

@AndreasFuchsTPM can you elaborate here?

[AndreasFuchsTPM]

We need to update the spec. No idea why we did not, it was discussed in TCG though.

A bit of background: We first released the spec, then did the reference implementation, then we found issues and updated the FAPI with the 3.0 release and wanted to play this back into the spec. The last step seems to have been dropped (by me) somehow. I'll make sure to get the "update FAPI spec" on the agenda and my work schedule for the next weeks again.

@fergus-dall and all: If you have any more inputs about misalignments, let me know.