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.
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
related excerpts from current state of spec
This issue has been migrated from https://github.com/FeLungs/xapi-profiles/issues/5