[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: New dial-in for July 18 PSTC meeting (to discuss RESTPML)
Please note the NEW DIAL-IN for today's meeting: 1-866-682-4770 conference: 1938387 passcode: 123456. On today's agenda is to discuss the RESTPML draft. I haven't seen so far any comments on the alias. That could mean that: - No one has looked at it yet. - What's written there makes perfect sense. - What's written there makes no sense at all. - Everyone is waiting to see the Standard Schema for Person. - Everyone is waiting to see how simple the simplest path will be. The agenda posted currently on Kavi is: 1) Call Roll. 2) Approve minutes from June 6 meeting. 3) Discuss "RESTPML" draft: - Proposed Scope - RESTful API: URIs - RESTful API: XSD 4) Discuss priorities for work yet to do on draft: - Standard Schema for User - Standard Schema for other entities and relationships - Examples of minimal implementation - Examples of supporting User only 5) AOB Gary On Jun 20, 2011, at 10:38 AM, Gary Cole wrote: > Richard is in transit today If members respond and indicate that > they want me to hold a meeting I will do so, but I would prefer that > members used the time to look over on the wiki the draft of the > proposed RESTful binding to SPML: http://wiki.oasis-open.org/provision/restpml > > The wiki page currently: > - Describes the proposed scope of the RESTful binding in terms of > SPML Operations and Capabilities. > - Describes a RESTful API in terms of URIs. In formal terms, this > might be a Resource Summary. > - Describes a RESTful API in terms of XSD. In formal terms, these > are resource representations. > > This proposed scope drawn from the emails that earlier circulated on > the list. The Resource Summary and Resource Representations are new > material and describe abstractly a system I believe is rich enough > to encompass the full scope of SPMLv2--other than those capabilities > explicitly placed out of scope. > > What's missing from the proposal? There are placeholders at the > bottom of the page for sections that: > - Describe the RESTful API in terms of Entitles and Relationships-- > i.e. explains how provider metadata would work. > - Describe the RESTful API in terms of Standard Schema. This should > start with Person (or User), but should also include Org, Role and > Group. > > These final sections remain placeholders for two reasons: > 1) The time I can spend on this task is limited, as each of you will > understand. > 2) The question of standard schema is logically separable, and I'd > like to get some feedback on what I've proposed thus far. > > Please respond to the list with your questions, comments and > concerns related to the RESTPML proposal. Also, please respond to > this email within the next hour or so if you believe that we should > hold a PSTC meeting today. > > Gary > > > > > --------------------------------------------------------------------- > To unsubscribe from this mail list, you must leave the OASIS TC that > generates this mail. Follow this link to all your TCs in OASIS at: > https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]