Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

xAPI Profiles 2.0 / Alignment to xAPI 2.0: Include xAPI Version in xapi profiles #267

Open
imartinezortiz opened this issue Sep 26, 2024 · 0 comments

Comments

@imartinezortiz
Copy link
Contributor

Change Log Item Ids

s22, s24, s25, x1, x2

1.0.3 text -> 9274.1.1 Update

The LRS SHOULD* return the Timestamp in UTC timezone.
->
An LRS shall convert Timestamps to UTC rather than rejecting Statements that send Timestamps not in UTC form

When comparing Durations, any precision beyond 0.01 second precision SHOULD* NOT be included in the comparison
->
When comparing Durations (or Statements containing them), any precision beyond 0.01 second precision shall not be included in the comparison.

When comparing Durations, any precision beyond 0.01 second precision SHOULD* NOT be included in the comparison
->
When comparing Durations (or Statements containing them), any precision beyond 0.01 second precision shall not be included in the comparison.

The Statement data structure includes a property for the instructor (context.instructor : Agent) in section 2.4.6.
->
The IEEE standard includes a new context array for contextAgents (in section 4.2.2.5 and section 5.2.2.5). This is an array of contextAgent objects including an objectType, agent and relevantTypes (array of “type” IRIs). Although context.instructor from version 1.0.3 is still present, it is considered deprecated. Implementers should make use of a contextAgent with an instructor relevantType IRI for this purpose. The intent of contextAgent is to allow additional actors to be included as context of a statement beyond just the instructor allowed in version 1.0.3

The Statement data structure includes a property for team (context.team : Group) in section 2.4.6.
->
The IEEE standard includes a new context array for contextGroups (in section 4.2.2.5 and section 5.2.2.5). This is an array of contextGroup objects including an objectType, Group, and relevantTypes (array of “type” IRIs). Although context.team from version 1.0.3 is still present, it is considered deprecated. Implementers should make use of a contextGroup with a team relevantType IRI for this purpose. The intent of contextGroups is to allow additional groups to be included as context of a statement beyond just the team allowed in version 1.0.3

Updates to xAPI Profile spec

  • Language / property that indicates what version(s) of xAPI are supported by a Profile

This issue has been migrated from: FeLungs#9

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant