Content_Api.js contains a custom implementation of the TinCan.LRS which overrides the default implementation, thus enabling communication between Content and LMS throug postMessage.

Content needs to include TinCan-1.0.1.js, Content_Api-0.2.13.js and add a single line of javascript code: var lrs = new ContentApiLrs(); (see figure below) to make it work.

For a working example see the link below.

• Parent window with Content IFrame using TinCan-1.0.1.js and Content_Api-0.2.13.js to communicate to the parent using postmessage.

Some kind of description of verbs

Some kind of description of the standard verbs

Some kind of description of the custom (bao.mijnklas.nl) verbs

Some kind of description of the 'bao.mijnklas.nl/xapi' extensions

Some kind of description of the standard extensions

Some kind of description of the custom (bao.mijnklas.nl) extensions

Different colors in the JSON Representation give special meaning to that part of the json.

Optional: May be added for clarity. Bao xApi ignores it if present.

Removed: Bao xApi has no use for it but TinCan Api requests/requires it. Bao xApi ignores it if present.

Comment: Comment for clarification of the property. This should not be present in the json representation

{	
	"verb": {
		"id": http://example.com/xapi/verbs/demo",
		"display": {
			"nl-NL": "Demo"
		}
	},
	"object": {
		"id": "http://bao.mijnklas.nl/xapi/demo",
		"objectType": "Activity",
		"definition": {
			"extensions": {
				"benefit": "Joker"
			},
			"correctResponsesPattern": [
				"400"
			]
		}
	}
}