Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Difference between revisions of "COSMOS Design 198553"
(→Design Considerations) |
|||
| Line 16: | Line 16: | ||
* What additional dependencies are we bringing in? | * What additional dependencies are we bringing in? | ||
** 3rd party code, e.g. xerces, xpath.. | ** 3rd party code, e.g. xerces, xpath.. | ||
| + | *** Currently looking at Qexo as the XQuery engine for this effort. | ||
| + | **** Qexo is available as part of the KAWA framework. It is freely available under the X11/MIT License. We will need to investigate this license to see if it will work for this effort. | ||
| + | **** The web site for Qexo is http://www.gnu.org/software/qexo/ | ||
| + | **** I have given this information to Mark Weitzel for submission and approval. | ||
** JVM et.. | ** JVM et.. | ||
| Line 23: | Line 27: | ||
* Would prefer an API that does not require intimate knowlege of the resources in the catalog. XPath is not a good choice for this. | * Would prefer an API that does not require intimate knowlege of the resources in the catalog. XPath is not a good choice for this. | ||
| − | |||
| − | |||
== Applications of WS-RC in COSMOS == | == Applications of WS-RC in COSMOS == | ||
Revision as of 11:36, 8 August 2007
Contents
Design Considerations
- We would like to have clean layers in the design. The web services layer needs to be distinct from the actual implementation of the catalog itself.
- We would like to be able to "bind" to different underlying implementations. For COSMOS in open source, can we use a simple flat file or do we need a relational DB?
- In the case of COSMOS and CMDBf, we would NOT choose to expose the MDR via WS-RC.
- What is the mapping of SML onto the schema of the RC?
- If this is a simple mapping, e.g. <EntryRef> = <SMLRef>, <ResourceRef> = <SMLRef w/EPR>, or something like that, can we simply use the existing SML repository that we have now and expose WS APIs that exchange RC entries via an XSLT? SML to WSRC Mapping
- The WS-RC spec talks about the use of WS-R
- Do we need a flat file representation, relational, or both?
- We think both
- What additional dependencies are we bringing in?
- 3rd party code, e.g. xerces, xpath..
- Currently looking at Qexo as the XQuery engine for this effort.
- Qexo is available as part of the KAWA framework. It is freely available under the X11/MIT License. We will need to investigate this license to see if it will work for this effort.
- The web site for Qexo is http://www.gnu.org/software/qexo/
- I have given this information to Mark Weitzel for submission and approval.
- Currently looking at Qexo as the XQuery engine for this effort.
- JVM et..
- 3rd party code, e.g. xerces, xpath..
- What parts of the spec will we not implement?
- 3.6.4: Don't need to support meta-epr.
- Would prefer an API that does not require intimate knowlege of the resources in the catalog. XPath is not a good choice for this.
Applications of WS-RC in COSMOS
- Management Domain
- Data Broker
- The remote APIs will be WS-RC APIs
Use Cases
- Mohammad to enumerate
Action Items / ToDos
- David: First cut at SML - RC mapping
- Jimmy/Mark: Map RC onto the Domain and Data Broker use cases