search

adlnet / xAPI-Spec

The xAPI Specification describes communication about learner activity and experiences between technologies.
https://adlnet.gov/projects/xapi/
901 stars 405 forks source link

Deprecation of "endpoint" #973

Closed andyjohnson closed 8 years ago

andyjohnson commented 8 years ago

So for at least one patch version, I do want to leave "endpoint" in the definitions. Are we okay striking it completely otherwise? Or are the sprinkled uses of it helpful reminders?

garemoko commented 8 years ago

xAPI-Communication.md mentions "endpoint" 32 times including an appendix titled "Table of All Endpoints". This is a term we're using alot.

andyjohnson commented 8 years ago

As an alternative, we could leave both in for this patch version and let people get their feet wet calling them Resources/Resource Locations, with a plan to completely remove endpoint for the next version. The biggest issue I see is that we use the same term "endpoint" to talk both about the actual location as well as the functionality provided at that location.

On Tue, Aug 9, 2016 at 5:21 AM, Andrew Downes notifications@github.com wrote:

xAPI-Communication.md mentions "endpoint" 32 times including an appendix titled "Table of All Endpoints". This is a term we're using alot.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/adlnet/xAPI-Spec/issues/973#issuecomment-238499781, or mute the thread https://github.com/notifications/unsubscribe-auth/ABQ36xXDHQ5NvxIclFNAzIwZtdy8ITIrks5qeEawgaJpZM4JfZeV .

Andy Johnson ADL Technical Team 608-318-0049

andyjohnson commented 8 years ago

So I did some more searching on this and I think endpoint can stay, but will be careful to limit its use to where it means an endpoint and not actually the resource itself or actions that occur there.

andyjohnson commented 8 years ago

Given that the description of the issue no longer matches the action, I'm closing the issue to prevent confusion. Check #960 for details.