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: Extra Profile Properties #277

Draft
wants to merge 2 commits into
base: master
Choose a base branch
from

Conversation

imartinezortiz
Copy link
Contributor

PR for #273

  • Update section 4.0 to disallow properties not defined in this document (JSON-LD keywords still allowed)
  • Update Profile Server section to include initial requirements related to Profile ingestion and storage

This PR has been migrated from FeLungs#12. See discussion there.

@andyjohnson
Copy link
Collaborator

To make a Comprehensive Guide for Profile Servers, we would have to create another PAR. Any existing language should refer to an existing profiles. Validation should be kept for Conformance Testing (as authorized by PAR) and can be normative. Anything with the Profile Server requirements needs to be informative and can only have SHOULD, SHOULD NOT, or MAY requirements.

@andyjohnson
Copy link
Collaborator

xAPI Profiles SHALL NOT contain extra properties other than those defined in this standard (this standard may allow extensions in a future version).

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

Successfully merging this pull request may close these issues.

2 participants