E-mail
Attending: Joel Farrell, Chair; James Fiore, Dan Rehak, Valerie Smothers
Dan asked if we've seen BEA for adl's new round of funding. There is a section on medical training that includes virtual patients. He offered to forward the link.
Reserved characters in file names - MVP request
Valerie provided some context. Several members of the virtual patient working group have made packages available for testing. Rachel was testing one of the packages and discovered that it included several filenames that used the backslash character. Backslash is an illegal character for filenames in several operating systems, including Windows. Dan asked if it was a filename or file path problem. Valerie offered to ask.
Dan commented that SCORM and IMS CP don't say anything about filename or file path restrictions. They do require special characters to be URL encoded in xml. There are no other restrictions. The Wikipedia filename's article provides a lot of good information on operating system restrictions on filenames. Linux allows any character except slash, whereas Windows has many restrictions. Dan recommended referencing the Wikipedia page and saying to avoid any restricted characters or words is a best practice.
Joel commented that paths were another matter. If you are moving from a Linux system to a Windows system, the slashes in the full path filename would need to be reversed. Dan added that many commercial systems remap filenames and make the changes on the fly. It becomes messy if you parse HTML files that have the filenames embedded; this is even messier if the filenames are embedded in JavaScript.
The group recommended going back to Rachel with the note that references the Wikipedia filename document and recommends that users be aware of restrictions of other operating systems when creating filenames. We can even use the example of the backslash. Dan added that the content package is an exchange mechanism and that filenames may not be acceptable in the target system. It is the responsibility of the reader to translate filenames into something that works locally.
Valerie will draft something and circulate to the TSC before sending to VPWG.
REST Guidelines Document - review updated draft and open questions
Dan made some overall guidelines on the rest document. The introduction needs more information. He suggested changing the title of section 5 to use the word other than resource so it is not confused with the resource of rest. In the beginning of section 7 there is the phrase "navigating to access the resource is the representation of the resource," which is awkward. He recommended correcting the wording. Also in the quote "The common model should be rich enough to support an appropriate representation in JSON and XML structures during the conversion" - what conversion? Expand. He added that people were not likely to understand section 10. He recommended sending a draft to others in the MedBiquitous community to see if the document is at the right level for them and provides the information they need. Valerie asked James if he could offer some perspective. James commented that they are using rest services as a consumer, and that the document made a lot of sense. He particularly appreciated the references to easy to read documents. Joel suggested asking some of the virtual patient working group members from Europe.
Note: Valerie embedded several of the changes the suggestions into the guidelines; therefore, they are not captured in the minutes.
Joel moved on to section 12. The group agreed that the content for this section was good.
Dan brought up two editorial issues -" It adds additive information..." He recommended taking out additive.
Valerie will edit the document for the next call. Joel encouraged Valerie to send any questions to the group.