Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

xAPI Profiles 2.0 / Alignment to xAPI 2.0: Addressing Character limits #275

Draft
wants to merge 3 commits into
base: master
Choose a base branch
from
Draft

xAPI Profiles 2.0 / Alignment to xAPI 2.0: Addressing Character limits #275

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
ca54664
Delete Issue template
Oct 28, 2022
a9b2557
Merge pull request #1 from FeLungs/remove_issue_template
Oct 28, 2022
239041b
Adding clarifications to character limits discussed in #4.
imartinezortiz Feb 27, 2023
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
9 changes: 0 additions & 9 deletions ISSUE_TEMPLATE.md
View file
Open in desktop

This file was deleted.

4 changes: 3 additions & 1 deletion xapi-profiles-about.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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
Expand Down
2 changes: 2 additions & 0 deletions xapi-profiles-communication.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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

Expand Down