OBO-Edit Working Group, Tuesday March 2nd, 2010 8.30 a.m. PDT
Conference call details: New GOC conference call numbers
US: 1 866 953 9688
UK: 0808 238 6001
Minutes: these notes, such as they are, from Midori
Attendees: Midori, Harold, Laurel, Ramona, Karen C, Becky
Action items carried over
Bug and Feature Tracker Updates
Amina didn't make it -- she was delayed by bridge traffic.
Laurel and Ramona brought up a problem with characters (letters 'b' and 'n') showing up in browsers, but not in OE. We think it's probably newlines ('\n') and something else of that ilk. They'll try running verification checks to see if that's the problem.
No one else had anything to bring up.
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.
- 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