Read the SCORM standard, see what it requires, and implement the requirements? I dunno, that would seem like a plan to me...
I did some searches, and couldn't figure out just what the heck that standard does require. It would seem JQM is irrelevant to this.
It appears to be a standard way of marking up online learning modules using XML in a standard way, so that they can be used as interchangeable components that can be read by any compliant "player" application or website.
I'm uncertain, though, as I wasn't able to find the standard itself or any examples, and so I assume it's one of those closely-guarded standards where you have to pay B$G BUCKS to actually read the standard. (Seems like a good way to insure non-compliance...)
So, I'm guessing (and all I can do is guess when you just throw a couple of acronyms at us...) that your app reads these XML files and formats them into HTML. Or needs to.
SCORM packages are .zip files. They normally contain a number of HTML files, media files and configuration files. SCORM-compliant LMS software has a runtime environment for these modules. You upload the SCORM package and the software creates the learning module for you. In its basic form, the learning module is a sequence of HTML files with images, video, etc.
'Moodle' is one of the most widely used LMS packages. It is open-source and written in PHP. There are several generic PhoneGap-based apps that allow you to connect to any Moodle instance, provided you change something in the Moodle configuration. That seems to be the best solution. Writing a SCORM runtime environment for use with JQM is going to be extremely complicated.
I am not sure if the original poster wanted to create a SCORM runtime environment or just a SCORM complient package that can be used on mobile devices. I thought of the latter (which is indeed quite easy).