Date: 3 Jan 2013
Time: 7:00 AM Pacific, 10:00 AM Eastern, 3:00 PM UK, 4:00 PM Frankfurt, 5:00 PM Haifa, 8:30 PM Bangalore
Call In Number: (emailed)
Participation request: contact Jim Conallen
Agenda
- Discuss recent changes to Diagram resource.
- Define and assign use case scenario details.
- Discuss MDD/Transformations topic. Shall we try to include into 3.0 spec?
Active topics
Attendance
Regrets: Steve Speicher, Sandeep Kholi, Eldad Palachi, Eran Gery, Vishy Ramaswamy, Sandeep Katoch
Atendees: Adam Neal, Clyde D. Icuspit, Uri Shani, Jim Conallen
Minutes
Jim updated the Diagram resource discussion documents with examples of using rdf:Seq instead of the current approach of a home grown linked list. Examples were provided for human readability of the RDF (in Turtle) and API examples using the Jena API. Jim’s conclusions were that there was no substantial advantage of either. Both had the same level of readability and complexity of code. Clyde asked what query examples using either would look like. Jim said that he did not provide those, because there was no real usage scenario where querying the points of the polygon made sense. Uri commented that if that was the case, then perhaps the points could be combined into a formatted string, as it is in the HTML <map> element. Jim agreed to update the examples using this approach and then notifying the group for review.
We discussed scenarios where a service provider would provide query services with something other than OSLC Simple Query. The scenario is based on the idea that an AM service provider, managing resource in some domain (e.g. UML) might want to provide query services in a language or format that is native to that domain (e.g. OCL). Clyde was volunteered to update the wiki with a scenario or two (provided he got prompted off line by Jim :).
Long running operations like MDD or code generation is still a useful thing to discuss as a possible inclusion to the next version of the specification. We discussed some basic scenarios, and how a REST client and a web client would be used in such cases. Jim agreed to provide the start of some detailed scenarios which Uri would review and contribute to later.
