{"action":"created","issue":{"url":"https://api.github.com/repos/nasa/utm-apis/issues/90","repository_url":"https://api.github.com/repos/nasa/utm-apis","labels_url":"https://api.github.com/repos/nasa/utm-apis/issues/90/labels{/name}","comments_url":"https://api.github.com/repos/nasa/utm-apis/issues/90/comments","events_url":"https://api.github.com/repos/nasa/utm-apis/issues/90/events","html_url":"https://github.com/nasa/utm-apis/issues/90","id":344119051,"node_id":"MDU6SXNzdWUzNDQxMTkwNTE=","number":90,"title":"Order of OperationVolumes with respect to Start and End Times","user":{"login":"shabemdadi","id":11860013,"node_id":"MDQ6VXNlcjExODYwMDEz","avatar_url":"https://avatars0.githubusercontent.com/u/11860013?v=4","gravatar_id":"","url":"https://api.github.com/users/shabemdadi","html_url":"https://github.com/shabemdadi","followers_url":"https://api.github.com/users/shabemdadi/followers","following_url":"https://api.github.com/users/shabemdadi/following{/other_user}","gists_url":"https://api.github.com/users/shabemdadi/gists{/gist_id}","starred_url":"https://api.github.com/users/shabemdadi/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/shabemdadi/subscriptions","organizations_url":"https://api.github.com/users/shabemdadi/orgs","repos_url":"https://api.github.com/users/shabemdadi/repos","events_url":"https://api.github.com/users/shabemdadi/events{/privacy}","received_events_url":"https://api.github.com/users/shabemdadi/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":12,"created_at":"2018-07-24T16:46:36Z","updated_at":"2018-07-25T18:04:44Z","closed_at":null,"author_association":"NONE","body":"It seems as though the list of operation volumes within the Operation model should be in sequential order (the first volume in the list has the _earliest start time_ of all others in the list), however, I am curious if we can assume that the last volume in the list has the _latest end time_ of all others in the list as well.\r\n\r\nI am thinking of a case where we have:\r\n[0] - 1-8\r\n[1]- 2-6\r\n\r\nWhere the earlier starting volume consumes and extends over the period of the second volume. Could this/should this be possible? \r\n\r\n"},"comment":{"url":"https://api.github.com/repos/nasa/utm-apis/issues/comments/407844327","html_url":"https://github.com/nasa/utm-apis/issues/90#issuecomment-407844327","issue_url":"https://api.github.com/repos/nasa/utm-apis/issues/90","id":407844327,"node_id":"MDEyOklzc3VlQ29tbWVudDQwNzg0NDMyNw==","user":{"login":"esparano","id":3947139,"node_id":"MDQ6VXNlcjM5NDcxMzk=","avatar_url":"https://avatars2.githubusercontent.com/u/3947139?v=4","gravatar_id":"","url":"https://api.github.com/users/esparano","html_url":"https://github.com/esparano","followers_url":"https://api.github.com/users/esparano/followers","following_url":"https://api.github.com/users/esparano/following{/other_user}","gists_url":"https://api.github.com/users/esparano/gists{/gist_id}","starred_url":"https://api.github.com/users/esparano/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/esparano/subscriptions","organizations_url":"https://api.github.com/users/esparano/orgs","repos_url":"https://api.github.com/users/esparano/repos","events_url":"https://api.github.com/users/esparano/events{/privacy}","received_events_url":"https://api.github.com/users/esparano/received_events","type":"User","site_admin":false},"created_at":"2018-07-25T18:04:44Z","updated_at":"2018-07-25T18:04:44Z","author_association":"NONE","body":"Yeah, I agree. I'm cautious about it too. Perhaps it's easier/safer to add more restrictions later."}}
{"actor":{"display_login":"esparano"}}