Date
2016-05-16 20.00 UTC
GoToMeeting Details
https://global.gotomeeting.com/join/201313901
I get an error starting the meeting! Will start a join.me session in a sec!
USE THIS INSTEAD:
Previous Meetings
Title | Creator | Modified | |
---|---|---|---|
E2O meeting 20220825 | Daniel Karlsson | 2022-Aug-25 | |
2022-05-23 - OBSERVABLE Meeting | Daniel Karlsson | 2022-May-24 | |
E2O meeting 20220504 | Daniel Karlsson | 2022-May-05 | |
2022-04-25 - OBSERVABLE Meeting | Daniel Karlsson | 2022-Apr-26 | |
2022-04-06 - OBSERVABLE Face-to-face Meeting | Daniel Karlsson | 2022-Apr-25 | |
2022-03-21 - OBSERVABLE Meeting | Daniel Karlsson | 2022-Mar-31 | |
E2O 23rd meeting 20220223 | Daniel Karlsson | 2022-Feb-23 | |
2022-02-21 - OBSERVABLE Meeting | Daniel Karlsson | 2022-Feb-22 | |
E2O 22st meeting 20220202 | Daniel Karlsson | 2022-Feb-02 | |
2022-01-24 - OBSERVABLE Meeting | Daniel Karlsson | 2022-Jan-24 | |
2021-12-20 - OBSERVABLE Meeting | Daniel Karlsson | 2021-Dec-20 | |
2021-11-15 - OBSERVABLE Meeting | Daniel Karlsson | 2021-Dec-16 |
3 Comments
David Sperzel
One of the above items on the agenda is about the different ways that the COMPONENT attribute is role grouped in Procedures and Observables. There was some discussion about the idea of creating two different COMPONENT roles, one for use with Observables and the other for use with Procedures. Although the TOWARD attribute by itself continues to seem rather confusing because it is "overloaded," I wonder what the group would think about addressing this issue by adding three different sub-roles, such as TOWARD COMPONENT, TOWARD DISPOSITION, and TOWARD REALIZATION. TOWARD COMPONENT could be used with Observables, while "plain" COMPONENT could be used with Procedures.
Michael Osborne
I'll just throw this out there... Perhaps since we are trying to describe the "Feature of an entity", we should call the attribute "feature component".
Jim Case
Since the context of use is implied in the hierarchy they are used with, what is the advantage of creating two attributes? Each addition of a new attribute makes consistent modeling more difficult to obtain.