Character Limits

[FeLungs]

Change Log Item Ids

s9, s10

1.0.3 text -> 9274.1.1 Update

The LRS SHOULD* NOT enforce character limits relating to response patterns.
->
Removed as a requirement

The LRS SHOULD* NOT limit the length of the correctResponsesPattern array for any interactionType
->
Removed as a requirement

Updates to xAPI Profile spec

• ensure xAPI profile data doesn't impose character limits
• add language to profile server section indicating implementations can impose character restrictions
  • should mirror similar language within xAPI base spec / standard

[FeLungs]

Where the specification does not include requirements relating to a particular facet of implementation, that detail can be considered to be outside of the scope of this specification. It is up to the implementer to determine a sensible approach. This specification tries to avoid vagueness and will usually give a rationale even if there no requirement in a given area.

^^^ from end of section 2.2 within Part 1

Given that clauses, should we mention character limits at all?

• Could serve as a good example of what this clause means in practice
• "For example, this specification does not place any limits on character limits on xAPI Profile fields but a Profile Server implementation MAY choose to include character limits for domain specific purposes like security or data storage"

[imartinezortiz]

Maybe copy the very same clause. Besides, domain specific can be confused with the specific domain of an application profile.

[FeLungs]

Add reminder to Profile Server part that re-iterates "...specification does not include requirements relating to a particular facet of implementation..."

Reader may want to just go to section 3 and not have to read section 1 to know ^^^

[imartinezortiz]

This issue has been migrated to upstream repo adlnet#272

[imartinezortiz]

This issue has been migrated to upstream repo adlnet#271