Invalidating statements

The x API specification (1.0.0 at the time of this writing) allows any full URI to be used as a verb.We’ve built the Experience API Registry as a place to store and add verbs, along with a place for your verbs’ URIs to resolve.

The definition for an activity object can be refined over time (though it shouldn’t ever be changed significantly enough to describe what should have been some other new activity).Descriptive fields in the activity definition offer a way for x API to natively support internationalization.A basic verb example: Back to top ▲ Wrapping up the core statement structure, let’s consider the “object” field.Typically the object will be a x API activity, though it might be another actor, and in the case of voiding, another statement.It’s an important principle of x API that no two activities are ever referenced by the same ID.

By definition an ID corresponds one to one with the logical activity it identifies.In the technical introduction to x API, we outlined some basic concepts about statements.Here we’ll take a deeper look into the structure of statements, and discover their utility in capturing experiences.We’ll also talk about representing systems (not people) and groups as actors as well.For now, those details can be found in the Experience API specification.That list includes “experienced”, “attended”, “attempted”, “completed”, “passed”, “failed”, “answered”, “interacted”, “imported”, “created”, “shared”, and “voided”.