governance doc and pull request

1 view
Skip to first unread message

Tim Holahan

unread,
Dec 4, 2018, 4:47:51 PM12/4/18
to osdi-go...@googlegroups.com
Hi, folks.

Two items need your attention. Details below on each.
  1. If you haven't already, please choose a section of the governance doc to focus on for review.
  2. Please read up on a pending pull request from Josh.
Thanks,
Tim

Governance doc review

On last week's exec call, we talked about our plan to take a good look at and, if we felt it necessary, tweak or re-work the governance document.

The latest version of the document can be found here in PDF form.

Sonya has created a Slack post breaking out the sections of the doc so that we can each take a section or two, read them carefully (not to preclude reading the whole thing for extra credit), and propose tweaks.

Sonya, Brady, and I have each taken a section. Pamela and Ariel, can you choose yours?

Pull request: clarification on use of $expand URL query parameter

Explanation from Josh:


The use of the $expand URL query parameter (as defined by ODATA), can be used within OSDI’s HAL framework as a loose analogy to JOINs.  If I am querying the collection of new people in the people collection, I can ask the server to return the person’s petition submissions, donations, or event attendances within the same response, by using _embedded.

$expand can also be used specifically ask for fields or inline objects on a collection such as people in a manner similar to the column list on a SELECT statement.  Certain inline objects, like districts/divisions, may be resource intensive for a server to return in all cases, and so it may only be returned with it is explicitly requested with the $expand parameter.

OSDI leverages the ODATA URL query conventions such as filter (to get records newer than xyz date).

----
Tim Holahan
Product Manager, Broadstripes LLC
tim.h...@broadstripes.com
(203) 687-6186
Reply all
Reply to author
Forward
0 new messages