2013/1/9
Attendees: Chris, Andrew, Keith, Jim
Notes:
- Discussed things briefly, discussed unconference, brief call
2012/12/12
Attendees: Chris, Naveed
Notes:
- Call postponed until next time
2012/11/28
Attendees: Chris, Jim, Shilen, Jimmy
Notes:
- Change relative URIs and keep root URI at bottom, must start with slash to be relative, else absolute, append slash to root uri
- Server should use the same path separator that the client sent in, and the server escapes/unescape, see if any path separator would work
- Yes to groups and roles returned in same resource, add default field for roleType: group|role
- Chris will work on PUT/POST folder for next time
- For lists of resources, e.g. /groups, the first 100 records will be returned if no paging is specified: OK
- If pagingEnabled is false, or the limit is too high, the server's max limit will be imposed. Note, this max limit must be at least 1000. OK
- Validation on sorting/paging: you cannot send an offset without a limit. If you send pagingEnabled = false, then you shouldnt send in paging settings OK
- Fields (extra/omit) (see description on standard api wiki) OK
- The folder path separator is specified in the request and response. If the path separator appears in a folder extension or object extension, then URL encode it. Note, if this path is in a URL, then it will be URL encoded again. Needless to say it is ideal if there arent path separators in extensions, or percents in extensions, though if they are, its ok, they can be escaped. In requests, the path separator must be sent in a URL param: pathSeparator. It must be one character. In the response from the server, the separator is specified in the serviceMeta.pathSeparator. This is sent back with all responses. Note, if a client sends in a path separator to the server, the server does not have to use the same path separator in the response. Note URL encoding should be lowercases for a-f. Note, if a different separator is used, then the separator the server uses shouldnt be used in the path or the server will escape it OK
- Groups and roles will be returned by group resources... OK
2012/11/15
Attendees: Chris, Jim, Keith, Ben, Rob
Notes:
- Specify how to encode separators in values
- Add total tests to test harness
- Note that running the test messes up the audits
- Note about paging and next index, how to turn off paging, define but not implement in reference API
- Add next page uri
- Add in paging stuff to resource container
2012/10/31
Attendees: Chris, Jim
Notes:
- Character sets and encodings
- Posting or putting, can use utf-8, in URL need to urlencode
- Characterset for names in REST call
- UTF-8 titles and descriptions
- param ?indent=true will indent the response - DONE
- Does self-URL contain the params on the url? yes (not the credentials, strip out things that dont make sense to the API) - DONE
- Method override changed from HTTP header to method param (consistent with Stormpath): yes - DONE
- TODO XML header with UTF - DONE
- Are we sure we want to start field names with underscore? xstream says invalid xml. Do not have fields that start with underscore DONE
- TODO put the data in container with a unique name that can be looked up (field that wraps data). Note, this can be the same name as the structureName without the container - DONE
- httpstatuscode in requestMeta? yes - DONE
- TODO move status, warning, success to requestMeta - DONE
- TODO meta: separatorChar: - must be one char, could be anything
- TODO ? separatorChar=something note: there might be a request meta section too
- TODO no URL params start with underscore - DONE
- Can we assume single valued HTTP params? yes - DONE
- TODO add in "structureName" in meta which can be googlable like the XML wrapper - DONE
- TODO make HTTP header for content type is there (XML and JSON) - DONE
- TODO groups resource which is a search result. In the group, selfUri in each group (same for folders), paged
- TODO delete the test credential, and create credentials for people
2012/10/17
Attendees: Chris, Jim, Shilen, Ben, Jimmy, Naveed (Rutgers), Omar (Rutgers), Keith
Notes:
- Introduce standard authorization API
- Structure for calls: implement parts each two weeks, discuss what was implemented, what will be implemented, future plans
- Need to collect and satisfy use cases - e.g. COmanage, Shib integration, NET+ services, standard authz libraries
- Will create a reference implementation, client, test harness (iteratively)
- Charset is UTF-8
- Escaping of group names needs to be defined. We can start with URL encoding, until we devise better method. Or we could pass back and forth the separator
- Success flag is ok if in addition to HTTP codes etc
- Discussed the default and version resources for GET
- Format is specified with extension: .json or .xml
- Names should be uri's (folder name and group names etc, e.g. name:a:b, or id:123abc)
- Discuss history of memberships search operation