Difference between revisions of "Implementation FAQ"
Charliemccay (talk | contribs) |
Charliemccay (talk | contribs) |
||
| Line 5: | Line 5: | ||
| − | + | == Source and target systems lack rich semantics == | |
Black and white TV to HDTV to black and white | Black and white TV to HDTV to black and white | ||
| − | + | == cost benefit ratio - startup costs are very high == | |
Have a running system using V2, how do I justify moving to V3, esp as V2 just keeps getting better. | Have a running system using V2, how do I justify moving to V3, esp as V2 just keeps getting better. | ||
| − | + | == version 3 documentation not as easy to use as V2 documents == | |
In v2.3.1 as a PDF -- one big document and using the find button is a great way to find what you want. This is particularly good as a single document. | In v2.3.1 as a PDF -- one big document and using the find button is a great way to find what you want. This is particularly good as a single document. | ||
| − | + | == information overload == | |
How much information has to be shared with a trading partner. If the trading partner is V3 knowledgeable is it easier to do. | How much information has to be shared with a trading partner. If the trading partner is V3 knowledgeable is it easier to do. | ||
| − | + | == learning curve == | |
Implementers have to understand the RIM classes and attributes | Implementers have to understand the RIM classes and attributes | ||
| − | + | == fill the blanks transforms == | |
V3 startup for implementers can be done by creating “fill the blanks” transforms. | V3 startup for implementers can be done by creating “fill the blanks” transforms. | ||
| − | + | == V2 implementation profiles are easy to read == | |
It is | It is | ||
| − | + | == get some example implementation guides on the wiki == | |
| − | + | == how to write an implementation guide == | |
Added technical guide | Added technical guide | ||
Added conformance profile guide | Added conformance profile guide | ||
Added wrapper documentation | Added wrapper documentation | ||
| − | + | == selling point for V3 == | |
What is the real value of the reference model in V3 – what is the life of the system – this can be a long time for strategic programs. These need to be future-proofed. Action: what does the marketing committee have on the rationale for using V3. | What is the real value of the reference model in V3 – what is the life of the system – this can be a long time for strategic programs. These need to be future-proofed. Action: what does the marketing committee have on the rationale for using V3. | ||
Revision as of 16:29, 17 May 2006
This currently contains a set of brainstormed points that can be turned into a FAQ for implementation. The first draft of this page was created on the fly in the committee, partly as a group learning exercise to establish that we could develop the content in this way.
The following text will be retained as a record of the session, and then a new set of pages will be created to form a basis for the FAQ
Contents
- 1 Source and target systems lack rich semantics
- 2 cost benefit ratio - startup costs are very high
- 3 version 3 documentation not as easy to use as V2 documents
- 4 information overload
- 5 learning curve
- 6 fill the blanks transforms
- 7 V2 implementation profiles are easy to read
- 8 get some example implementation guides on the wiki
- 9 how to write an implementation guide
- 10 selling point for V3
Source and target systems lack rich semantics
Black and white TV to HDTV to black and white
cost benefit ratio - startup costs are very high
Have a running system using V2, how do I justify moving to V3, esp as V2 just keeps getting better.
version 3 documentation not as easy to use as V2 documents
In v2.3.1 as a PDF -- one big document and using the find button is a great way to find what you want. This is particularly good as a single document.
information overload
How much information has to be shared with a trading partner. If the trading partner is V3 knowledgeable is it easier to do.
learning curve
Implementers have to understand the RIM classes and attributes
fill the blanks transforms
V3 startup for implementers can be done by creating “fill the blanks” transforms.
V2 implementation profiles are easy to read
It is
get some example implementation guides on the wiki
how to write an implementation guide
Added technical guide Added conformance profile guide Added wrapper documentation
selling point for V3
What is the real value of the reference model in V3 – what is the life of the system – this can be a long time for strategic programs. These need to be future-proofed. Action: what does the marketing committee have on the rationale for using V3.
