CMI 5 Working Group Meeting Minutes – January 27th, 2023

cmi5 Working Group Meeting Minutes – January 27th, 2023

Attendee List

• Bill McDonald (Working Group Leader)
• Andy Johnson (ADL)
• Brian Miller (Rustici Software)
• Thomas Turrell-Croft ()
• Lisa Toquothty ()
• Franklin Ludgood ()
• Vineet Mahesh (InXSOL)
• Henry Ryng (InXSOL)
• Christopher Thompson (National Council For Mental Wellbeing)
• Yifei Dong (Keybridge Technologies)

Notes

The group continued its document style discussions for referencing statement concepts, verbs, and properties.

The following is proposed language to express the document style conventions. (e.g. a "how to read this document")

References to Statements

This document uses, as shorthand, specific vocabulary such as verbs in conjunction with the word "statement" (e.g., a "completed" statement). This shorthand refers to that statement meeting all requirements that would accompany the correct use of that concept. When using this shorthand with the word “the”, this means the cmi5 defined version of that statement with the verb’s display property. (see Section 7.1.3 Types of Statements for the definition of cmi5 defined)

For example:

The “completed” statement

Would be a cmi5 defined xAPI statement with a verb display name of ‘completed’ and a verb IRI of ‘http://adlnet.gov/expapi/verbs/completed’. Similar conventions might be used for other xAPI properties.

This document uses the following style conventions:

• Back Ticks ( ` ) – (possibly rendered as “inline code”) for all literal names of verbs and properties – ‘completed’ verb
• Double Quotes for shorthand – “completed” statement (as described in above)
• Literal syntax case – When referring to verbs and properties the case will show as they appear in xAPI statements
• Section Titles with verbs/properties – may use either Capitalized or Literal

Style Usage examples

• the ‘score’ property
• for ‘score’ when….
• Remove bold/italic styling on verb & properties in text descriptions (use back ticks instead)
• The ‘fetch’ parameter contains a URL value that is used to….
• The “fetch” URL = The shorthand Concept of
• The ‘fetch’ query parameter contains a URL value (the “fetch” URL) that is used by the AU to obtain an authorization token created and managed by the LMS. The authorization token is used by the AU being launched.

Discussion Topics for Next Meeting:

• Object Based Type = AU
• ActivityType Discussion

---

All Previous cmi5 Meeting Minutes

https://github.com/AICC/CMI-5_Spec_Current/wiki

cmi5 on GitHub:

http://aicc.github.io/CMI-5_Spec_Current/