Adding clarifications to character limits discussed in #4.

FeLungs · Feb 27, 2023 · 239041b · 239041b
1 parent a9b2557
commit 239041b
Show file tree

Hide file tree

Showing 2 changed files with 5 additions and 1 deletion.
diff --git a/xapi-profiles-about.md b/xapi-profiles-about.md
@@ -170,7 +170,9 @@ can be used to inform interpretation of requirements, but are not intended to ta
 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.
+even if there no requirement in a given area. 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 purposes
+like security or data storage.
 
 <a name="definitions"></a>
 ## 3.0 Definitions

diff --git a/xapi-profiles-communication.md b/xapi-profiles-communication.md
@@ -65,6 +65,8 @@ contain all the current versions of Profiles.
 
 A Profile Server will include inference logic for the following, at minimum: all SKOS predicate relationships, and `profile:concepts`, `profile:templates`, and `profile:patterns` being subproperties of the inverse of `skos:inScheme`.
 
+**Note: ** As stated in the section [Part One: About xAPI Profiles, section 2.2](./xapi-profiles-about.md#interpret-text-table) 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 purposes like security or data storage.
+
 <a name="prof-versions"></a>
 ### 1.1 Profile Versions