1 / 11

JOINT ACTION GROUP FOR XML AND WEB SERVICES

JOINT ACTION GROUP FOR XML AND WEB SERVICES. October 15, 2007 Virtual Meeting JAG/XMLWS-2007-02. Opening Remarks. Eric Wise and Bob Bunge (JAG/XMLWS Cochairs). Administrative Remarks. Ken Barnett (JAG/XMLWS ES) JAG/XMLWS Meeting 2007-01

ryu
Download Presentation

JOINT ACTION GROUP FOR XML AND WEB SERVICES

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. JOINT ACTION GROUP FOR XML AND WEB SERVICES October 15, 2007 Virtual Meeting JAG/XMLWS-2007-02

  2. Opening Remarks Eric Wise and Bob Bunge (JAG/XMLWS Cochairs)

  3. Administrative Remarks Ken Barnett (JAG/XMLWS ES) • JAG/XMLWS Meeting 2007-01 • 2007-01.1 Greg and Oliver will complete one use case and distribute to the group as a model for scope and level of detail. To be completed in mid-September. • 2007-01.2 All group members will email their use cases to Ken Barnett and Tim Hopkins by October 1, 2007

  4. Administrative Remarks • Action Items from the Tri-Agency Meeting that Impact this Group. • ACTION #1 - DoD needs to determine how CAP services will be implemented into the existing system. (Leads: Eric Wise and Jennifer Hailes. Contacts: Bob Bunge and Ron Jones.) • ACTION #2 – DoD needs to determine what work needs to be done to convert or translate to UML data model documentation format. (Eric Wise has the lead on this action.) • ACTION #4 – NWS and FAA need to gain access to the DoD JM DSWG web site through soft certificates or CAC access. (Lead: Eric Wise. Contacts: Tim Hopkins and Dave Pace.) • ACTION #5 - DoD needs to determine how to make JMBL and data modeling information content available for public domain access. This may be done through exporting to some outside DoD website, but how to keep the information up to date or in sync will have to be determined. (Leads: Eric Wise and Jennifer Hailes. Contact: Tim Hopkins.) • NOTE: The “new” JAG/XML will review the Collaborations Areas listed by this Tri-Agency group and determine a work plan with resources and time lines. • ACTION #11 – The JAG/XML Work Plan will have to be approved by CEISC and briefed to the Tri-Agency management. (Leads: JAG/XML chairs. Contact point: Ken Barnett.)

  5. Eurocontrol Update Tim Hopkins (NWS)

  6. Use Cases Open group discussion

  7. Next Steps (1) • Next meeting • Virtual meeting with Web Ex or Go To Meeting • Target is October 15, 2007 • Ken to set up a test meeting ahead to identify participation issues • Agenda • Discuss use cases to identify baseline of current and near-term capability • Outline a business case for resources to establish • Standardized, XML-based schema exchange format • Consistent, national net-centric weather services interfaces • Pick a date for follow on face to face meeting • Roadmap Objective • Shape JMBL into JMBL++ to become a national and international standard for machine-to-machine environmental data exchange • Evaluate other technologies for adoption as special purpose services within JMBL++ • Leading candidates include DWML, CAP, ADDS, etc. • E.g., propose CAP to for alert messaging for the meteorological community • The overall approach is driven by use cases

  8. Next Steps (2) • Roadmap • Brief OGC meeting at NCAR (Sep 07) • Use Case Gathering (Oct 07) • Derive use cases from selected existing systems • Augment with near-term use cases • ROM cost to this point is roughly 440 hours (senior analyst/engineer) • Obtain resources to work remainder of roadmap (Oct 07) • ROM cost will depend on outcome of use case analysis • Additional team representation will be needed • Use Case Abstraction (Nov 07) • Identify commonality • Consolidate • Service Design (Feb 08) • Assess how well existing services (JMBL, DWML, CAP, ADDS, …) • Meet needs of use cases • Comply with standards such as • ISO (19xxx), OGC (GML), HDF5, NetCDF • Some of these are data model 'building blocks' and require application profiles • Apply use cases to shape JMBL into JMBL++ to become a national and international standard for environmental data exchange • Seek close EUROCONTROL collaboration on conceptual data model, … • Identify functionality gaps in existing services, missing services • Augment existing services to fill functionality gaps • Work within standards bodies working groups • Create service 'profiles' for weather COI • Propose new services as needed • 'Flight path service', etc. • Welcome use cases from EUROCONTROL for further collaboration

  9. Next Steps (3) • Beyond Feb 08 • Address registry, discovery, metadata, catalog, … • File format issues (netCDF-4/binary xml) • Examine REST as a complement to SOAP • Common business rules for server behavior

  10. Closing Comments and Proposal of the Next Meeting Bob Bunge and Eric Wise

  11. Adjournment Thank You!

More Related