Closed jhaag75 closed 6 years ago
Just that one comment from me, otherwise +1 though I would like to check it again once the line breaks have been made to make sure I didn't miss some change.
hmm.. perhaps I'm not explaining it well. Here's what we are doing for xapi profile IRIs:
https://github.com/perma-id/w3id.org/blob/master/xapi/.htaccess
To avoid writing unique rules for every profile you can create regex pattern matching rules.
On Sep 8, 2017 2:33 PM, "fugu13" notifications@github.com wrote:
@fugu13 commented on this pull request.
In xAPI-About.md https://github.com/adlnet/xAPI-Spec/pull/1063#discussion_r137872325:
@@ -643,6 +634,9 @@ and "category" contextActivities. "contextActivities":{ "category":[ {
- "id":"https://w3id.org/xapi/cmi5"
The link you gave is to content negotiation, which is great, but has nothing to do with the form of the IRI, and none of that has anything to do with pattern matching for dereferencing.
I'm not especially worried about being a bad example, but even if it is, it is not avoidable without deciding not to do a Profiles document for the current version of cmi5.
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/adlnet/xAPI-Spec/pull/1063#discussion_r137872325, or mute the thread https://github.com/notifications/unsubscribe-auth/AAiZRjwesSIYXwrak-Eicyrc8lMlQJAQks5sgZZvgaJpZM4O7zXc .
Updates to reflect Profile spec guidelines