|
Revision 5, 1.1 kB
(checked in by margs, 15 years ago)
|
|
moving old files into new repository.
|
| Line | |
|---|
| 1 | RUNNING THE TRANSFORMATION |
|---|
| 2 | ***************************** |
|---|
| 3 | Store the ddr_HTMLReport_transformation.xsl, the .css and the schema at some location. Include the processing instruction |
|---|
| 4 | in the xml to be transformed: |
|---|
| 5 | |
|---|
| 6 | <?xml version="1.0" encoding="ISO-8859-1"?> |
|---|
| 7 | <?xml-stylesheet type="text/xsl" href="ddr_HTMLReport_transformation.xsl"?> |
|---|
| 8 | <witsml:drillReports |
|---|
| 9 | |
|---|
| 10 | Open the xml file in a browser, and the content should be formated in HTML |
|---|
| 11 | |
|---|
| 12 | |
|---|
| 13 | |
|---|
| 14 | |
|---|
| 15 | TECHNICAL DETAILS |
|---|
| 16 | ******************* |
|---|
| 17 | The transforamtion file has refenrece to and imports the drill report schema. The reason for this is to enable |
|---|
| 18 | lookup of element definitions via the RDS URL. |
|---|
| 19 | |
|---|
| 20 | So, the drill report schema must be imported and the schamaLocation (in the import element) has to reflect the |
|---|
| 21 | location of the file. Furthermore, this file is used when retreiving the RDS reference. As the schema file name might |
|---|
| 22 | changes when NPD/Ptil is issuing their new official verison, we have introduced a global variable to hold the file name. |
|---|
| 23 | Thus, if the file name changes, updating the value (i.e. select) of the variable "ddrSchema" should be ok. |
|---|
