The CMI5 Spec

The Twitter account for the CMI 5 specification. Hashtag #cmi5spec

[The CMI5 Spec @CMI5Spec]

The web conference connection information for the weekly #cmi5 specification working group meetings have changed.

Please join us Fridays at 10:30am US Eastern time ! (See link)

https://t.co/OvWJZn4tPO

#xapi #lms #lxp

[The CMI5 Spec @CMI5Spec]

At Friday's meeting, we got a "sneak preview" of CATAPULT (the new #cmi5 test suite)!! It will provide automatic cmi5 conformance testing for LMS systems and more. See the official webinar for CATAPULT on Sept 21 !

https://t.co/qA05dMUzX4

#xAPI

[The CMI5 Spec @CMI5Spec]

In friday's meeting, we discussed how collateral credit in a #cmi5 course structure might work

https://t.co/u51qCSTBuw

#xAPI

[The CMI5 Spec @CMI5Spec]

In today's meeting, we added the "key features" section to our "Conceptual Overview of #cmi5" document which is the first of a 3 part series explaining how to implement #cmi5 in Learning Content (AUs) and LMS systems.

https://t.co/1051VXvet3

#xAPI

[The CMI5 Spec @CMI5Spec]

In today's meeting, we discussed the status of the ADL's cmi5# Player and Test Suite (PTS) Prototype Project and reviewed LMS/LRS/AU sequence flows.

https://t.co/abudYwuNJE

#xAPI

[The CMI5 Spec @CMI5Spec]

In today's meeting, we continued our work drafting a conceptual overview of #cmi5 which is the first of a 3 part series of documents explaining how to implement #cmi5 in Learning Content (AUs) and LMS systems.

https://t.co/JOiyVbhe5Y

#xAPI

[The CMI5 Spec @CMI5Spec]

In today's #cmi5 meeting, we discussed the conceptual overview of cmi5 in these terms:

1) xAPI = data model + transfer protocol

2) cmi5 = xAPI + Information Model + Content Package + Launch Mechanism

https://t.co/M5uHaahc5k

#xAPI

[The CMI5 Spec @CMI5Spec]

In Friday's #cmi5 meeting, we created new AU(content) best practices for preventing cmi5 errors when learner refreshes the browser window.

https://t.co/1UdaMucITr

#xAPI

[The CMI5 Spec @CMI5Spec]

In today's meeting, we drafted the XSD for the new "moveOnAllowed" AU (content) attribute to be used in the #cmi5 course structure. This will provide documentation that specifies which "moveOn" values a given AU is capable of supporting.

https://t.co/TDMhEDFpU6
#xAPI

[The CMI5 Spec @CMI5Spec]

In Friday's #cmi5 meeting, we discussed a new best practice (and future spec changes) to address conflicts that could occur when an AU cannot support potential moveOn criteria changes.

https://t.co/fhq7yDhh9t
#xAPI

[The CMI5 Spec @CMI5Spec]

In today's #cmi5 meeting, we reviewed working documents for cmi5 conformance testing and clarified masteryScore usage.

https://t.co/9JWmcABuVg
#xAPI

[The CMI5 Spec @CMI5Spec]

In today's meeting, we began drafting a mid level presentation to help LMS developers understand what is needed to implement #cmi5.

https://t.co/upL9XvkAlk

[The CMI5 Spec @CMI5Spec]

In today's meeting, we continued our review of the draft #cmi5 jsonld for use with the #xAPI profile server. We also discussed updating contextActivities in the next cmi5 spec release to better align with xAPI profile sever validation practices.

https://t.co/Ps9MwJNyoc

[The CMI5 Spec @CMI5Spec]

On friday, the #cmi5 working group continued its review of the draft cmi5 jsonld for use with the #xAPI profile server.
The group discussed the "exactMatch" property usage for the "course" ActivityType.

https://t.co/moZdQZemDy

[The CMI5 Spec @CMI5Spec]

On friday, the #cmi5 working group published a document comparing cmi5 with the most common method of publishing #xAPI/TinCan content currently used by authoring tools.

See https://t.co/PdnrocQMSg

[The CMI5 Spec @CMI5Spec]

At friday's meeting, the group discussed how "attempts" are implemented using "allowed" statements, reviewed #cmi5 topics presented at iFest 2019, and the new BAA issued by the US DoD for funding a #cmi5 TestSuite.

https://t.co/dYlfizzTXg
#xAPI

[The CMI5 Spec @CMI5Spec]

At friday's #cmi5 meeting, the group discussed the differences between tincan.xml and cmi5.xml (packages for LMS import).
One major difference: multiple learning activities can be launched by the LMS with cmi5.xml versus only one with tincan.xml

https://t.co/QzaCLTeNqU
#xAPI

[The CMI5 Spec @CMI5Spec]

#cmi5 working group has changed our gotoWebinar connect info. The group meets every Friday at 10:30am US Eastern Time. If you are interested in xAPI integration with LMS, please consider attending.

(re)register here: https://t.co/0VNQ6E40xG

Note: we are not meeting July 5th

[The CMI5 Spec @CMI5Spec]

At today's #cmi5 meeting, the group reviewed current draft of the TinCan (Packaging/Launch method) vs cmi5 comparison document. The group also discussed adding a "problem statement" to the document

https://t.co/8tgEagMKKV
#xAPI

[The CMI5 Spec @CMI5Spec]

At today's #cmi5 meeting, the group reviewed updates to the cmi5 AU narrative presentation and discussed the phenomenon of "partial xAPI implementations".

https://t.co/031hgFaPU3
#xAPI