OEWG 20100309: Difference between revisions
Jump to navigation
Jump to search
(Created page with 'OBO-Edit Working Group, Tuesday March 9th, 2010 8.30 a.m. PDT <br> Conference call details: New GOC conference call numbers<br> US: 1 866 953 9688 <br> UK: 0808 238 6001<br> pin…') |
|||
Line 18: | Line 18: | ||
==Discussion items== | ==Discussion items== | ||
== Cross product support issues == | |||
There are a bunch of related issues to do with incomplete support for editing intersections. In most cases, I think we just need them to be treated like regular relationships. Perhaps the best thing to do would be to look at how editing works for relationships in various scenarios and check whether intersections are treated the same or not. | |||
Examples: | |||
* [https://sourceforge.net/tracker/?func=detail&atid=418257&aid=2952892&group_id=36855 Loss of intersection status on merge] | |||
* [https://sourceforge.net/tracker/?func=detail&aid=2821389&group_id=36855&atid=418257 indestructible XPs] | |||
** As long as only inferred classification is ignored, this issue can also be solved be treated intersections in the same way as relationships. | |||
* [https://sourceforge.net/tracker/?func=detail&aid=2914257&group_id=36855&atid=418257 Changing relationship type in parent editor blitzes XP stat] | |||
* [https://sourceforge.net/tracker/?func=detail&aid=2914257&group_id=36855&atid=418257 When a term is cloned, intersections become relationships] | |||
==Action Items== | ==Action Items== |
Revision as of 13:54, 2 March 2010
OBO-Edit Working Group, Tuesday March 9th, 2010 8.30 a.m. PDT
Conference call details: New GOC conference call numbers
US: 1 866 953 9688
UK: 0808 238 6001
pin: 801561
Agenda/Chair:
Minutes:
Attendees:
Action items carried over
Bug and Feature Tracker Updates
Discussion items
Cross product support issues
There are a bunch of related issues to do with incomplete support for editing intersections. In most cases, I think we just need them to be treated like regular relationships. Perhaps the best thing to do would be to look at how editing works for relationships in various scenarios and check whether intersections are treated the same or not.
Examples:
- Loss of intersection status on merge
- indestructible XPs
- As long as only inferred classification is ignored, this issue can also be solved be treated intersections in the same way as relationships.
- Changing relationship type in parent editor blitzes XP stat
- When a term is cloned, intersections become relationships