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: Defining an IRI #271

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

xAPI Profiles 2.0 / Alignment to xAPI 2.0: Defining an IRI #271

imartinezortiz opened this issue Sep 26, 2024 · 0 comments

Comments

@imartinezortiz
Copy link
Contributor

Change Log Item Ids

s15

1.0.3 text -> 9274.1.1 Update

Metadata Providers defining new IRIs SHOULD* only use IRIs they control or have permission from the controller to use.
->
Learning Record Providers defining new IRIs should only use IRIs they control or have permission from the controller to use.

Updates to xAPI Profile spec

  • ensure there's an IRI section that explicitly states what is means to define an IRI within an xAPI Profile

related excerpts from current state of spec

A Profile MUST NOT define a Concept that is defined in another Profile unless it supersedes all versions of the other Profile containing the Concept and indicates that in with wasRevisionOf.

A Profile Author MUST change a Statement Template's id between versions if any of the Determining Properties, StatementRef properties, or rules change. Changes of scopeNote are not considered changes in rules.

A Profile Author MUST change a Pattern's id between versions if any of alternates, optional, oneOrMore, sequence, or zeroOrMore change. Note that if a Pattern used within another Pattern changes, the change will "bubble up" as each id gets changed.

This issue has been migrated from FeLungs#5

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