E-mail
Attending: Joel Farrell, Chair; Steve Kenney, Carl Singer, Valerie Smothers.
LEAP2A Status
Valerie provided an update on the LEAP2A status. She communicated with Simon regarding the TSC’s concerns about inconsistencies regarding use of author and contributor elements within lEAP2A . Simon spoke with LEAP2A implementers and made the change to the specification. She also validated a sample educational trajectory and discovered that the way the working group had been representing suprvisor testimonials, using the Atom content element to point to an image file, was no longer considered valid in LEAP2a. LEAP2A requests that all file attachments be referenced using the link element, adding the rel=enclosures attribute.
Joel asked what is normally in the content tag for other educational trajectory content. Valerie replied that normally there is a description of an activity in the content tag. Joel recommended providing a description fo the testimonial in the content tag to remain consistent with the rest of the specification. That would be useful and would promote conformance.
Attachments guidelines
The group walked though the most recent version of the guidelines document. Valerie recorded modifications needed within the text of the document.
Joel agreed to see if there is a best practice for how small a file should be to do base 64 encoding.
Valerie talked through the XML diagram. The Attachment element uses XSD choice, so either an encoded attachment or a reference to an attachment must be included. Joel recommended creating a new mtom example with a profess profile XML snippet. He added that we would have to figure out where to put the xop element. We could add the mtom reference for xop include as an optional element in the new schema.
Carl commented that they normally add Atom links for clients to retrieve documents in a RESTful way.
Joel clarified that you can’t do attachments with REST; that would use the reference approach. Carl commented that we should make a note of that in the guidelines: if you are using a REST-based service, use the reference approach to attachments. It will require the entity retrieving the XML to make another call for each attachment.
Joel noted that he would be unavailable for the September 8 call, and the group decided to cancel. We will work on a new version for Sept 22.
Decisions
The Sep 8 call is cancelled.
Action Items
- Valerie will edit Educational Trajectory specification so that a description of a supervisor testimonial may be included in the content tag.
- Valerie will continue to edit the attachment guidelines
- Joel will see if there is a best practice for Base 64 encoding