From ca5466438ea2c8d97272407ffd01318dfca75ef2 Mon Sep 17 00:00:00 2001 From: Will Hoyt Date: Fri, 28 Oct 2022 14:32:07 -0400 Subject: [PATCH 1/2] Delete Issue template remove issue template --- ISSUE_TEMPLATE.md | 9 --------- 1 file changed, 9 deletions(-) delete mode 100644 ISSUE_TEMPLATE.md diff --git a/ISSUE_TEMPLATE.md b/ISSUE_TEMPLATE.md deleted file mode 100644 index 850ca52..0000000 --- a/ISSUE_TEMPLATE.md +++ /dev/null @@ -1,9 +0,0 @@ -Filing an issue about the **xAPI Profiles** specification? Please include the following - -- [ ] Which part/parts of the specification are at issue? - -- [ ] What is your understanding of what the spec means in these parts? - -- [ ] Related to your implementation, what's the use case you're trying to achieve? What are the user stories you're trying to support? - -- [ ] How you would like the specification to be improved? From 239041b9502d4610f80dd1bccf6736e750888fb3 Mon Sep 17 00:00:00 2001 From: Ivan Martinez-Ortiz Date: Mon, 27 Feb 2023 16:35:02 +0100 Subject: [PATCH 2/2] Adding clarifications to character limits discussed in #4. --- xapi-profiles-about.md | 4 +++- xapi-profiles-communication.md | 2 ++ 2 files changed, 5 insertions(+), 1 deletion(-) diff --git a/xapi-profiles-about.md b/xapi-profiles-about.md index fbf3bf2..864b189 100644 --- 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. ## 3.0 Definitions diff --git a/xapi-profiles-communication.md b/xapi-profiles-communication.md index 9d68a63..46372ca 100644 --- 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. + ### 1.1 Profile Versions