Skip to content

xAPI Profiles 2.0 / Alignment to xAPI 2.0: Extra Profile Properties#277

Closed
imartinezortiz wants to merge 2 commits intoadlnet:masterfrom
imartinezortiz:extra_props
Closed

xAPI Profiles 2.0 / Alignment to xAPI 2.0: Extra Profile Properties#277
imartinezortiz wants to merge 2 commits intoadlnet:masterfrom
imartinezortiz:extra_props

Conversation

@imartinezortiz
Copy link
Copy Markdown
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
Copy Markdown
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
Copy Markdown
Collaborator

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

@imartinezortiz
Copy link
Copy Markdown
Contributor Author

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