{"action":"created","issue":{"url":"https://api.github.com/repos/adlnet/xAPI-Spec/issues/556","labels_url":"https://api.github.com/repos/adlnet/xAPI-Spec/issues/556/labels{/name}","comments_url":"https://api.github.com/repos/adlnet/xAPI-Spec/issues/556/comments","events_url":"https://api.github.com/repos/adlnet/xAPI-Spec/issues/556/events","html_url":"https://github.com/adlnet/xAPI-Spec/issues/556","id":52007116,"number":556,"title":"Context and Goals","user":{"login":"rswetnam","id":2905367,"avatar_url":"https://avatars.githubusercontent.com/u/2905367?v=3","gravatar_id":"","url":"https://api.github.com/users/rswetnam","html_url":"https://github.com/rswetnam","followers_url":"https://api.github.com/users/rswetnam/followers","following_url":"https://api.github.com/users/rswetnam/following{/other_user}","gists_url":"https://api.github.com/users/rswetnam/gists{/gist_id}","starred_url":"https://api.github.com/users/rswetnam/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/rswetnam/subscriptions","organizations_url":"https://api.github.com/users/rswetnam/orgs","repos_url":"https://api.github.com/users/rswetnam/repos","events_url":"https://api.github.com/users/rswetnam/events{/privacy}","received_events_url":"https://api.github.com/users/rswetnam/received_events","type":"User","site_admin":false},"labels":[{"url":"https://api.github.com/repos/adlnet/xAPI-Spec/labels/question","name":"question","color":"cc317c"}],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":6,"created_at":"2014-12-15T16:29:39Z","updated_at":"2015-02-05T13:43:36Z","closed_at":null,"body":"In order to promote the wider adoption of the xAPI, I think that it's important that the document set out more clearly, the rationale for the xAPI and situate it's historical context more clearly.  It should answer questions for both technical and non-technical readers such as \"Why should i use it?\"  \"What can it do that SCORM can't\"  I don't think these questions adequately set out in the document.\r\n\r\nMy own experience in reading the xAOI document the first few times was that the \"helpful\"  Reading Guidelines in the description and rationale sections actually impaired my attempts to understand the document.  Rather than just complain about this, I thought I would offer some suggestions on how the document could be improved in that regard through \"pull requests\"  - now that I under stand what they are.  But before doing this, there are a number of questions - some quite mundane and trivial -  that I have that hopefully members of the community can help me with.  \r\n\r\n1. Why does the document not have the version number in the title?  I think it should though this may be some requirement of the specializations world that I am not aware of.  \r\n\r\n2. In 2.0, it says that the \"Experience API is a service that allows for statements of experience to be delivered to and stored securely in a Learning Record Store\".  I don't believe that the xAPI is a service.  I believe it's a framework or a description of a framework.  Am I missing something?  Also, while API is prominent in the title and the discussion, it is never defined in the document.  (I'm assuming that it stands for\" Application Programming Interface\")  Should this not be addressed somewhere in the document?\r\n\r\n3. What is the relationship with SCORM?  Why was it decided to come up with a whole new title and spec rather than updating SCORM to include non LMS applications?  \r\n\r\n4. Why could learning experiences could not be stored in Learning Management Systems based on an updated SCORM specification?  \r\n\r\n5. What are the major benefits of allowing learning experiences to be stored in and queried from Learning Record Stores?\r\n\r\n6. I am assuming that a primary  goal of having the spec and the ADL oversee it is to promote interoperability between applications and Learning Management Stores.  Is that true?  Should that be stated i the spec?  \r\n\r\n7. What are examples of uses that the xAPI will be able to support that have inspired its creation that were not possible before it.  For me the statement \"Authentication services, querying services, visualization services and personal data services\" given in the introduction as additional technologies that the xAPI is designed to support is neither inspiring nor instructive - as I believe that most of these services could be \"supported\" by existing frameworks and specifications.\r\n\r\n8. What is the primary goal of the xAPI?"},"comment":{"url":"https://api.github.com/repos/adlnet/xAPI-Spec/issues/comments/73047554","html_url":"https://github.com/adlnet/xAPI-Spec/issues/556#issuecomment-73047554","issue_url":"https://api.github.com/repos/adlnet/xAPI-Spec/issues/556","id":73047554,"user":{"login":"garemoko","id":1363163,"avatar_url":"https://avatars.githubusercontent.com/u/1363163?v=3","gravatar_id":"","url":"https://api.github.com/users/garemoko","html_url":"https://github.com/garemoko","followers_url":"https://api.github.com/users/garemoko/followers","following_url":"https://api.github.com/users/garemoko/following{/other_user}","gists_url":"https://api.github.com/users/garemoko/gists{/gist_id}","starred_url":"https://api.github.com/users/garemoko/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/garemoko/subscriptions","organizations_url":"https://api.github.com/users/garemoko/orgs","repos_url":"https://api.github.com/users/garemoko/repos","events_url":"https://api.github.com/users/garemoko/events{/privacy}","received_events_url":"https://api.github.com/users/garemoko/received_events","type":"User","site_admin":false},"created_at":"2015-02-05T13:43:36Z","updated_at":"2015-02-05T13:43:36Z","body":"Seems like consensus is that we do need aims, but we don't need to make any changes to the spec. Can this be closed? "}}