{"action":"closed","issue":{"url":"https://api.github.com/repos/ga4gh/schemas/issues/637","repository_url":"https://api.github.com/repos/ga4gh/schemas","labels_url":"https://api.github.com/repos/ga4gh/schemas/issues/637/labels{/name}","comments_url":"https://api.github.com/repos/ga4gh/schemas/issues/637/comments","events_url":"https://api.github.com/repos/ga4gh/schemas/issues/637/events","html_url":"https://github.com/ga4gh/schemas/issues/637","id":161241848,"number":637,"title":"``message_create_time`` inconsistent and ambiguous in Experiment","user":{"login":"jeromekelleher","id":2664569,"avatar_url":"https://avatars.githubusercontent.com/u/2664569?v=3","gravatar_id":"","url":"https://api.github.com/users/jeromekelleher","html_url":"https://github.com/jeromekelleher","followers_url":"https://api.github.com/users/jeromekelleher/followers","following_url":"https://api.github.com/users/jeromekelleher/following{/other_user}","gists_url":"https://api.github.com/users/jeromekelleher/gists{/gist_id}","starred_url":"https://api.github.com/users/jeromekelleher/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/jeromekelleher/subscriptions","organizations_url":"https://api.github.com/users/jeromekelleher/orgs","repos_url":"https://api.github.com/users/jeromekelleher/repos","events_url":"https://api.github.com/users/jeromekelleher/events{/privacy}","received_events_url":"https://api.github.com/users/jeromekelleher/received_events","type":"User","site_admin":false},"labels":[],"state":"closed","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":2,"created_at":"2016-06-20T16:49:08Z","updated_at":"2016-08-17T18:53:23Z","closed_at":"2016-08-17T18:53:23Z","body":"Creating an issue to avoid side tracking PR636, https://github.com/ga4gh/schemas/pull/636#discussion_r67723063\r\n\r\n> Why message_create_time here? The work message seems ambiguous, i.e., does this refer to the individual message objects as they are being sent to the client, or to the 'record' that is stored on the server? I'm guessing that this is because of a clash with run_time? I would have thought it would be better to just use created and updated just for the sake of being consistent with all the other objects (and change them all in one go to something more specific like creation_timestamp, update_timestamp, if/when this is done)."}}
{"actor":{"display_login":"mbaudis"}}