1 / 6

Project Status

This presentation will probably involve audience discussion, which will create action items. Use PowerPoint to keep track of these action items during your presentation In Slide Show, click on the right mouse button Select “Meeting Minder” Select the “Action Items” tab

weston
Download Presentation

Project Status

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. This presentation will probably involve audience discussion, which will create action items. Use PowerPoint to keep track of these action items during your presentation • In Slide Show, click on the right mouse button • Select “Meeting Minder” • Select the “Action Items” tab • Type in action items as they come up • Click OK to dismiss this box • This will automatically create an Action Item slide at the end of your presentation with your points entered. Project Status NASA’s Use of the DoD XML Registry: A Status Report Bruce Altner Vicky Niblett NASA HQ/SAIC August 18, 2004

  2. Status Summary • Small, simple projects are simple to register in their entirety • Larger, more complex projects present additional challenges • A few issues have been identified with the Registry software (and are being addressed) • NASA remains committed to working with DISA to enhance and use the Registry • Perspective on future upgrades to the Registry

  3. Progress • A few (4) NASA XML projects have been entered into the DoD XML Registry to date, with only minor difficulties • Auto-generation of the package manifest file works (albeit not perfectly) • No special handling of the project artifacts is required • We have completed work on a draft Registry Requirements document • We have many projects waiting to be submitted

  4. Progress (continued…) • XML projects involving multiple complex, interdependent schema do require special handling • There are constructs that are not handled well by the automatic manifest generating mechanism • There are constructs in the project schema that are not supported by the Registry schema • We apply an 80/20 rule, identifying the key concepts in the project and making sure these get entered. • The Registry contractor is committed to fixing present problems as well as those that we encounter in the future

  5. Future Plans for the Registry • Schedule is for two releases per year • Version 4.1 (4Q 2004) • Users will be able to submit/view new requirements for the registry • Adding a new gallery for sharing ontologies written using a DoD-specific version of OWL, for search and discovery.

  6. Future Plans continued … • Version 5.0 (next year) • Will be built as a portal using the BEA Portal server • Will use clusters to increase uptime and reliability • Will be 508 compliant • Will be ebXML RIM compliant • Will use JAXR (Java API for XML Registries) • Improved user security • Will use Network Centric Enterprise Services (NCES) to deploy Web Services extensively • Will have specialized searches and improved recovery, discovery, searching, retrieval etc. • User customization to allow branding

More Related