xAPI Profiles 2.0 / Alignment to xAPI 2.0: IRI comparison

[imartinezortiz]

Change Log Item Ids

s16, s17, s18

1.0.3 text -> 9274.1.1 Update

When re-using an existing identifier, Metadata Providers SHOULD* ensure that the exact character equivelent IRI is used.
->
Unclear and unnecessary. Requirement removed.

When storing or comparing IRIs, LRSs SHOULD* handle them only by using one or more of the approaches described in 5.3.1
(Simple String Comparison) and 5.3.2 (Syntax-Based Normalization) of RFC 3987, and SHOULD* NOT handle them using any approaches described in 5.3.3 (Scheme-Based Normalization) or 5.3.4 (Protocol-Based Normalization) of the same RFC, or any other approaches.
->
When storing or comparing IRIs, LRSs shall handle them only by using one or more of the approaches described in 5.3.1 (Simple String Comparison) and 5.3.2 (Syntax-Based Normalization) of RFC 3987.

LRSs SHOULD* apply the same IRI comparison and normalization rules with all IRIs in parameters and fields defined to contain IRIs.
->
removed, handled by change s-16

Updates to xAPI Profile spec

• update to Profile Server section to indicate how IRIs should be stored in triple store and compared
• Profile Server response to new profiles that use IRIs already defined within existing profiles

This issue has been migrated from FeLungs#6