PIOP tasks

Belongs to Portfolio interoperability prototyping (PIOP)

=Portfolio Interoperability Prototyping Tasks=

set out in e-mail of 2008-01-15
1. Please consider the practice scenario A, and let us know briefly if you think it is realistic, or could be improved for realism. If the practice you know about is similar to this but different in significant detail, please write the differences. You may need to talk to practitioners to ensure it is realistic.

What I suggested at the meeting was that we would all benefit from a set of this kind of scenarios, so that each of the three collaborators can consider what records would be made or used in this and other similar scenarios. This leads to the second and third request...

2. Please make a list of the records that would be generated or used in your system relevant to this scenario above.

3. Please write other scenarios (perhaps of a comparable length) particularly to illustrate the use of parts of your system records that are not exercised by the first scenario above.

We can then discuss which other ones to use in a similar way.

There are several reasons why these would be of value:
 * it will help greatly in giving us reference points so we know what we are talking about
 * we can work towards semantic interoperability - where similar records used in similar ways are marked up so that they can be recognised as being used similarly
 * we have the basis for writing examples of sets of information used, relating to these scenarios
 * it will greatly help other readers relate to our work, by giving context in a commonly understandable way.

added 2008-02-29
4. Please compose chunks of XML relevant to one of the Scenarios. If you can do that in a style that is like the examples so far, good: but equally good if you come up with something that is different from the examples so far. Anything useful will be added to the examples. Nice, simple examples are just as welcome as more complex ones.

agreed 2008-03-07
5. Agree a definite initial set of: This is to be done by March 20th, before Easter.
 * types
 * categories
 * relationships
 * fields to be added as sub-elements of entries

6. Hand-writing of XML examples
 * to agree on what is and is not within scope
 * to agree on formats we are going to use
 * finish process by April 18th - all partners to agree all examples

7. Also by April 18th, complete draft mappings of each partner's fields to the emerging spec. Here or earlier, start work on coding import and export.

8. Get import and export running on all 3 sites (Nottingham deferred until the arrival of a new programmer).
 * Prototypes to be running by mid May (now delayed due to competing work pressures)
 * Check export and import of own information.
 * Pass round generated XML between partners.