{"action":"created","issue":{"url":"https://api.github.com/repos/ESIPFed/sweet/issues/33","repository_url":"https://api.github.com/repos/ESIPFed/sweet","labels_url":"https://api.github.com/repos/ESIPFed/sweet/issues/33/labels{/name}","comments_url":"https://api.github.com/repos/ESIPFed/sweet/issues/33/comments","events_url":"https://api.github.com/repos/ESIPFed/sweet/issues/33/events","html_url":"https://github.com/ESIPFed/sweet/issues/33","id":247862893,"number":33,"title":"Earth Science Idol ","user":{"login":"bethhuffer","id":19212312,"avatar_url":"https://avatars1.githubusercontent.com/u/19212312?v=4","gravatar_id":"","url":"https://api.github.com/users/bethhuffer","html_url":"https://github.com/bethhuffer","followers_url":"https://api.github.com/users/bethhuffer/followers","following_url":"https://api.github.com/users/bethhuffer/following{/other_user}","gists_url":"https://api.github.com/users/bethhuffer/gists{/gist_id}","starred_url":"https://api.github.com/users/bethhuffer/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/bethhuffer/subscriptions","organizations_url":"https://api.github.com/users/bethhuffer/orgs","repos_url":"https://api.github.com/users/bethhuffer/repos","events_url":"https://api.github.com/users/bethhuffer/events{/privacy}","received_events_url":"https://api.github.com/users/bethhuffer/received_events","type":"User","site_admin":false},"labels":[{"id":571448469,"url":"https://api.github.com/repos/ESIPFed/sweet/labels/documentation","name":"documentation","color":"e99695","default":false},{"id":557915712,"url":"https://api.github.com/repos/ESIPFed/sweet/labels/enhancement","name":"enhancement","color":"84b6eb","default":true},{"id":571448576,"url":"https://api.github.com/repos/ESIPFed/sweet/labels/governance","name":"governance","color":"fbca04","default":false},{"id":557915713,"url":"https://api.github.com/repos/ESIPFed/sweet/labels/help%20wanted","name":"help wanted","color":"128A0C","default":true}],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":{"url":"https://api.github.com/repos/ESIPFed/sweet/milestones/1","html_url":"https://github.com/ESIPFed/sweet/milestone/1","labels_url":"https://api.github.com/repos/ESIPFed/sweet/milestones/1/labels","id":2378215,"number":1,"title":"2.4","description":"Development drive for SWEEt v2.4","creator":{"login":"lewismc","id":1165719,"avatar_url":"https://avatars1.githubusercontent.com/u/1165719?v=4","gravatar_id":"","url":"https://api.github.com/users/lewismc","html_url":"https://github.com/lewismc","followers_url":"https://api.github.com/users/lewismc/followers","following_url":"https://api.github.com/users/lewismc/following{/other_user}","gists_url":"https://api.github.com/users/lewismc/gists{/gist_id}","starred_url":"https://api.github.com/users/lewismc/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/lewismc/subscriptions","organizations_url":"https://api.github.com/users/lewismc/orgs","repos_url":"https://api.github.com/users/lewismc/repos","events_url":"https://api.github.com/users/lewismc/events{/privacy}","received_events_url":"https://api.github.com/users/lewismc/received_events","type":"User","site_admin":false},"open_issues":17,"closed_issues":16,"state":"open","created_at":"2017-03-10T18:34:04Z","updated_at":"2017-08-29T12:28:23Z","due_on":null,"closed_at":null},"comments":18,"created_at":"2017-08-03T23:25:08Z","updated_at":"2017-08-29T23:13:07Z","closed_at":null,"author_association":"NONE","body":"Question from Mike Huhn re: your pilot project aligning SWEET and ENVO: I see several possibilities and would like to understand which you intend. The possibilities are\r\n\r\n1.      Augment ENVO with terms from SWEET (eventually SWEET might not be needed, because ENVO would be a superset of it)\r\n2.      Augment SWEET with terms from ENVO (eventually ENVO might not be needed)\r\n3.      Augment both SWEET and ENVO with terms from each other (eventually SWEET and ENVO would be identical)\r\n4.      Identify the intersection of SWEET and ENVO, which in some sense would be a core ontology for the environmental domain. It might even be maintained separately, with SWEET and ENVO being unique extensions of it\r\n5.      Create mappings between terms in SWEET and terms in ENVO (this is what Line Pouchard’s student did ~2 years ago), so that the union of SWEET and ENVO could be used, while their separate development could continue.\r\n\r\n So, please clarify your approach and let me know how I can help.\r\n\r\n One more thing, I have a concern about using yamz, because it appears to operate on one pair of terms at a time. As you know, the power of an ontology is not in the terms and their attached English definition, but is in the relationships among the terms. For example, the term “soil” might be a verb or a noun, and this is determined by whether it is a subclass of the term “Process” or a subclass of the term “Physical Object.”"},"comment":{"url":"https://api.github.com/repos/ESIPFed/sweet/issues/comments/325830842","html_url":"https://github.com/ESIPFed/sweet/issues/33#issuecomment-325830842","issue_url":"https://api.github.com/repos/ESIPFed/sweet/issues/33","id":325830842,"user":{"login":"dr-shorthair","id":608303,"avatar_url":"https://avatars0.githubusercontent.com/u/608303?v=4","gravatar_id":"","url":"https://api.github.com/users/dr-shorthair","html_url":"https://github.com/dr-shorthair","followers_url":"https://api.github.com/users/dr-shorthair/followers","following_url":"https://api.github.com/users/dr-shorthair/following{/other_user}","gists_url":"https://api.github.com/users/dr-shorthair/gists{/gist_id}","starred_url":"https://api.github.com/users/dr-shorthair/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/dr-shorthair/subscriptions","organizations_url":"https://api.github.com/users/dr-shorthair/orgs","repos_url":"https://api.github.com/users/dr-shorthair/repos","events_url":"https://api.github.com/users/dr-shorthair/events{/privacy}","received_events_url":"https://api.github.com/users/dr-shorthair/received_events","type":"User","site_admin":false},"created_at":"2017-08-29T23:13:07Z","updated_at":"2017-08-29T23:13:07Z","author_association":"CONTRIBUTOR","body":"Onto the SWEET-ENVO alignment issue - \r\n\r\nI understood that SWEET started with a larger scope than ENVO, but during the development of ENVO, PLB has grown the scope as he realised that this was necessary for a full system description. A key difference between SWEET and ENVO is that ENVO adopted an existing framework (OBO) and its upper ontology (BFO) which come from the life-sciences. I'm not sure if ENVO can be used de-coupled from BFO etc, but it not, then a strong alignment of SWEET to ENVO might come with some costs. \r\n\r\nThere are a few styles in ontology development. The OBO foundry follows the \"one big system integrated through use of a particular upper ontology\". Historically SWEET has offered something similar, but with a different upper layer. More recently the 'Ontology Design Patterns' community has proposed that \"lots of small, tightly-scoped ontologies, each solving one problem, which can be aligned separately if and only when you need to\" might be a more pragmatic approach, and which is also more like what the W3C community has done. It means that your ontological commitment is less, and it is less painful to change your mind and switch later, one piece at a time. "}}
{"actor":{"display_login":"dr-shorthair"}}