1) Test procedures
- As of now there is no need to merge test procedures
- 1-2 test scenarios will be added in related to the usage of ENTSO-E Network Modelling Database
- We see a need to predifine what is to be checked in the IOP, i.e. for a certain model we agree to check reative power of XX genartor, or specific load flow parameters for the whole model.

In case IOP participants see any optimizations in the test procedures that could be applied please inform Chavdar. 

2) Questions from participants:

- Is it mandatory not to use the character CARRIAGE RETURN  to mark the end of a line ?

If you use only LINE FEED then a FTP transfer of the file from Linux to VMS is not possible since VMS will interpret the file as one record having a length equal to the whole file. Such long records are not

accepted by the VMS operating system. Wouldn't it be better to have a standard with CARRIAGE RETURN and LINE FEED which can be used on all operating systems ?
    > Binary mode should be used for the exchange of the files. There is no change in line endings in binary mode. 
    > In XML please see http://www.w3.org/TR/REC-xml/#sec-line-ends

Kendall's questions:

 - Test file from last IOP: Inconsistency between rdfs and instance file; namespace inconsistency generationtype. Test data problem. To be fixed

- Geographic Profile: Class Location the direction of the association to PowerSystemResource. Agreement is necessary. Check with Alan 

Pending issues for further discussion:

1) List of issues to WG13;

2) RDFID UUID issue - additional info provided by Michał Wiernowolski