1 / 11

UCM meeting notes 4/10/08 Mexico City

UCM meeting notes 4/10/08 Mexico City. Meeting Notes (S. Hinkelman) Agenda Categorize available use cases Review inventory of current contributions (for new and existing members) Review submitted use cases for understanding and questions

emile
Download Presentation

UCM meeting notes 4/10/08 Mexico City

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. UCM meeting notes 4/10/08 Mexico City • Meeting Notes (S. Hinkelman) • Agenda • Categorize available use cases • Review inventory of current contributions (for new and existing members) • Review submitted use cases for understanding and questions • Discussion on extension of use case time submission deadline • Summary / Next steps

  2. In Attendance • David Connelly, OAGi • Nikola Stojknovic, RosettaNet • Ed Buchinski, Transport Canada, TBG14 • Niki Sahling, Paradigma , TBG14 • Scott Hinkelman, Oracle • Gait Boxman, TIE • Martin Forsberg, SFTI • Jim Wilson, CIDX • Ian Watt, AEC, TBG14 • Chuck Allen, HR-XML • Mark Crawford, SAP • Michael Rowell, Oracle

  3. Current Inventory • Review current inventory (for new members and by request) via the Wiki • Completed requirements document • First draft based on 1 (first) submission • 2 current submissions • Tony Coates • SAP (Gunther S.) • Various other work products, mostly all related to the 2 current submissions

  4. Available use case categorization • Mark Crawford delivered a set of use cases he collected – thank you • Note: These notes do not substitute in any way for the actual submitted use cases (go read the use cases) • Team built a spread sheet identifying the currently available use cases • Team decided to give priority to use cases where we know the primary contact • A side discussion took place resulting in agreement that we are not assuming the currently defined context drivers in CCTS 2.X are complete. • Note: use case numbering in current spread sheet may change

  5. Use Case Review Notes…. • OAGI (David C. in discussion) – Context Mechanism Scope • Users are sub-setting/profiling with various tools. • UCM spec should specify the criteria for sub-setting/adding to the approach. • No definitive best practices to tie the rationale of sub-setting to the actual unit of message exchange • The group has a good understanding of this use case • Examples and some more detail is requested

  6. Use Case Review Notes…. • OAGI (David C. in discussion) – Levels of Context are Needed • David will provide more information on the content stack • Need a holistic view of context not just components • Context mechanism needs to take into unit of data exchange and top down. • David will document the steps users take

  7. Use Case Review Notes…. • OAGI (David C. in discussion) – Message Granularity for Business Use • B2MML adopted the OAGI message assembly. Mapping was attempted but not possible due to the underlying data model being very different. • The group concluded that UCM may not be able to solve all data model usage contexts

  8. Use Case Review Notes…. • HR-XML (Chuck A. in discussion) – Official Jurisdiction • Absence/presence of an element • Which code list is appropriate • Groups of entities which always are appropriate together • Official constraints by jurisdiction - matrix across race, geography • Matrix across “trust’ (trusted sources) • end system/application, role • sensitive information (information kind) -in Germany they collect religion info unlike in the US  • Skill taxonomy / applicable constraints within business process step • Chuck will split this use case into two

  9. Use Case Review Notes…. • TBG1/2/6 (Martin F. in discussion) - UMM • This use case seems to indicate that context needs to operate at an instance of a model layer, not a model layer. • Cardinality is within context • Type of an element is within context • The group found this use case very interesting and requested more detail example

  10. Use Case Review Notes…. • TBG14 (Niki S. in discussion) - UMM • Presented an initial picture of UMM structure, ABIE, and where context needs to apply • This will eventually be a use case submission from TBG14 • ABIE (linked to UMM business information) is in context of the UMM transaction • Desire to have the UMM business process be in context of geo, company, industry

  11. Summary / Schedule / Next Steps • Summary • Took inventory of current UCM content (for new users and by request), 6 cases reviewed with active submitter participation • Schedule • Agreed to extend call for use cases until end of May • Next Steps • Identify primary contacts on submissions • Move all work product to the Wiki • Establish use case review as the primary agenda item on the weekly UCM call (Thursday 9:00US Central / 16:00 Central Europe) • Invite submitters as needed [ Several members expressed comment of this being a very productive UCM meeting. Thanks to all involved ! ]

More Related