| Test ID: | ibm-not-wf-P85-ibm85n56.xml |
| Collection: | IBM XML Conformance Test Suite - Production 85 |
|
Tests BaseChar with an illegal character. The character #x0991
occurs as the first character of the PITarget in the PI in the DTD.
|
| Sections [Rules]: | B. |
| Test ID: | ibm-not-wf-P85-ibm85n57.xml |
| Collection: | IBM XML Conformance Test Suite - Production 85 |
|
Tests BaseChar with an illegal character. The character #x0992
occurs as the first character of the PITarget in the PI in the DTD.
|
| Sections [Rules]: | B. |
| Test ID: | ibm-not-wf-P85-ibm85n58.xml |
| Collection: | IBM XML Conformance Test Suite - Production 85 |
|
Tests BaseChar with an illegal character. The character #x09A9
occurs as the first character of the PITarget in the PI in the DTD.
|
| Sections [Rules]: | B. |
| Test ID: | ibm-not-wf-P85-ibm85n59.xml |
| Collection: | IBM XML Conformance Test Suite - Production 85 |
|
Tests BaseChar with an illegal character. The character #x09B1
occurs as the first character of the PITarget in the PI in the DTD.
|
| Sections [Rules]: | B. |
| Test ID: | ibm-not-wf-P85-ibm85n60.xml |
| Collection: | IBM XML Conformance Test Suite - Production 85 |
|
Tests BaseChar with an illegal character. The character #x09B5
occurs as the first character of the PITarget in the PI in the DTD.
|
| Sections [Rules]: | B. |
| Test ID: | ibm-not-wf-P85-ibm85n61.xml |
| Collection: | IBM XML Conformance Test Suite - Production 85 |
|
Tests BaseChar with an illegal character. The character #x09BA
occurs as the first character of the PITarget in the PI in the DTD.
|
| Sections [Rules]: | B. |
| Test ID: | ibm-not-wf-P85-ibm85n62.xml |
| Collection: | IBM XML Conformance Test Suite - Production 85 |
|
Tests BaseChar with an illegal character. The character #x09DE
occurs as the first character of the PITarget in the PI in the DTD.
|
| Sections [Rules]: | B. |
| Test ID: | ibm-not-wf-P85-ibm85n63.xml |
| Collection: | IBM XML Conformance Test Suite - Production 85 |
|
Tests BaseChar with an illegal character. The character #x09E2
occurs as the first character of the PITarget in the PI in the DTD.
|
| Sections [Rules]: | B. |
| Test ID: | ibm-not-wf-P85-ibm85n64.xml |
| Collection: | IBM XML Conformance Test Suite - Production 85 |
|
Tests BaseChar with an illegal character. The character #x09F2
occurs as the first character of the PITarget in the PI in the DTD.
|
| Sections [Rules]: | B. |
| Test ID: | ibm-not-wf-P85-ibm85n65.xml |
| Collection: | IBM XML Conformance Test Suite - Production 85 |
|
Tests BaseChar with an illegal character. The character #x0A0B
occurs as the first character of the PITarget in the PI in the DTD.
|
| Sections [Rules]: | B. |
| Test ID: | ibm-not-wf-P85-ibm85n66.xml |
| Collection: | IBM XML Conformance Test Suite - Production 85 |
|
Tests BaseChar with an illegal character. The character #x0A11
occurs as the first character of the PITarget in the PI in the DTD.
|
| Sections [Rules]: | B. |
| Test ID: | ibm-not-wf-P85-ibm85n67.xml |
| Collection: | IBM XML Conformance Test Suite - Production 85 |
|
Tests BaseChar with an illegal character. The character #x0A29
occurs as the first character of the PITarget in the PI in the DTD.
|
| Sections [Rules]: | B. |
| Test ID: | ibm-not-wf-P85-ibm85n68.xml |
| Collection: | IBM XML Conformance Test Suite - Production 85 |
|
Tests BaseChar with an illegal character. The character #x0A31
occurs as the first character of the PITarget in the PI in the DTD.
|
| Sections [Rules]: | B. |
| Test ID: | ibm-not-wf-P85-ibm85n69.xml |
| Collection: | IBM XML Conformance Test Suite - Production 85 |
|
Tests BaseChar with an illegal character. The character #x0A34
occurs as the first character of the PITarget in the PI in the DTD.
|
| Sections [Rules]: | B. |
| Test ID: | ibm-not-wf-P85-ibm85n70.xml |
| Collection: | IBM XML Conformance Test Suite - Production 85 |
|
Tests BaseChar with an illegal character. The character #x0A37
occurs as the first character of the PITarget in the PI in the DTD.
|
| Sections [Rules]: | B. |
| Test ID: | ibm-not-wf-P85-ibm85n71.xml |
| Collection: | IBM XML Conformance Test Suite - Production 85 |
|
Tests BaseChar with an illegal character. The character #x0A3A
occurs as the first character of the PITarget in the PI in the DTD.
|
| Sections [Rules]: | B. |
| Test ID: | ibm-not-wf-P85-ibm85n72.xml |
| Collection: | IBM XML Conformance Test Suite - Production 85 |
|
Tests BaseChar with an illegal character. The character #x0A5B
occurs as the first character of the PITarget in the PI in the DTD.
|
| Sections [Rules]: | B. |
| Test ID: | ibm-not-wf-P85-ibm85n73.xml |
| Collection: | IBM XML Conformance Test Suite - Production 85 |
|
Tests BaseChar with an illegal character. The character #x0A70
occurs as the first character of the PITarget in the PI in the DTD.
|
| Sections [Rules]: | B. |
| Test ID: | ibm-not-wf-P85-ibm85n74.xml |
| Collection: | IBM XML Conformance Test Suite - Production 85 |
|
Tests BaseChar with an illegal character. The character #x0A75
occurs as the first character of the PITarget in the PI in the DTD.
|
| Sections [Rules]: | B. |
| Test ID: | ibm-not-wf-P85-ibm85n75.xml |
| Collection: | IBM XML Conformance Test Suite - Production 85 |
|
Tests BaseChar with an illegal character. The character #x
occurs as the first character of the PITarget in the PI in the DTD.
|
| Sections [Rules]: | B. |
| Test ID: | ibm-not-wf-P85-ibm85n76.xml |
| Collection: | IBM XML Conformance Test Suite - Production 85 |
|
Tests BaseChar with an illegal character. The character #x0ABC
occurs as the first character of the PITarget in the PI in the DTD.
|
| Sections [Rules]: | B. |
| Test ID: | ibm-not-wf-P85-ibm85n77.xml |
| Collection: | IBM XML Conformance Test Suite - Production 85 |
|
Tests BaseChar with an illegal character. The character #x0A92
occurs as the first character of the PITarget in the PI in the DTD.
|
| Sections [Rules]: | B. |
| Test ID: | ibm-not-wf-P85-ibm85n78.xml |
| Collection: | IBM XML Conformance Test Suite - Production 85 |
|
Tests BaseChar with an illegal character. The character #x0AA9
occurs as the first character of the PITarget in the PI in the DTD.
|
| Sections [Rules]: | B. |
| Test ID: | ibm-not-wf-P85-ibm85n79.xml |
| Collection: | IBM XML Conformance Test Suite - Production 85 |
|
Tests BaseChar with an illegal character. The character #x0AB1
occurs as the first character of the PITarget in the PI in the DTD.
|
| Sections [Rules]: | B. |
| Test ID: | ibm-not-wf-P85-ibm85n80.xml |
| Collection: | IBM XML Conformance Test Suite - Production 85 |
|
Tests BaseChar with an illegal character. The character #x0AB4
occurs as the first character of the PITarget in the PI in the DTD.
|
| Sections [Rules]: | B. |
| Test ID: | ibm-not-wf-P85-ibm85n81.xml |
| Collection: | IBM XML Conformance Test Suite - Production 85 |
|
Tests BaseChar with an illegal character. The character #x0ABA
occurs as the first character of the PITarget in the PI in the DTD.
|
| Sections [Rules]: | B. |
| Test ID: | ibm-not-wf-P85-ibm85n82.xml |
| Collection: | IBM XML Conformance Test Suite - Production 85 |
|
Tests BaseChar with an illegal character. The character #x0B04
occurs as the first character of the PITarget in the PI in the DTD.
|
| Sections [Rules]: | B. |
| Test ID: | ibm-not-wf-P85-ibm85n83.xml |
| Collection: | IBM XML Conformance Test Suite - Production 85 |
|
Tests BaseChar with an illegal character. The character #x0B0D
occurs as the first character of the PITarget in the PI in the DTD.
|
| Sections [Rules]: | B. |
| Test ID: | ibm-not-wf-P85-ibm85n84.xml |
| Collection: | IBM XML Conformance Test Suite - Production 85 |
|
Tests BaseChar with an illegal character. The character #x0B11
occurs as the first character of the PITarget in the PI in the DTD.
|
| Sections [Rules]: | B. |
| Test ID: | ibm-not-wf-P85-ibm85n85.xml |
| Collection: | IBM XML Conformance Test Suite - Production 85 |
|
Tests BaseChar with an illegal character. The character #x0B29
occurs as the first character of the PITarget in the PI in the DTD.
|
| Sections [Rules]: | B. |
| Test ID: | ibm-not-wf-P85-ibm85n86.xml |
| Collection: | IBM XML Conformance Test Suite - Production 85 |
|
Tests BaseChar with an illegal character. The character #x0B31
occurs as the first character of the PITarget in the PI in the DTD.
|
| Sections [Rules]: | B. |
| Test ID: | ibm-not-wf-P85-ibm85n87.xml |
| Collection: | IBM XML Conformance Test Suite - Production 85 |
|
Tests BaseChar with an illegal character. The character #x0B34
occurs as the first character of the PITarget in the PI in the DTD.
|
| Sections [Rules]: | B. |
| Test ID: | ibm-not-wf-P85-ibm85n88.xml |
| Collection: | IBM XML Conformance Test Suite - Production 85 |
|
Tests BaseChar with an illegal character. The character #x0B3A
occurs as the first character of the PITarget in the PI in the DTD.
|
| Sections [Rules]: | B. |
| Test ID: | ibm-not-wf-P85-ibm85n89.xml |
| Collection: | IBM XML Conformance Test Suite - Production 85 |
|
Tests BaseChar with an illegal character. The character #x0B3E
occurs as the first character of the PITarget in the PI in the DTD.
|
| Sections [Rules]: | B. |
| Test ID: | ibm-not-wf-P85-ibm85n90.xml |
| Collection: | IBM XML Conformance Test Suite - Production 85 |
|
Tests BaseChar with an illegal character. The character #x0B5E
occurs as the first character of the PITarget in the PI in the DTD.
|
| Sections [Rules]: | B. |
| Test ID: | ibm-not-wf-P85-ibm85n91.xml |
| Collection: | IBM XML Conformance Test Suite - Production 85 |
|
Tests BaseChar with an illegal character. The character #x0B62
occurs as the first character of the PITarget in the PI in the DTD.
|
| Sections [Rules]: | B. |
| Test ID: | ibm-not-wf-P85-ibm85n92.xml |
| Collection: | IBM XML Conformance Test Suite - Production 85 |
|
Tests BaseChar with an illegal character. The character #x0B8B
occurs as the first character of the PITarget in the PI in the DTD.
|
| Sections [Rules]: | B. |
| Test ID: | ibm-not-wf-P85-ibm85n93.xml |
| Collection: | IBM XML Conformance Test Suite - Production 85 |
|
Tests BaseChar with an illegal character. The character #x0B91
occurs as the first character of the PITarget in the PI in the DTD.
|
| Sections [Rules]: | B. |
| Test ID: | ibm-not-wf-P85-ibm85n94.xml |
| Collection: | IBM XML Conformance Test Suite - Production 85 |
|
Tests BaseChar with an illegal character. The character #x0B98
occurs as the first character of the PITarget in the PI in the DTD.
|
| Sections [Rules]: | B. |
| Test ID: | ibm-not-wf-P85-ibm85n95.xml |
| Collection: | IBM XML Conformance Test Suite - Production 85 |
|
Tests BaseChar with an illegal character. The character #x0B9B
occurs as the first character of the PITarget in the PI in the DTD.
|
| Sections [Rules]: | B. |
| Test ID: | ibm-not-wf-P85-ibm85n96.xml |
| Collection: | IBM XML Conformance Test Suite - Production 85 |
|
Tests BaseChar with an illegal character. The character #x0B9D
occurs as the first character of the PITarget in the PI in the DTD.
|
| Sections [Rules]: | B. |
| Test ID: | ibm-not-wf-P85-ibm85n97.xml |
| Collection: | IBM XML Conformance Test Suite - Production 85 |
|
Tests BaseChar with an illegal character. The character #x0BA0
occurs as the first character of the PITarget in the PI in the DTD.
|
| Sections [Rules]: | B. |
| Test ID: | ibm-not-wf-P85-ibm85n98.xml |
| Collection: | IBM XML Conformance Test Suite - Production 85 |
|
Tests BaseChar with an illegal character. The character #x0BA7
occurs as the first character of the PITarget in the PI in the DTD.
|
| Sections [Rules]: | B. |
| Test ID: | ibm-not-wf-P85-ibm85n99.xml |
| Collection: | IBM XML Conformance Test Suite - Production 85 |
|
Tests BaseChar with an illegal character. The character #x0BAB
occurs as the first character of the PITarget in the PI in the DTD.
|
| Sections [Rules]: | B. |
| Test ID: | ibm-not-wf-P86-ibm86n01.xml |
| Collection: | IBM XML Conformance Test Suite - Production 86 |
|
Tests Ideographic with an illegal character. The character #x4CFF
occurs as the first character in the PITarget in the PI in the DTD.
|
| Sections [Rules]: | B. |
| Test ID: | ibm-not-wf-P86-ibm86n02.xml |
| Collection: | IBM XML Conformance Test Suite - Production 86 |
|
Tests Ideographic with an illegal character. The character #x9FA6
occurs as the first character in the PITarget in the PI in the DTD.
|
| Sections [Rules]: | B. |
| Test ID: | ibm-not-wf-P86-ibm86n03.xml |
| Collection: | IBM XML Conformance Test Suite - Production 86 |
|
Tests Ideographic with an illegal character. The character #x3008
occurs as the first character in the PITarget in the PI in the DTD.
|
| Sections [Rules]: | B. |
| Test ID: | ibm-not-wf-P86-ibm86n04.xml |
| Collection: | IBM XML Conformance Test Suite - Production 86 |
|
Tests Ideographic with an illegal character. The character #x302A
occurs as the first character in the PITarget in the PI in the DTD.
|
| Sections [Rules]: | B. |
| Test ID: | ibm-not-wf-P87-ibm87n01.xml |
| Collection: | IBM XML Conformance Test Suite - Production 87 |
|
Tests CombiningChar with an illegal character. The character #x02FF
occurs as the second character in the PITarget in the PI in the DTD.
|
| Sections [Rules]: | B. |
| Test ID: | ibm-not-wf-P87-ibm87n02.xml |
| Collection: | IBM XML Conformance Test Suite - Production 87 |
|
Tests CombiningChar with an illegal character. The character #x0346
occurs as the second character in the PITarget in the PI in the DTD.
|
| Sections [Rules]: | B. |
| Test ID: | ibm-not-wf-P87-ibm87n03.xml |
| Collection: | IBM XML Conformance Test Suite - Production 87 |
|
Tests CombiningChar with an illegal character. The character #x0362
occurs as the second character in the PITarget in the PI in the DTD.
|
| Sections [Rules]: | B. |
| Test ID: | ibm-not-wf-P87-ibm87n04.xml |
| Collection: | IBM XML Conformance Test Suite - Production 87 |
|
Tests CombiningChar with an illegal character. The character #x0487
occurs as the second character in the PITarget in the PI in the DTD.
|
| Sections [Rules]: | B. |
| Test ID: | ibm-not-wf-P87-ibm87n05.xml |
| Collection: | IBM XML Conformance Test Suite - Production 87 |
|
Tests CombiningChar with an illegal character. The character #x05A2
occurs as the second character in the PITarget in the PI in the DTD.
|
| Sections [Rules]: | B. |
| Test ID: | ibm-not-wf-P87-ibm87n06.xml |
| Collection: | IBM XML Conformance Test Suite - Production 87 |
|
Tests CombiningChar with an illegal character. The character #x05BA
occurs as the second character in the PITarget in the PI in the DTD.
|
| Sections [Rules]: | B. |
| Test ID: | ibm-not-wf-P87-ibm87n07.xml |
| Collection: | IBM XML Conformance Test Suite - Production 87 |
|
Tests CombiningChar with an illegal character. The character #x05BE
occurs as the second character in the PITarget in the PI in the DTD.
|
| Sections [Rules]: | B. |
| Test ID: | ibm-not-wf-P87-ibm87n08.xml |
| Collection: | IBM XML Conformance Test Suite - Production 87 |
|
Tests CombiningChar with an illegal character. The character #x05C0
occurs as the second character in the PITarget in the PI in the DTD.
|
| Sections [Rules]: | B. |
| Test ID: | ibm-not-wf-P87-ibm87n09.xml |
| Collection: | IBM XML Conformance Test Suite - Production 87 |
|
Tests CombiningChar with an illegal character. The character #x05C3
occurs as the second character in the PITarget in the PI in the DTD.
|
| Sections [Rules]: | B. |
| Test ID: | ibm-not-wf-P87-ibm87n10.xml |
| Collection: | IBM XML Conformance Test Suite - Production 87 |
|
Tests CombiningChar with an illegal character. The character #x0653
occurs as the second character in the PITarget in the PI in the DTD.
|
| Sections [Rules]: | B. |
| Test ID: | ibm-not-wf-P87-ibm87n11.xml |
| Collection: | IBM XML Conformance Test Suite - Production 87 |
|
Tests CombiningChar with an illegal character. The character #x06B8
occurs as the second character in the PITarget in the PI in the DTD.
|
| Sections [Rules]: | B. |
| Test ID: | ibm-not-wf-P87-ibm87n12.xml |
| Collection: | IBM XML Conformance Test Suite - Production 87 |
|
Tests CombiningChar with an illegal character. The character #x06B9
occurs as the second character in the PITarget in the PI in the DTD.
|
| Sections [Rules]: | B. |
| Test ID: | ibm-not-wf-P87-ibm87n13.xml |
| Collection: | IBM XML Conformance Test Suite - Production 87 |
|
Tests CombiningChar with an illegal character. The character #x06E9
occurs as the second character in the PITarget in the PI in the DTD.
|
| Sections [Rules]: | B. |
| Test ID: | ibm-not-wf-P87-ibm87n14.xml |
| Collection: | IBM XML Conformance Test Suite - Production 87 |
|
Tests CombiningChar with an illegal character. The character #x06EE
occurs as the second character in the PITarget in the PI in the DTD.
|
| Sections [Rules]: | B. |
| Test ID: | ibm-not-wf-P87-ibm87n15.xml |
| Collection: | IBM XML Conformance Test Suite - Production 87 |
|
Tests CombiningChar with an illegal character. The character #x0904
occurs as the second character in the PITarget in the PI in the DTD.
|
| Sections [Rules]: | B. |
| Test ID: | ibm-not-wf-P87-ibm87n16.xml |
| Collection: | IBM XML Conformance Test Suite - Production 87 |
|
Tests CombiningChar with an illegal character. The character #x093B
occurs as the second character in the PITarget in the PI in the DTD.
|
| Sections [Rules]: | B. |
| Test ID: | ibm-not-wf-P87-ibm87n17.xml |
| Collection: | IBM XML Conformance Test Suite - Production 87 |
|
Tests CombiningChar with an illegal character. The character #x094E
occurs as the second character in the PITarget in the PI in the DTD.
|
| Sections [Rules]: | B. |
| Test ID: | ibm-not-wf-P87-ibm87n18.xml |
| Collection: | IBM XML Conformance Test Suite - Production 87 |
|
Tests CombiningChar with an illegal character. The character #x0955
occurs as the second character in the PITarget in the PI in the DTD.
|
| Sections [Rules]: | B. |
| Test ID: | ibm-not-wf-P87-ibm87n19.xml |
| Collection: | IBM XML Conformance Test Suite - Production 87 |
|
Tests CombiningChar with an illegal character. The character #x0964
occurs as the second character in the PITarget in the PI in the DTD.
|
| Sections [Rules]: | B. |
| Test ID: | ibm-not-wf-P87-ibm87n20.xml |
| Collection: | IBM XML Conformance Test Suite - Production 87 |
|
Tests CombiningChar with an illegal character. The character #x0984
occurs as the second character in the PITarget in the PI in the DTD.
|
| Sections [Rules]: | B. |
| Test ID: | ibm-not-wf-P87-ibm87n21.xml |
| Collection: | IBM XML Conformance Test Suite - Production 87 |
|
Tests CombiningChar with an illegal character. The character #x09C5
occurs as the second character in the PITarget in the PI in the DTD.
|
| Sections [Rules]: | B. |
| Test ID: | ibm-not-wf-P87-ibm87n22.xml |
| Collection: | IBM XML Conformance Test Suite - Production 87 |
|
Tests CombiningChar with an illegal character. The character #x09C9
occurs as the second character in the PITarget in the PI in the DTD.
|
| Sections [Rules]: | B. |
| Test ID: | ibm-not-wf-P87-ibm87n23.xml |
| Collection: | IBM XML Conformance Test Suite - Production 87 |
|
Tests CombiningChar with an illegal character. The character #x09CE
occurs as the second character in the PITarget in the PI in the DTD.
|
| Sections [Rules]: | B. |
| Test ID: | ibm-not-wf-P87-ibm87n24.xml |
| Collection: | IBM XML Conformance Test Suite - Production 87 |
|
Tests CombiningChar with an illegal character. The character #x09D8
occurs as the second character in the PITarget in the PI in the DTD.
|
| Sections [Rules]: | B. |
| Test ID: | ibm-not-wf-P87-ibm87n25.xml |
| Collection: | IBM XML Conformance Test Suite - Production 87 |
|
Tests CombiningChar with an illegal character. The character #x09E4
occurs as the second character in the PITarget in the PI in the DTD.
|
| Sections [Rules]: | B. |
| Test ID: | ibm-not-wf-P87-ibm87n26.xml |
| Collection: | IBM XML Conformance Test Suite - Production 87 |
|
Tests CombiningChar with an illegal character. The character #x0A03
occurs as the second character in the PITarget in the PI in the DTD.
|
| Sections [Rules]: | B. |
| Test ID: | ibm-not-wf-P87-ibm87n27.xml |
| Collection: | IBM XML Conformance Test Suite - Production 87 |
|
Tests CombiningChar with an illegal character. The character #x0A3D
occurs as the second character in the PITarget in the PI in the DTD.
|
| Sections [Rules]: | B. |
| Test ID: | ibm-not-wf-P87-ibm87n28.xml |
| Collection: | IBM XML Conformance Test Suite - Production 87 |
|
Tests CombiningChar with an illegal character. The character #x0A46
occurs as the second character in the PITarget in the PI in the DTD.
|
| Sections [Rules]: | B. |
| Test ID: | ibm-not-wf-P87-ibm87n29.xml |
| Collection: | IBM XML Conformance Test Suite - Production 87 |
|
Tests CombiningChar with an illegal character. The character #x0A49
occurs as the second character in the PITarget in the PI in the DTD.
|
| Sections [Rules]: | B. |
| Test ID: | ibm-not-wf-P87-ibm87n30.xml |
| Collection: | IBM XML Conformance Test Suite - Production 87 |
|
Tests CombiningChar with an illegal character. The character #x0A4E
occurs as the second character in the PITarget in the PI in the DTD.
|
| Sections [Rules]: | B. |
| Test ID: | ibm-not-wf-P87-ibm87n31.xml |
| Collection: | IBM XML Conformance Test Suite - Production 87 |
|
Tests CombiningChar with an illegal character. The character #x0A80
occurs as the second character in the PITarget in the PI in the DTD.
|
| Sections [Rules]: | B. |
| Test ID: | ibm-not-wf-P87-ibm87n32.xml |
| Collection: | IBM XML Conformance Test Suite - Production 87 |
|
Tests CombiningChar with an illegal character. The character #x0A84
occurs as the second character in the PITarget in the PI in the DTD.
|
| Sections [Rules]: | B. |
| Test ID: | ibm-not-wf-P87-ibm87n33.xml |
| Collection: | IBM XML Conformance Test Suite - Production 87 |
|
Tests CombiningChar with an illegal character. The character #x0ABB
occurs as the second character in the PITarget in the PI in the DTD.
|
| Sections [Rules]: | B. |
| Test ID: | ibm-not-wf-P87-ibm87n34.xml |
| Collection: | IBM XML Conformance Test Suite - Production 87 |
|
Tests CombiningChar with an illegal character. The character #x0AC6
occurs as the second character in the PITarget in the PI in the DTD.
|
| Sections [Rules]: | B. |
| Test ID: | ibm-not-wf-P87-ibm87n35.xml |
| Collection: | IBM XML Conformance Test Suite - Production 87 |
|
Tests CombiningChar with an illegal character. The character #x0ACA
occurs as the second character in the PITarget in the PI in the DTD.
|
| Sections [Rules]: | B. |
| Test ID: | ibm-not-wf-P87-ibm87n36.xml |
| Collection: | IBM XML Conformance Test Suite - Production 87 |
|
Tests CombiningChar with an illegal character. The character #x0ACE
occurs as the second character in the PITarget in the PI in the DTD.
|
| Sections [Rules]: | B. |
| Test ID: | ibm-not-wf-P87-ibm87n37.xml |
| Collection: | IBM XML Conformance Test Suite - Production 87 |
|
Tests CombiningChar with an illegal character. The character #x0B04
occurs as the second character in the PITarget in the PI in the DTD.
|
| Sections [Rules]: | B. |
| Test ID: | ibm-not-wf-P87-ibm87n38.xml |
| Collection: | IBM XML Conformance Test Suite - Production 87 |
|
Tests CombiningChar with an illegal character. The character #x0B3B
occurs as the second character in the PITarget in the PI in the DTD.
|
| Sections [Rules]: | B. |
| Test ID: | ibm-not-wf-P87-ibm87n39.xml |
| Collection: | IBM XML Conformance Test Suite - Production 87 |
|
Tests CombiningChar with an illegal character. The character #x0B44
occurs as the second character in the PITarget in the PI in the DTD.
|
| Sections [Rules]: | B. |
| Test ID: | ibm-not-wf-P87-ibm87n40.xml |
| Collection: | IBM XML Conformance Test Suite - Production 87 |
|
Tests CombiningChar with an illegal character. The character #x0B4A
occurs as the second character in the PITarget in the PI in the DTD.
|
| Sections [Rules]: | B. |
| Test ID: | ibm-not-wf-P87-ibm87n41.xml |
| Collection: | IBM XML Conformance Test Suite - Production 87 |
|
Tests CombiningChar with an illegal character. The character #x0B4E
occurs as the second character in the PITarget in the PI in the DTD.
|
| Sections [Rules]: | B. |
| Test ID: | ibm-not-wf-P87-ibm87n42.xml |
| Collection: | IBM XML Conformance Test Suite - Production 87 |
|
Tests CombiningChar with an illegal character. The character #x0B58
occurs as the second character in the PITarget in the PI in the DTD.
|
| Sections [Rules]: | B. |
| Test ID: | ibm-not-wf-P87-ibm87n43.xml |
| Collection: | IBM XML Conformance Test Suite - Production 87 |
|
Tests CombiningChar with an illegal character. The character #x0B84
occurs as the second character in the PITarget in the PI in the DTD.
|
| Sections [Rules]: | B. |
| Test ID: | ibm-not-wf-P87-ibm87n44.xml |
| Collection: | IBM XML Conformance Test Suite - Production 87 |
|
Tests CombiningChar with an illegal character. The character #x0BC3
occurs as the second character in the PITarget in the PI in the DTD.
|
| Sections [Rules]: | B. |
| Test ID: | ibm-not-wf-P87-ibm87n45.xml |
| Collection: | IBM XML Conformance Test Suite - Production 87 |
|
Tests CombiningChar with an illegal character. The character #x0BC9
occurs as the second character in the PITarget in the PI in the DTD.
|
| Sections [Rules]: | B. |
| Test ID: | ibm-not-wf-P87-ibm87n46.xml |
| Collection: | IBM XML Conformance Test Suite - Production 87 |
|
Tests CombiningChar with an illegal character. The character #x0BD6
occurs as the second character in the PITarget in the PI in the DTD.
|
| Sections [Rules]: | B. |
| Test ID: | ibm-not-wf-P87-ibm87n47.xml |
| Collection: | IBM XML Conformance Test Suite - Production 87 |
|
Tests CombiningChar with an illegal character. The character #x0C0D
occurs as the second character in the PITarget in the PI in the DTD.
|
| Sections [Rules]: | B. |
| Test ID: | ibm-not-wf-P87-ibm87n48.xml |
| Collection: | IBM XML Conformance Test Suite - Production 87 |
|
Tests CombiningChar with an illegal character. The character #x0C45
occurs as the second character in the PITarget in the PI in the DTD.
|
| Sections [Rules]: | B. |
| Test ID: | ibm-not-wf-P87-ibm87n49.xml |
| Collection: | IBM XML Conformance Test Suite - Production 87 |
|
Tests CombiningChar with an illegal character. The character #x0C49
occurs as the second character in the PITarget in the PI in the DTD.
|
| Sections [Rules]: | B. |
| Test ID: | ibm-not-wf-P87-ibm87n50.xml |
| Collection: | IBM XML Conformance Test Suite - Production 87 |
|
Tests CombiningChar with an illegal character. The character #x0C54
occurs as the second character in the PITarget in the PI in the DTD.
|
| Sections [Rules]: | B. |
| Test ID: | ibm-not-wf-P87-ibm87n51.xml |
| Collection: | IBM XML Conformance Test Suite - Production 87 |
|
Tests CombiningChar with an illegal character. The character #x0C81
occurs as the second character in the PITarget in the PI in the DTD.
|
| Sections [Rules]: | B. |
| Test ID: | ibm-not-wf-P87-ibm87n52.xml |
| Collection: | IBM XML Conformance Test Suite - Production 87 |
|
Tests CombiningChar with an illegal character. The character #x0C84
occurs as the second character in the PITarget in the PI in the DTD.
|
| Sections [Rules]: | B. |
| Test ID: | ibm-not-wf-P87-ibm87n53.xml |
| Collection: | IBM XML Conformance Test Suite - Production 87 |
|
Tests CombiningChar with an illegal character. The character #x0CC5
occurs as the second character in the PITarget in the PI in the DTD.
|
| Sections [Rules]: | B. |
| Test ID: | ibm-not-wf-P87-ibm87n54.xml |
| Collection: | IBM XML Conformance Test Suite - Production 87 |
|
Tests CombiningChar with an illegal character. The character #x0CC9
occurs as the second character in the PITarget in the PI in the DTD.
|
| Sections [Rules]: | B. |
| Test ID: | ibm-not-wf-P87-ibm87n55.xml |
| Collection: | IBM XML Conformance Test Suite - Production 87 |
|
Tests CombiningChar with an illegal character. The character #x0CD4
occurs as the second character in the PITarget in the PI in the DTD.
|
| Sections [Rules]: | B. |
| Test ID: | ibm-not-wf-P87-ibm87n56.xml |
| Collection: | IBM XML Conformance Test Suite - Production 87 |
|
Tests CombiningChar with an illegal character. The character #x0CD7
occurs as the second character in the PITarget in the PI in the DTD.
|
| Sections [Rules]: | B. |
| Test ID: | ibm-not-wf-P87-ibm87n57.xml |
| Collection: | IBM XML Conformance Test Suite - Production 87 |
|
Tests CombiningChar with an illegal character. The character #x0D04
occurs as the second character in the PITarget in the PI in the DTD.
|
| Sections [Rules]: | B. |
| Test ID: | ibm-not-wf-P87-ibm87n58.xml |
| Collection: | IBM XML Conformance Test Suite - Production 87 |
|
Tests CombiningChar with an illegal character. The character #x0D45
occurs as the second character in the PITarget in the PI in the DTD.
|
| Sections [Rules]: | B. |
| Test ID: | ibm-not-wf-P87-ibm87n59.xml |
| Collection: | IBM XML Conformance Test Suite - Production 87 |
|
Tests CombiningChar with an illegal character. The character #x0D49
occurs as the second character in the PITarget in the PI in the DTD.
|
| Sections [Rules]: | B. |
| Test ID: | ibm-not-wf-P87-ibm87n60.xml |
| Collection: | IBM XML Conformance Test Suite - Production 87 |
|
Tests CombiningChar with an illegal character. The character #x0D4E
occurs as the second character in the PITarget in the PI in the DTD.
|
| Sections [Rules]: | B. |
| Test ID: | ibm-not-wf-P87-ibm87n61.xml |
| Collection: | IBM XML Conformance Test Suite - Production 87 |
|
Tests CombiningChar with an illegal character. The character #x0D58
occurs as the second character in the PITarget in the PI in the DTD.
|
| Sections [Rules]: | B. |
| Test ID: | ibm-not-wf-P87-ibm87n62.xml |
| Collection: | IBM XML Conformance Test Suite - Production 87 |
|
Tests CombiningChar with an illegal character. The character #x0E3F
occurs as the second character in the PITarget in the PI in the DTD.
|
| Sections [Rules]: | B. |
| Test ID: | ibm-not-wf-P87-ibm87n63.xml |
| Collection: | IBM XML Conformance Test Suite - Production 87 |
|
Tests CombiningChar with an illegal character. The character #x0E3B
occurs as the second character in the PITarget in the PI in the DTD.
|
| Sections [Rules]: | B. |
| Test ID: | ibm-not-wf-P87-ibm87n64.xml |
| Collection: | IBM XML Conformance Test Suite - Production 87 |
|
Tests CombiningChar with an illegal character. The character #x0E4F
occurs as the second character in the PITarget in the PI in the DTD.
|
| Sections [Rules]: | B. |
| Test ID: | ibm-not-wf-P87-ibm87n66.xml |
| Collection: | IBM XML Conformance Test Suite - Production 87 |
|
Tests CombiningChar with an illegal character. The character #x0EBA
occurs as the second character in the PITarget in the PI in the DTD.
|
| Sections [Rules]: | B. |
| Test ID: | ibm-not-wf-P87-ibm87n67.xml |
| Collection: | IBM XML Conformance Test Suite - Production 87 |
|
Tests CombiningChar with an illegal character. The character #x0EBE
occurs as the second character in the PITarget in the PI in the DTD.
|
| Sections [Rules]: | B. |
| Test ID: | ibm-not-wf-P87-ibm87n68.xml |
| Collection: | IBM XML Conformance Test Suite - Production 87 |
|
Tests CombiningChar with an illegal character. The character #x0ECE
occurs as the second character in the PITarget in the PI in the DTD.
|
| Sections [Rules]: | B. |
| Test ID: | ibm-not-wf-P87-ibm87n69.xml |
| Collection: | IBM XML Conformance Test Suite - Production 87 |
|
Tests CombiningChar with an illegal character. The character #x0F1A
occurs as the second character in the PITarget in the PI in the DTD.
|
| Sections [Rules]: | B. |
| Test ID: | ibm-not-wf-P87-ibm87n70.xml |
| Collection: | IBM XML Conformance Test Suite - Production 87 |
|
Tests CombiningChar with an illegal character. The character #x0F36
occurs as the second character in the PITarget in the PI in the DTD.
|
| Sections [Rules]: | B. |
| Test ID: | ibm-not-wf-P87-ibm87n71.xml |
| Collection: | IBM XML Conformance Test Suite - Production 87 |
|
Tests CombiningChar with an illegal character. The character #x0F38
occurs as the second character in the PITarget in the PI in the DTD.
|
| Sections [Rules]: | B. |
| Test ID: | ibm-not-wf-P87-ibm87n72.xml |
| Collection: | IBM XML Conformance Test Suite - Production 87 |
|
Tests CombiningChar with an illegal character. The character #x0F3B
occurs as the second character in the PITarget in the PI in the DTD.
|
| Sections [Rules]: | B. |
| Test ID: | ibm-not-wf-P87-ibm87n73.xml |
| Collection: | IBM XML Conformance Test Suite - Production 87 |
|
Tests CombiningChar with an illegal character. The character #x0F3A
occurs as the second character in the PITarget in the PI in the DTD.
|
| Sections [Rules]: | B. |
| Test ID: | ibm-not-wf-P87-ibm87n74.xml |
| Collection: | IBM XML Conformance Test Suite - Production 87 |
|
Tests CombiningChar with an illegal character. The character #x0F70
occurs as the second character in the PITarget in the PI in the DTD.
|
| Sections [Rules]: | B. |
| Test ID: | ibm-not-wf-P87-ibm87n75.xml |
| Collection: | IBM XML Conformance Test Suite - Production 87 |
|
Tests CombiningChar with an illegal character. The character #x0F85
occurs as the second character in the PITarget in the PI in the DTD.
|
| Sections [Rules]: | B. |
| Test ID: | ibm-not-wf-P87-ibm87n76.xml |
| Collection: | IBM XML Conformance Test Suite - Production 87 |
|
Tests CombiningChar with an illegal character. The character #x0F8C
occurs as the second character in the PITarget in the PI in the DTD.
|
| Sections [Rules]: | B. |
| Test ID: | ibm-not-wf-P87-ibm87n77.xml |
| Collection: | IBM XML Conformance Test Suite - Production 87 |
|
Tests CombiningChar with an illegal character. The character #x0F96
occurs as the second character in the PITarget in the PI in the DTD.
|
| Sections [Rules]: | B. |
| Test ID: | ibm-not-wf-P87-ibm87n78.xml |
| Collection: | IBM XML Conformance Test Suite - Production 87 |
|
Tests CombiningChar with an illegal character. The character #x0F98
occurs as the second character in the PITarget in the PI in the DTD.
|
| Sections [Rules]: | B. |
| Test ID: | ibm-not-wf-P87-ibm87n79.xml |
| Collection: | IBM XML Conformance Test Suite - Production 87 |
|
Tests CombiningChar with an illegal character. The character #x0FB0
occurs as the second character in the PITarget in the PI in the DTD.
|
| Sections [Rules]: | B. |
| Test ID: | ibm-not-wf-P87-ibm87n80.xml |
| Collection: | IBM XML Conformance Test Suite - Production 87 |
|
Tests CombiningChar with an illegal character. The character #x0FB8
occurs as the second character in the PITarget in the PI in the DTD.
|
| Sections [Rules]: | B. |
| Test ID: | ibm-not-wf-P87-ibm87n81.xml |
| Collection: | IBM XML Conformance Test Suite - Production 87 |
|
Tests CombiningChar with an illegal character. The character #x0FBA
occurs as the second character in the PITarget in the PI in the DTD.
|
| Sections [Rules]: | B. |
| Test ID: | ibm-not-wf-P87-ibm87n82.xml |
| Collection: | IBM XML Conformance Test Suite - Production 87 |
|
Tests CombiningChar with an illegal character. The character #x20DD
occurs as the second character in the PITarget in the PI in the DTD.
|
| Sections [Rules]: | B. |
| Test ID: | ibm-not-wf-P87-ibm87n83.xml |
| Collection: | IBM XML Conformance Test Suite - Production 87 |
|
Tests CombiningChar with an illegal character. The character #x20E2
occurs as the second character in the PITarget in the PI in the DTD.
|
| Sections [Rules]: | B. |
| Test ID: | ibm-not-wf-P87-ibm87n84.xml |
| Collection: | IBM XML Conformance Test Suite - Production 87 |
|
Tests CombiningChar with an illegal character. The character #x3030
occurs as the second character in the PITarget in the PI in the DTD.
|
| Sections [Rules]: | B. |
| Test ID: | ibm-not-wf-P87-ibm87n85.xml |
| Collection: | IBM XML Conformance Test Suite - Production 87 |
|
Tests CombiningChar with an illegal character. The character #x309B
occurs as the second character in the PITarget in the PI in the DTD.
|
| Sections [Rules]: | B. |
| Test ID: | ibm-not-wf-P88-ibm88n01.xml |
| Collection: | IBM XML Conformance Test Suite - Production 88 |
|
Tests Digit with an illegal character. The character #x0029
occurs as the second character in the PITarget in the PI in the DTD.
|
| Sections [Rules]: | B. |
| Test ID: | ibm-not-wf-P88-ibm88n02.xml |
| Collection: | IBM XML Conformance Test Suite - Production 88 |
|
Tests Digit with an illegal character. The character #x003B
occurs as the second character in the PITarget in the PI in the DTD.
|
| Sections [Rules]: | B. |
| Test ID: | ibm-not-wf-P88-ibm88n03.xml |
| Collection: | IBM XML Conformance Test Suite - Production 88 |
|
Tests Digit with an illegal character. The character #x066A
occurs as the second character in the PITarget in the PI in the DTD.
|
| Sections [Rules]: | B. |
| Test ID: | ibm-not-wf-P88-ibm88n04.xml |
| Collection: | IBM XML Conformance Test Suite - Production 88 |
|
Tests Digit with an illegal character. The character #x06FA
occurs as the second character in the PITarget in the PI in the DTD.
|
| Sections [Rules]: | B. |
| Test ID: | ibm-not-wf-P88-ibm88n05.xml |
| Collection: | IBM XML Conformance Test Suite - Production 88 |
|
Tests Digit with an illegal character. The character #x0970
occurs as the second character in the PITarget in the PI in the DTD.
|
| Sections [Rules]: | B. |
| Test ID: | ibm-not-wf-P88-ibm88n06.xml |
| Collection: | IBM XML Conformance Test Suite - Production 88 |
|
Tests Digit with an illegal character. The character #x09F2
occurs as the second character in the PITarget in the PI in the DTD.
|
| Sections [Rules]: | B. |
| Test ID: | ibm-not-wf-P88-ibm88n08.xml |
| Collection: | IBM XML Conformance Test Suite - Production 88 |
|
Tests Digit with an illegal character. The character #x0AF0
occurs as the second character in the PITarget in the PI in the DTD.
|
| Sections [Rules]: | B. |
| Test ID: | ibm-not-wf-P88-ibm88n09.xml |
| Collection: | IBM XML Conformance Test Suite - Production 88 |
|
Tests Digit with an illegal character. The character #x0B70
occurs as the second character in the PITarget in the PI in the DTD.
|
| Sections [Rules]: | B. |
| Test ID: | ibm-not-wf-P88-ibm88n10.xml |
| Collection: | IBM XML Conformance Test Suite - Production 88 |
|
Tests Digit with an illegal character. The character #x0C65
occurs as the second character in the PITarget in the PI in the DTD.
|
| Sections [Rules]: | B. |
| Test ID: | ibm-not-wf-P88-ibm88n11.xml |
| Collection: | IBM XML Conformance Test Suite - Production 88 |
|
Tests Digit with an illegal character. The character #x0CE5
occurs as the second character in the PITarget in the PI in the DTD.
|
| Sections [Rules]: | B. |
| Test ID: | ibm-not-wf-P88-ibm88n12.xml |
| Collection: | IBM XML Conformance Test Suite - Production 88 |
|
Tests Digit with an illegal character. The character #x0CF0
occurs as the second character in the PITarget in the PI in the DTD.
|
| Sections [Rules]: | B. |
| Test ID: | ibm-not-wf-P88-ibm88n13.xml |
| Collection: | IBM XML Conformance Test Suite - Production 88 |
|
Tests Digit with an illegal character. The character #x0D70
occurs as the second character in the PITarget in the PI in the DTD.
|
| Sections [Rules]: | B. |
| Test ID: | ibm-not-wf-P88-ibm88n14.xml |
| Collection: | IBM XML Conformance Test Suite - Production 88 |
|
Tests Digit with an illegal character. The character #x0E5A
occurs as the second character in the PITarget in the PI in the DTD.
|
| Sections [Rules]: | B. |
| Test ID: | ibm-not-wf-P88-ibm88n15.xml |
| Collection: | IBM XML Conformance Test Suite - Production 88 |
|
Tests Digit with an illegal character. The character #x0EDA
occurs as the second character in the PITarget in the PI in the DTD.
|
| Sections [Rules]: | B. |
| Test ID: | ibm-not-wf-P88-ibm88n16.xml |
| Collection: | IBM XML Conformance Test Suite - Production 88 |
|
Tests Digit with an illegal character. The character #x0F2A
occurs as the second character in the PITarget in the PI in the DTD.
|
| Sections [Rules]: | B. |
| Test ID: | ibm-not-wf-P89-ibm89n01.xml |
| Collection: | IBM XML Conformance Test Suite - Production 89 |
|
Tests Extender with an illegal character. The character #x00B6
occurs as the second character in the PITarget in the PI in the DTD.
|
| Sections [Rules]: | B. |
| Test ID: | ibm-not-wf-P89-ibm89n02.xml |
| Collection: | IBM XML Conformance Test Suite - Production 89 |
|
Tests Extender with an illegal character. The character #x00B8
occurs as the second character in the PITarget in the PI in the DTD.
|
| Sections [Rules]: | B. |
| Test ID: | ibm-not-wf-P89-ibm89n03.xml |
| Collection: | IBM XML Conformance Test Suite - Production 89 |
|
Tests Extender with an illegal character. The character #x02D2
occurs as the second character in the PITarget in the PI in the DTD.
|
| Sections [Rules]: | B. |
| Test ID: | ibm-not-wf-P89-ibm89n04.xml |
| Collection: | IBM XML Conformance Test Suite - Production 89 |
|
Tests Extender with an illegal character. The character #x03FE
occurs as the second character in the PITarget in the PI in the DTD.
|
| Sections [Rules]: | B. |
| Test ID: | ibm-not-wf-P89-ibm89n05.xml |
| Collection: | IBM XML Conformance Test Suite - Production 89 |
|
Tests Extender with an illegal character. The character #x065F
occurs as the second character in the PITarget in the PI in the DTD.
|
| Sections [Rules]: | B. |
| Test ID: | ibm-not-wf-P89-ibm89n06.xml |
| Collection: | IBM XML Conformance Test Suite - Production 89 |
|
Tests Extender with an illegal character. The character #x0EC7
occurs as the second character in the PITarget in the PI in the DTD.
|
| Sections [Rules]: | B. |
| Test ID: | ibm-not-wf-P89-ibm89n07.xml |
| Collection: | IBM XML Conformance Test Suite - Production 89 |
|
Tests Extender with an illegal character. The character #x3006
occurs as the second character in the PITarget in the PI in the DTD.
|
| Sections [Rules]: | B. |
| Test ID: | ibm-not-wf-P89-ibm89n08.xml |
| Collection: | IBM XML Conformance Test Suite - Production 89 |
|
Tests Extender with an illegal character. The character #x3030
occurs as the second character in the PITarget in the PI in the DTD.
|
| Sections [Rules]: | B. |
| Test ID: | ibm-not-wf-P89-ibm89n09.xml |
| Collection: | IBM XML Conformance Test Suite - Production 89 |
|
Tests Extender with an illegal character. The character #x3036
occurs as the second character in the PITarget in the PI in the DTD.
|
| Sections [Rules]: | B. |
| Test ID: | ibm-not-wf-P89-ibm89n10.xml |
| Collection: | IBM XML Conformance Test Suite - Production 89 |
|
Tests Extender with an illegal character. The character #x309C
occurs as the second character in the PITarget in the PI in the DTD.
|
| Sections [Rules]: | B. |
| Test ID: | ibm-not-wf-P89-ibm89n11.xml |
| Collection: | IBM XML Conformance Test Suite - Production 89 |
|
Tests Extender with an illegal character. The character #x309F
occurs as the second character in the PITarget in the PI in the DTD.
|
| Sections [Rules]: | B. |
| Test ID: | ibm-not-wf-P89-ibm89n12.xml |
| Collection: | IBM XML Conformance Test Suite - Production 89 |
|
Tests Extender with an illegal character. The character #x30FF
occurs as the second character in the PITarget in the PI in the DTD.
|
3.4 XML Documents with Optional Errors
Conforming XML 1.0 Processors are permitted to ignore
certain errors, or to report them at user option. In this
section of this test report are found descriptions of
test cases which fit into this category.
Processor behavior on such test cases does not affect
conformance to the XML 1.0 (Second Edition) Recommendation, except as noted.
| Sections [Rules]: | 2.3, 4.2.2 [11] |
| Test ID: | o-p11pass1 |
| Collection: | OASIS/NIST TESTS, 1-Nov-1998 |
|
system literals may not contain
URI fragments
|
| Sections [Rules]: | 4.1 |
| Test ID: | not-wf-not-sa-005 |
| Collection: | James Clark XMLTEST cases, 18-Nov-1998 |
|
Tests the Entity Declared VC by referring to an
undefined parameter entity within an external entity.
|
| Sections [Rules]: | 4.1 |
| Test ID: | ibm-invalid-P68-ibm68i01.xml |
| Collection: | IBM XML Conformance Test Suite - Production 68 |
|
Tests invalid EntityRef which is against P68 VC: Entity Declared. The GE with
the name "ge2" is referred in the file ibm68i01.dtd", but not declared.
There is an output test associated with this
input file.
|
| Sections [Rules]: | 4.1 |
| Test ID: | ibm-invalid-P68-ibm68i02.xml |
| Collection: | IBM XML Conformance Test Suite - Production 68 |
|
Tests invalid EntityRef which is against P68 VC: Entity Declared. The GE with
the name "ge1" is referred before declared in the file ibm68i01.dtd".
There is an output test associated with this
input file.
|
| Sections [Rules]: | 4.1 |
| Test ID: | ibm-invalid-P68-ibm68i03.xml |
| Collection: | IBM XML Conformance Test Suite - Production 68 |
|
Tests invalid EntityRef which is against P68 VC: Entity Declared. The GE with
the name "ge2" is referred in the file ibm68i03.ent", but not declared.
There is an output test associated with this
input file.
|
| Sections [Rules]: | 4.1 |
| Test ID: | ibm-invalid-P68-ibm68i04.xml |
| Collection: | IBM XML Conformance Test Suite - Production 68 |
|
Tests invalid EntityRef which is against P68 VC: Entity Declared. The GE with
the name "ge1" is referred before declared in the file ibm68i04.ent".
There is an output test associated with this
input file.
|
| Sections [Rules]: | 4.1 |
| Test ID: | ibm-invalid-P69-ibm69i01.xml |
| Collection: | IBM XML Conformance Test Suite - Production 69 |
|
Tests invalid PEReference which is against P69 VC: Entity Declared. The Name
"pe2" in the PEReference in the file ibm69i01.dtd does not match the Name of
any declared PE.
There is an output test associated with this
input file.
|
| Sections [Rules]: | 4.1 |
| Test ID: | ibm-invalid-P69-ibm69i02.xml |
| Collection: | IBM XML Conformance Test Suite - Production 69 |
|
Tests invalid PEReference which is against P69 VC: Entity Declared. The PE with
the name "pe1" is referred before declared in the file ibm69i02.dtd
There is an output test associated with this
input file.
|
| Sections [Rules]: | 4.1 |
| Test ID: | ibm-invalid-P69-ibm69i03.xml |
| Collection: | IBM XML Conformance Test Suite - Production 69 |
|
Tests invalid PEReference which is against P69 VC: Entity Declared. The Name
"pe3" in the PEReference in the file ibm69i03.ent does not match the Name of
any declared PE.
There is an output test associated with this
input file.
|
| Sections [Rules]: | 4.1 |
| Test ID: | ibm-invalid-P69-ibm69i04.xml |
| Collection: | IBM XML Conformance Test Suite - Production 69 |
|
Tests invalid PEReference which is against P69 VC: Entity Declared. The PE with
the name "pe2" is referred before declared in the file ibm69i04.ent.
There is an output test associated with this
input file.
|
| Sections [Rules]: | 4.1 |
| Test ID: | ibm-not-wf-P69-ibm69n05.xml |
| Collection: | IBM XML Conformance Test Suite - Production 69 |
|
Based on E29 substantial source: minutes XML-Syntax 1999-02-24 E38 in
XML 1.0 Errata, this WFC does not apply to P69, but the VC Entity declared
still apply.
Tests PEReference which is against P69 WFC: Entity Declared. The PE
with the name "paaa" is referred before declared in the DTD.
|
| Sections [Rules]: | 4.2.2 [75] |
| Test ID: | uri01 |
| Collection: | Sun Microsystems XML Tests |
|
SYSTEM ids may not have URI fragments
|
| Sections [Rules]: | 4.3.3 [4,84] |
| Test ID: | pr-xml-euc-jp |
| Collection: | Fuji Xerox Japanese Text Tests |
|
Test support for the EUC-JP encoding, and for text
which relies on Japanese characters.
If a processor does not support this encoding, it must
report a fatal error.
(Also requires ability to process a moderately complex DTD.)
|
| Sections [Rules]: | 4.3.3 [4,84] |
| Test ID: | pr-xml-iso-2022-jp |
| Collection: | Fuji Xerox Japanese Text Tests |
|
Test support for the ISO-2022-JP encoding, and for text
which relies on Japanese characters.
If a processor does not support this encoding, it must
report a fatal error.
(Also requires ability to process a moderately complex DTD.)
|
| Sections [Rules]: | 4.3.3 [4,84] |
| Test ID: | pr-xml-shift_jis |
| Collection: | Fuji Xerox Japanese Text Tests |
|
Test support for the Shift_JIS encoding, and for text
which relies on Japanese characters.
If a processor does not support this encoding, it must
report a fatal error.
(Also requires ability to process a moderately complex DTD.)
|
| Sections [Rules]: | 4.3.3 [4,84] |
| Test ID: | weekly-euc-jp |
| Collection: | Fuji Xerox Japanese Text Tests |
|
Test support for EUC-JP encoding, and
XML names which contain Japanese characters.
If a processor does not support this encoding, it must
report a fatal error.
|
| Sections [Rules]: | 4.3.3 [4,84] |
| Test ID: | weekly-iso-2022-jp |
| Collection: | Fuji Xerox Japanese Text Tests |
|
Test support for ISO-2022-JP encoding, and
XML names which contain Japanese characters.
If a processor does not support this encoding, it must
report a fatal error.
|
| Sections [Rules]: | 4.3.3 [4,84] |
| Test ID: | weekly-shift_jis |
| Collection: | Fuji Xerox Japanese Text Tests |
|
Test support for Shift_JIS encoding, and
XML names which contain Japanese characters.
If a processor does not support this encoding, it must
report a fatal error.
|
4. Contributors (Non-normative)
A team of volunteer members have participated in the
development of this work. Contributions have come from:
- Murry Altheim, Sun Microsystems
- Mary Brady, NIST
- Tim Boland, NIST
- David Brownell, Sun Microsystems
- James Clark
- Karin Donker, IBM
- Irina Golfman, Inera Incorporated
- Tony Graham, Mulberry Technologies
- G. Ken Holman, Crane Softwrights Ltd
- Alex Milowski, Veo Systems, Inc
- Makota Murata, Fuji Xerox
- Miles O'Reilly, Microstar Software, Ltd
- Matt Timmermans, Microstar Software, Ltd
- Richard Rivello, NIST
- Lynne Rosenthal, NIST
- Brian Schellar, Chrystal Software
- Bill Smith, Sun Microsystems
- Trevor Veary, Software AG
- Richard Tobin, University of Edinburgh
- Jonathan Marsh, Microsoft
- Daniel Veillard, Imaq
- Jonathan Marsh, Microsoft
- Paul Grosso, Arbortext
End


An icon sets contains an arbitrary number of glyphs
Icons serve a very similar function to text in a page. In Semantic icons receive a special tag <i>
which allow for an abbreviated markup when sitting along-side text.
Icons can represent types of content found on websites
Alarm
Alarm Outline
Browser
Bug
Calendar
Calendar Outline
Cloud
Code
Comment
Comment Outline
Comments
Comments Outline
Content
Dashboard
External Link
External Link Square
Feed
History
Home
Idea
Inbox
Lab
Mail
Mail Outline
Mail square
Map
Payment
Privacy
Protect
Search
Setting
Settings
Shop
Sitemap
Tag
Tags
Tasks
Terminal
Ticket
Trophy
Wifi
Icons can represent common actions a user can take
Adjust
Archive
Ban
Bookmark
Call
Call Square
Cloud Download
Cloud Upload
Compress
Configure
Download
Edit
Erase
Exchange
External Share
Expand
Filter
Flag
Flag Outline
Hide
Lock
Mail Forward
Pin
Print
Random
Recycle
Refresh
Remove Bookmark
Repeat
Reply All
Reply
Retweet
Send
Send Outline
Share Alternate
Share Alternate Square
Share
Share Square
Sign in
Sign out
Theme
Translate
Undo
Unhide
Unlock Alternate
Unlock
Upload
Wait
Wizard
Write
Write Square
Icons can alert users to the type of message being displayed
Announcement
Flag
Help
Help Circle
Info
Info Circle
Warning
Warning Circle
Warning Sign
Icons can represent types of people
Child
Doctor
Female
Handicap
Male
Student
User
Users
Icons can alert users to common ways to adjust page layouts
Grid Layout
List Layout
Block Layout
Zoom
Zoom Out
Resize Vertical
Resize Horizontal
Maximize
Crop
Icons can be used to represent common objects
Anchor
Bar
Bomb
Book
Bullseye
Checkered Flag
Cocktail
Fax
Fire Extinguisher
Fire
Gift
Leaf
Legal
Lemon
Life Ring
Lightning
Magnet
Money
Moon
Plane
Puzzle
Rain
Road
Rocket
Shipping
Suitcase
Sun
Travel
Treatment
World
Icons can be used to create shapes
Crosshairs
Asterisk
Certificate
Spinner
Circle
Quote Left
Quote Right
Ellipsis Horizontal
Ellipsis Vertical
Cube
Cubes
Circle Notched
Circle Thin
Icons can show whether an item is included in a set
Add Circle
Add Square
Check Circle
Check Circle Outline
Check Square
Checkmark Box
Checkmark
Minus Circle
Minus
Minus Square
Minus Square Outline
Move
Plus
Plus Square Outline
Radio
Remove Circle
Remove Circle Outline
Remove
Selected Radio
Icons can represent common media types
Bar Chart
Camera Retro
Film
Photo
Sound
Icons can be used to indicate a direction
Angle Double Down
Angle Double Left
Angle Double Right
Angle Double Up
Angle Down
Angle Left
Angle Right
Angle Up
Arrow Circle Down
Arrow Circle Left
Arrow Circle Outline Down
Arrow Circle Outline Left
Arrow Circle Outline Right
Arrow Circle Outline Up
Arrow Circle Right
Arrow Circle Up
Arrow Down
Arrow Left
Arrow Right
Arrow Up
Caret Down
Caret Left
Caret Right
Caret Up
Chevron Circle Down
Chevron Circle Left
Chevron Circle Right
Chevron Circle Up
Chevron Down
Chevron Left
Chevron Right
Chevron Up
Long Arrow Down
Long Arrow Left
Long Arrow Right
Long Arrow Up
Pointing Down
Pointing Left
Pointing Right
Pointing Up
Toggle Down
Toggle Left
Toggle Right
Toggle Up
Icons can represent elements of a computer and its file system
Desktop
Disk Outline
File Archive Outline
File Audio Outline
File Code Outline
File Excel Outline
File
File Image Outline
File Outline
File Pdf Outline
File Powerpoint Outline
File Text
File Text Outline
File Video Outline
File Word Outline
Folder
Folder Open
Folder Open Outline
Folder Outline
Game
Keyboard
Laptop
Level Down
Level Up
Mobile
Power
Tablet
Trash
Icons can represent common technologies
Barcode
Css3
Database
Fork
Html5
Openid
Qrcode
Rss Square
Icons can be used to represent users attitude towards content
Empty Heart
Empty Star
Frown
Heart
Meh
Smile
Star Half Empty
Star Half
Star
Thumbs Down
Thumbs Outline Down
Thumbs Outline Up
Thumbs Up
Icons can be used to represent common ways to interact with audio
Backward
Eject
Fast Backward
Fast Forward
Forward
Music
Mute
Pause
Play
Record
Step Backward
Step Forward
Stop
Unmute
Video Play
Video Play Outline
Volume Down
Volume Off
Volume Up
Icons can be used to represent elements on a map
Building
Building Outline
Car
Coffee
Emergency
First Aid
Food
H
Hospital
Location Arrow
Marker
Military
Paw
Space Shuttle
Spoon
Taxi
Tree
University
Icons can be used to represent common actions inside a table
Columns
Sort Alphabet Ascending
Sort Alphabet Descending
Sort Ascending
Sort Content Ascending
Sort Content Descending
Sort Descending
Sort
Sort Numeric Ascending
Sort Numeric Descending
Table
Icons can represent common actions when editing text
Align Center
Align Justify
Align Left
Align Right
Attach
Bold
Copy
Cut
Font
Header
Indent
Italic
Linkify
List
Ordered List
Outdent
Paragraph
Paste
Save
Strikethrough
Subscript
Superscript
Text Height
Text Width
Underline
Unlink
Unordered List
Icons can represent units of currency
Dollar
Euro
Lira
Pound
Ruble
Rupee
Won
Yen
Icons can represent logos to common brands
Adn
Android
Apple
Behance
Behance Square
Bitbucket
Bitbucket Square
Bitcoin
Codepen
Delicious
Deviantart
Digg
Dribbble
Dropbox
Drupal
Empire
Facebook
Facebook Square
Flickr
Foursquare
Git
Git Square
Github Alternate
Github
Github Square
Gittip
Google
Google Plus
Google Plus Square
Hacker News
Instagram
Joomla
Jsfiddle
Linkedin
Linkedin Square
Linux
Maxcdn
Pagelines
Pied Piper Alternate
Pied Piper
Pinterest
Pinterest Square
Qq
Rebel
Reddit
Reddit Square
Renren
Skype
Slack
Soundcloud
Spotify
Stack Exchange
Stack Overflow
Steam
Steam Square
StumbleUpon Circle
StumbleUpon
Tencent Weibo
Trello
Tumblr
Tumblr Square
Twitter
Twitter Square
Vimeo
Vine
Vk
Wechat
Weibo
Windows
Wordpress
Xing
Xing Square
Yahoo
YouTube
YouTube Play
YouTube Square
An icon can show that it is disabled
An icon can be used as a simple loader
An icon can be formatted as a link
An icon can be formatted to appear circular
In 0.x.x
bordered was formally known as squared
An icon can be formatted to appear bordered
An icon can be formatted with different colors
an icon can have its colors inverted for contrast


Full width
One Half
One half
One Third
Two Thirds
One Quarter
Three Quarters
One Sixth
Five Sixths
Print info circle (1 page)
Print Record (1 page)
Print Twitter (1 page)
Print Phone (1 page)
Print Mail (1 page)
Print Mail (1 page)
Print search (1 page)
Print download (1 page)
Print Print (1 page)
Print Book (1 page)
Print Down open big (1 page)
Print right open big (1 page)
Print up open big (1 page)
Print cog (1 page)
Print check (1 page)
Print search1 (1 page)
Print popup (1 page)
Print up-bold (1 page)
Print down bold (1 page)
Print users (1 page)


Locks layout panel.
lock(panel, message, [showSpinner])
| message |
string, message |
| showSpinner |
boolean, optional, spinner indicator |
Description
This method will lock the panel by added a semi-transparent div on top of popup content. The user will not be able to interact with
the panel or its content until the panel is unlocked with .unlock(). This method will call
w2utils.lock() to perform the locking.
The first argument type is the name of the panel. It can be one of the following:
- top
- left
- main
- right
- preview
- bottom
You have 3 options how you want to lock the content. Lock with a message and a spinner:
Lock w/o a message, but with a spinner:
Lock w/o a message and w/o a spinner:


Run & Debug with PyDev¶
Totorial¶
Wit PyDev, you can run, debug, break and check variable.
1. create a PyDev project¶
After installed PyDev, the file -> new… menu can now create new PyDev project:
file -> new ... -> others ... -> PyDev -> PyDev Project
Then follow the new project dialog, create a new project.
2. add a source folder¶
After project been created, create a new PyDev module by:
right click in project panel -> new folder
Input folder name: lect01.
3. add a source file¶
right click folder -> new file
Input file name: fibonacci.py. Then in the file, past the file content, fibonacci.py into your new fibonacci.py file.
4. add a break point¶
Set a break point by click at the source file line number. (by double click a the left of line number or in menu, Run, Debug)
5. debug¶
Now debug it:
right click the project -> debug as -> Python Run
With break point stop the program, you can check what’s going on at the point, such as the variables are values like expected.
Tip:
Name your project and source file name with a starting letter. Otherwise
the breakpoint doesn't stop the process (Windows 10, Eclipse 4.17.0, PyDev
<IP_ADDRESS>09061309).
Like any other programming language, follow the common conventions e.g. start a variable with letter or underscore, “_”. We’ve encountered a weired situation that someone’s debug precess doesn’t stop at where the line with a breakpoint. After rename her project name, which is actually “1”, and the python source file name, which is “12.py”, everything works as expected.
Trouble Shootings¶
When a new python source module importing another module, e.g. a tester importing a tested class, Eclipse PyDev may show error markers.
To get rid of the wrong error report:
right click project -> PyDev -> remove error markers


• A list of available positions can be viewed 24/7 at our Receiving Section's bulletin boards located in front of the Subic Gym .
• Yes. You may apply for multiple positions that are currently open as long as you meet the minimum qualification standards of the vacancies.
• You may follow-up and check the status of your application at the Receiving Section based on the follow-up slip issued by the Manpower Services staff. You will also find notices of examination/ interview posted on the bulletin boards. If you are selected for an interview/ examination, you will be contacted in most cases by phone call or text by the locators/ investors you applied in.
• NO. Applying for any job vacancies inside the Subic Bay Freeport Zone is free-of-charge. If there are persons who ask for money in exchange of a job inside the Zone, please report it to the Manpower Services Division at the Subic Gym or at Bldg. 255. Or you may call 252.4346 / 252.4273.
• Initially, an SBF Investor/Locator shall address a formal request to the Labor Department via the Request for Recruitment Assistance (RRA) Form. The RRA form shall be used to submit request for job vacancy announcement. The job vacancy shall be advertised at the Receiving Section (in front of the Subic Gym) and other conspicuous places and/or through the Public Employment Service Offices (PESO) in various municipalities in Bataan and Zambales and other areas in Region III. It will also be published at the career microsite maintained by the Department and powered by JobStreet.com. Or you may visit the Evaluation Section at Rm. 138, Bldg. 255 to assist you in browsing at available resumes maintained by the Division.
• With the introduction of the SBMA Career Portal and Joint Recruitment service in collaboration with JobStreet.com, hiring may be done online via the microsite of SBMA. Registered SBF locators/investors may avail unlimited job posting at the microsite and experience the fastest, most effective, efficient and innovative online recruitment process only at www.sbma.com/subicjobs. To know more of the details, please coordinate with the SBMA Labor Department at +<IP_ADDRESS>01 and talk to your Account Officers or with JobStreet.com at<EMAIL_ADDRESS>• The SBMA locator/ investor may call or visit the Manpower Services Division at Bldg. 255, Rm. 138 for the Issuance and endorsement of Register of Eligibles (ROE) or the MSD Account Officer assigned to the company will inform the Locator/investor if there are available ROEs. An ROE is a list of all job applicants who qualified for the job vacancy.
• Hiring of people inside the Subic Bay Freeport Zone is a prerogative of the investor/locator. The applicants selected from the ROE and who were considered for employment by the SBF investor must pass through the Labor Department for their gate pass processing and eventually for endorsement for the issuance of their entry/exit pass to the Office Services Department thus, paving the way for the selected applicant(s) to get on-board and work for the SBF investor at a specified date. The Manpower Services Division handles gatepass processing for Investors/Locators while the Service Contracting Office is for the Contractors and Sub-contractors.
• The Labor Center discourages investor/locator/enterprise/contractor in resorting to direct hiring to avoid possible employment-related problems in the future.
• A posting fee of P200.00/day shall apply to non-SBF registered companies. Payments can be made at the SBMA Treasury Department.
• Should the investor decide to hire foreign national, it can do so by securing a Subic Clark Working Visa (SCWV). In securing an SCWV, among the supporting documents from the foreign national is an Alien Employment Permit (AEP) issued by the Department of Labor and Employment (DOLE)-RIII regional office in Pampanga. The SBMA Labor Department oversees the processing of Endorsement for AEP.
• You may visit the Conciliation and Employee Welfare Division at Bldg. 662 (at the back of Bldg. 255) for concerns on the workplace or you may call them at 252.4554 / 252.4828
• Yes. Employees of SBF Locators/Investors who got their regular employment status may avail of a 1-year computerized entry/exit pass. One of the requirements to secure a 1-year pass is by attending the Employee Orientation Seminar (EOS) every Wednesday at Bldg. 662. You may coordinate with the Workforce Development Division at 252.4067 / 252.4092 for further details.
• OJT program is being handled and monitored by the Workforce Development Division. If a student wishes to render his/her OJT in a registered company inside the Zone, the investor/locator must sponsor the student as endorsed by the student's school. For further details, you may coordinate with WDD at 252.4067 / 252.4092
• The Service Contracting Office (SCO) regulates and oversees the operation of accredited manpower and security agencies in the SBFZ. You may coordinate with SCO to check the list of accredited support services companies inside the Zone by visiting them at Rm. 210, Bldg. 255 or via phone at 252.4861


{% extends "base.html" %} {% block title %}Login{% endblock %} {% block content %}
Please enter a correct username and password. Note that both fields may be case-sensitive.
Don't have an account? Register here.


Click the large green button above the timetable then input your CRN. Courses will only be added to your timetable once you click the submit button.
Saving is done automatically every time you add or remove a course.
Because Tables for UVic uses all the hot new technology saving may not be supported in older browsers. We use HTML5's localStorage feature to save data, so you'll need Chrome 4+, FireFox 3.5+, or IE8+. On mobile, you'll need iOS 3.2+, or Android 2.1+.
There is! After adding all your courses click the export link (top right) and bookmark that link. Upon loading that link again, Tables will automatically add the courses you had in your timetable when you had originally clicked the export link.
You don't! Our export feature is designed to stop exactly this. Simply enter your CRNs on your computer then click 'Export' in the top right. Send this link to your phone (e.g. through email or Facebook) When you open that link on your phone all your courses will automatically be added.
The export feature stores all courses in the URL. So, if you had added three courses with the CRNS 20001, 20051, and 20052, your URL would look like http://www.tablesforuvic.com/index.html?&20001#20051#20052. Note the ?& after index.html - this tells the software that codes are following. After that comes the 5 digit CRNs separated by #s.
Of course! It's on Github, here. It's under the MIT license so you're free to do whatever you'd like with it, but if you use my code for anything I'd appreciate the heads up (I may even help you out!). I do my best to keep the readme up to date, but as the code is constantly changing I find I'm losing that battle.


Squibbler first started as a blog, hosted on Wordpress. But since, it has been dismantled and brought back to life as a website, hosted on Github. I searched in vain to find a hosting company that I liked, to no avail. Github was recommended by a friend, so I tried it. It has a bit of a learning curve at first, but then becomes easier to use. It allows you to record your progress, and even collaborate with others to help, if you so choose to..
Well, we are happy you decided to drop by. In the coming months we are creating our layout and content for our site, and look forward to sharing them with you.
Thanks.
Welcome to my website and blog. It's been a while waiting for the opportunity to work on this. It's not easy with 4 kids work and everything else in life that seems to take up the rest of the hours in a day. I have always wanted a blog, but have been discouraged by Wordpress, much because of the functionality of some of the plugins that don't seem to work all the time.
When we think of blogging, we


EBD - Easton Bible DIctionary
Hethlon
HETHLON
"HETHLON "wrapped up, a place on the north border of Palestine. The“way of Hethlon” (
Ezekiel 47:15
;
48:1
) is probably the pass at the end of Lebanon from the Mediterranean to the great plain of Hamath (q.v.), or the“entrance of Hamath.”
"HETHLON "wrapped up, a place on the north border of Palestine. The“way of Hethlon” (Ezekiel 47:15; 48:1) is probably the pass at the end of Lebanon from the Mediterranean to the great plain of Hamath (q.v.), or the“entrance of Hamath.”


cmake
git
© The Apache NiFi and MiNiFi projects and logos are copyright of the Apache Software Foundation.


Write a program that prompts the user to enter a series of integer values terminating in 0. When the input is done, report whether there were more even than odd values ("Even"), more odd than even values ("Odd"), or an equal number of even and odd values ("Equal"). Note that we do not want the sum of the numbers, just a comparison of the relative count of even vs. odd numbers.
Your solution must use a while loop.
Your program should run like the examples shown below:
Enter number: 17 Enter number: 36 Enter number: 10 Enter number: 0 Even
In the first example (above): there are two even numbers (36,10) and one odd number (17), so there are more even numbers than odd, as indicated in the output.
Enter number: 0
Equal
Enter number: 38 Enter number: 15 Enter number: 19 Enter number: 0 Odd


A flag to indicate whether this Subscription has already been unsubscribed.
Adds a tear down to be called during the unsubscribe() of this Subscription. Can also be used to add a child subscription.
If the tear down being added is a subscription that is already
unsubscribed, is the same reference add
is being called on, or is
Subscription.EMPTY
, it will not be added.
If this subscription is already in an closed
state, the passed
tear down logic will be executed immediately.
When a parent subscription is unsubscribed, any child subscriptions that were added to it are also unsubscribed.
The additional logic to execute on teardown.
Returns the Subscription used or created to be
added to the inner subscriptions list. This Subscription can be used with
remove()
to remove the passed teardown logic from the inner subscriptions
list.
Removes a Subscription from the internal list of subscriptions that will unsubscribe during the unsubscribe process of this Subscription.
The subscription to remove.
Disposes the resources held by the subscription. May, for instance, cancel an ongoing Observable execution or cancel any other type of work that started when the Subscription was created.
Generated using TypeDoc
Represents a disposable resource, such as the execution of an Observable. A Subscription has one important method,
unsubscribe
, that takes no argument and just disposes the resource held by the subscription.Additionally, subscriptions may be grouped together through the
add()
method, which will attach a child Subscription to the current Subscription. When a Subscription is unsubscribed, all its children (and its grandchildren) will be unsubscribed as well.


Class NodeExtensions
Extension methods for INode.
Inheritance
Inherited Members
Namespace: ZptSharp.Dom
Assembly: ZptSharp.dll
Syntax
public static class NodeExtensions
Methods
| Improve this Doc View SourceAddChildren(INode, IEnumerable<INode>, Nullable<Int32>)
Adds the specified nodesToAdd
to the specified node
.
By default, the nodes to add are appended to the end of the node's children.
In an insertIndex
is specified, though, the nodes to add are inserted into
node's children at the specified (zero-based) index position.
Declaration
public static void AddChildren(this INode node, IEnumerable<INode> nodesToAdd, int? insertIndex = default(int? ))
Parameters
| Type | Name | Description |
|---|---|---|
| INode | node | The node to which the new children should be added. |
| System.Collections.Generic.IEnumerable<INode> | nodesToAdd | Nodes to add. |
| System.Nullable<System.Int32> | insertIndex | If specified and non-null then the nodes to add are inserted into the node's children at this index. Otherwise the nodes to add are appended to the end of node's children. |
AddChildren(INode, IList<INode>, Nullable<Int32>)
Adds the specified nodesToAdd
to the specified node
.
By default, the nodes to add are appended to the end of the node's children.
In an insertIndex
is specified, though, the nodes to add are inserted into
node's children at the specified (zero-based) index position.
Declaration
public static void AddChildren(this INode node, IList<INode> nodesToAdd, int? insertIndex = default(int? ))
Parameters
| Type | Name | Description |
|---|---|---|
| INode | node | The node to which the new children should be added. |
| System.Collections.Generic.IList<INode> | nodesToAdd | Nodes to add. |
| System.Nullable<System.Int32> | insertIndex | If specified and non-null then the nodes to add are inserted into the node's children at this index. Otherwise the nodes to add are appended to the end of node's children. |
GetMatchingAttribute(INode, IEnumerable<AttributeSpec>, out AttributeSpec)
Gets the first IAttribute from the node which matches any of the specified a specs
.
Declaration
public static IAttribute GetMatchingAttribute(this INode node, IEnumerable<AttributeSpec> specs, out AttributeSpec matchingSpec)
Parameters
| Type | Name | Description |
|---|---|---|
| INode | node | The node from which to get the attribute. |
| System.Collections.Generic.IEnumerable<AttributeSpec> | specs | A collection of attribute specification. |
| AttributeSpec | matchingSpec | Exposes the specification (if any) which was matched. |
Returns
| Type | Description |
|---|---|
| IAttribute | The matching attribute, or a null reference if there is no match. |
GetMatchingAttribute(INode, AttributeSpec)
Gets the first IAttribute from the node which matches a spec
.
Declaration
public static IAttribute GetMatchingAttribute(this INode node, AttributeSpec spec)
Parameters
| Type | Name | Description |
|---|---|---|
| INode | node | The node from which to get the attribute. |
| AttributeSpec | spec | An attribute specification. |
Returns
| Type | Description |
|---|---|
| IAttribute | The matching attribute, or a null reference if there is no match. |
Remove(INode)
Removes the specified node
from its parent.
From this point onwards, the node should be discarded, as it
is no longer a valid part of the document.
Declaration
public static void Remove(this INode node)
Parameters
| Type | Name | Description |
|---|---|---|
| INode | node | The node to remove. |


Coding Quiz Challange
Try to answer the following code-related questions within the time limit. Keep in mind that incorrect answers will penalize your scrore time by ten seconds!
Question
A
B
C
D
Start Quiz
Next
Time:60
Submit


The TF-MxNE solver is a distributed inverse method (like dSPM or sLORETA) that promotes focal (sparse) sources (such as dipole fitting techniques). The benefit of this approach is that:
- it is spatio-temporal without assuming stationarity (sources properties can vary over time)
- activations are localized in space, time and frequency in one step.
- with a built-in filtering process based on a short time Fourier transform (STFT), data does not need to be low passed (just high pass to make the signals zero mean).
- the solver solves a convex optimization problem, hence cannot be trapped in local minima.
References:
A. Gramfort, D. Strohmeier, J. Haueisen, M. Hamalainen, M. Kowalski Time-Frequency Mixed-Norm Estimates: Sparse M/EEG imaging with non-stationary source activations Neuroimage, Volume 70, 15 April 2013, Pages 410-422, ISSN 1053-8119, DOI: 10.1016/j.neuroimage.2012.12.051.
A. Gramfort, D. Strohmeier, J. Haueisen, M. Hamalainen, M. Kowalski Functional Brain Imaging with M/EEG Using Structured Sparsity in Time-Frequency Dictionaries Proceedings Information Processing in Medical Imaging Lecture Notes in Computer Science, 2011, Volume 6801/2011, 600-611, DOI: 10.1007/978-3-642-22092-0_49 https://doi.org/10.1007/978-3-642-22092-0_49
# Author: Alexandre Gramfort<EMAIL_ADDRESS>#
# License: BSD (3-clause)
import mne
from mne.datasets import sample
from mne.minimum_norm import make_inverse_operator, apply_inverse
from mne.inverse_sparse import tf_mixed_norm
from mne.viz import plot_sparse_source_estimates
print(__doc__)
data_path = sample.data_path()
subjects_dir = data_path + '/subjects'
fwd_fname = data_path + '/MEG/sample/sample_audvis-meg-eeg-oct-6-fwd.fif'
ave_fname = data_path + '/MEG/sample/sample_audvis-no-filter-ave.fif'
cov_fname = data_path + '/MEG/sample/sample_audvis-shrunk-cov.fif'
# Read noise covariance matrix
cov = mne.read_cov(cov_fname)
# Handling average file
condition = 'Left visual'
evoked = mne.read_evokeds(ave_fname, condition=condition, baseline=(None, 0))
evoked = mne.pick_channels_evoked(evoked)
# We make the window slightly larger than what you'll eventually be interested
# in ([-0.05, 0.3]) to avoid edge effects.
evoked.crop(tmin=-0.1, tmax=0.4)
# Handling forward solution
forward = mne.read_forward_solution(fwd_fname, force_fixed=False,
surf_ori=True)
Out:
365 x 365 full covariance (kind = 1) found.
Read a total of 4 projection items:
PCA-v1 (1 x 102) active
PCA-v2 (1 x 102) active
PCA-v3 (1 x 102) active
Average EEG reference (1 x 59) active
Reading /home/ubuntu/mne_data/MNE-sample-data/MEG/sample/sample_audvis-no-filter-ave.fif ...
Read a total of 4 projection items:
PCA-v1 (1 x 102) active
PCA-v2 (1 x 102) active
PCA-v3 (1 x 102) active
Average EEG reference (1 x 60) active
Found the data of interest:
t = -199.80 ... 499.49 ms (Left visual)
0 CTF compensation matrices available
nave = 64 - aspect type = 100
Projections have already been applied. Setting proj attribute to True.
No baseline correction applied
Applying baseline correction (mode: mean)
Reading forward solution from /home/ubuntu/mne_data/MNE-sample-data/MEG/sample/sample_audvis-meg-eeg-oct-6-fwd.fif...
Reading a source space...
Computing patch statistics...
Patch information added...
Distance information added...
[done]
Reading a source space...
Computing patch statistics...
Patch information added...
Distance information added...
[done]
2 source spaces read
Desired named matrix (kind = 3523) not available
Read MEG forward solution (7498 sources, 306 channels, free orientations)
Desired named matrix (kind = 3523) not available
Read EEG forward solution (7498 sources, 60 channels, free orientations)
MEG and EEG forward solutions combined
Source spaces transformed to the forward solution coordinate frame
Converting to surface-based source orientations...
Average patch normals will be employed in the rotation to the local surface coordinates....
[done]
Run solver
# alpha_space regularization parameter is between 0 and 100 (100 is high)
alpha_space = 50. # spatial regularization parameter
# alpha_time parameter promotes temporal smoothness
# (0 means no temporal regularization)
alpha_time = 1. # temporal regularization parameter
loose, depth = 0.2, 0.9 # loose orientation & depth weighting
# Compute dSPM solution to be used as weights in MxNE
inverse_operator = make_inverse_operator(evoked.info, forward, cov,
loose=loose, depth=depth)
stc_dspm = apply_inverse(evoked, inverse_operator, lambda2=1. / 9.,
method='dSPM')
# Compute TF-MxNE inverse solution
stc, residual = tf_mixed_norm(evoked, forward, cov, alpha_space, alpha_time,
loose=loose, depth=depth, maxit=200, tol=1e-4,
weights=stc_dspm, weights_min=8., debias=True,
wsize=16, tstep=4, window=0.05,
return_residual=True)
# Crop to remove edges
stc.crop(tmin=-0.05, tmax=0.3)
evoked.crop(tmin=-0.05, tmax=0.3)
residual.crop(tmin=-0.05, tmax=0.3)
# Show the evoked response and the residual for gradiometers
ylim = dict(grad=[-120, 120])
evoked.pick_types(meg='grad', exclude='bads')
evoked.plot(titles=dict(grad='Evoked Response: Gradiometers'), ylim=ylim,
proj=True)
residual.pick_types(meg='grad', exclude='bads')
residual.plot(titles=dict(grad='Residuals: Gradiometers'), ylim=ylim,
proj=True)
Out:
info["bads"] and noise_cov["bads"] do not match, excluding bad channels from both
Computing inverse operator with 364 channels.
Created an SSP operator (subspace dimension = 4)
estimated rank (mag + grad): 302
Setting small MEG eigenvalues to zero.
Not doing PCA for MEG.
estimated rank (eeg): 58
Setting small EEG eigenvalues to zero.
Not doing PCA for EEG.
Total rank is 360
Creating the depth weighting matrix...
203 planar channels
limit = 7262/7498 = 10.020865
scale = 2.58122e-08 exp = 0.9
Computing inverse operator with 364 channels.
Creating the source covariance matrix
Applying loose dipole orientations. Loose value of 0.2.
Whitening the forward solution.
Adjusting source covariance matrix.
Computing SVD of whitened and weighted lead field matrix.
largest singular value = 5.96729
scaling factor to adjust the trace = 9.38524e+18
Preparing the inverse operator for use...
Scaled noise and source covariance from nave = 1 to nave = 64
Created the regularized inverter
Created an SSP operator (subspace dimension = 4)
Created the whitener using a full noise covariance matrix (4 small eigenvalues omitted)
Computing noise-normalization factors (dSPM)...
[done]
Picked 364 channels from the data
Computing inverse...
(eigenleads need to be weighted)...
combining the current components...
(dSPM)...
[done]
info["bads"] and noise_cov["bads"] do not match, excluding bad channels from both
Computing inverse operator with 364 channels.
Created an SSP operator (subspace dimension = 4)
estimated rank (mag + grad): 302
Setting small MEG eigenvalues to zero.
Not doing PCA for MEG.
estimated rank (eeg): 58
Setting small EEG eigenvalues to zero.
Not doing PCA for EEG.
Reducing data rank to 360
Total rank is 360
Whitening lead field matrix.
Applying loose dipole orientations. Loose value of 0.2.
Reducing source space to 985 sources
Whitening data matrix.
Using block coordinate descent and active set approach
Iteration 1
Iteration 1
Iteration 2
Iteration 3
Iteration 1
Iteration 1
Iteration 2
Iteration 3
Iteration 4
Iteration 5
Iteration 6
Iteration 7
Iteration 8
Iteration 9
Iteration 10
Iteration 11
Iteration 12
Iteration 13
Iteration 14
Convergence reached !
Iteration 1
Convergence reached !
Debiasing converged after 376 iterations max(|D - D0| = 1.305445e-07 < 1.000000e-06)
4 projection items deactivated
Created an SSP operator (subspace dimension = 4)
4 projection items activated
SSP projectors applied...
0 projection items deactivated
combining the current components...
[done]
View in 2D and 3D (“glass” brain like 3D plot)
plot_sparse_source_estimates(forward['src'], stc, bgcolor=(1, 1, 1),
opacity=0.1, fig_name="TF-MxNE (cond %s)"
% condition, modes=['sphere'], scale_factors=[1.])
time_label = 'TF-MxNE time=%0.2f ms'
clim = dict(kind='value', lims=[10e-9, 15e-9, 20e-9])
brain = stc.plot('sample', 'inflated', 'rh', views='medial',
clim=clim, time_label=time_label, smoothing_steps=5,
subjects_dir=subjects_dir, initial_time=150, time_unit='ms')
brain.add_label("V1", color="yellow", scalar_thresh=.5, borders=True)
brain.add_label("V2", color="red", scalar_thresh=.5, borders=True)
Out:
Total number of active sources: 2
Updating smoothing matrix, be patient..
Smoothing matrix creation, step 1
Smoothing matrix creation, step 2
Smoothing matrix creation, step 3
Smoothing matrix creation, step 4
Smoothing matrix creation, step 5
colormap: fmin=1.00e-08 fmid=1.50e-08 fmax=2.00e-08 transparent=1
Total running time of the script: ( 0 minutes 31.865 seconds)


Hello! My professional skills include designing, engineering, and developing code for safe autonomous vehicles, full-stack distributed applications, and scalable enterprise systems. Below is a showcase of selected work organized into four categories.
Below is feedback I've received on performance reviews from managers and clients:
"Strategic architectural design is the area where James shines the most, he was responsible for the architecture, design, and implementation of a major system (YRM) at the Mirage, where the customer was satisfied with the results." -Walid Abu-hadba, manager
"Quality of work is very high. James does what it takes to satisfy the customer and they ask for him by name." -Mike Kinney, manager
"James' technical skills are unquestionable. He makes it a point to analyze and understand every aspect of a project on which he is working." -Paramesh Vaidyanathan, manager
"The BN.com project has been a phenomenal success, providing significant product feedback (including 30 critical bugs) and increased order processing capacity for the customer. What stands out is that James did this single handedly." -Daryl Wray, manager
"James is truly gifted in analysis, design, and execution." -Microsoft client
"His strongest trait is his high quality work and his attention to detail. Whenever James sets about doing something, you know it will be done right!" -Mike Kinney, manager
"James has a strong ability to illustrate difficult concepts." -Microsoft client
At an early age, I realized an interest in science, mathematics, and technology: I mixed compounds using my chemistry set, explored circuits with a modular electronics kit, and poked at the keys of demonstration calculators in department stores. I was especially fascinated by those that were programmable.
A decisive moment in my life was being admitted to Stuyvesant High School in downtown New York City. It was there that I discovered an IBM computer that students could program. (This was before the PC came along.) The encounter led to learning Fortran and Assembly language, and volunteering as an operator: running jobs and performing supervisory functions.
A few years later, to help make ends meet during college, I secured a part-time job in the shipping department of Arizona State University Bookstore. Ultimately, management recognized they had a computer science major on their team and promoted me to support their inventory management and point-of-sale system.
In this new position, I was responsible for downloading transaction data from a digital tape attached to each cash register and keeping the nightly batch process on track. There were evenings when I would stay late to observe the progression of the many steps in the sequence. Occasionally, the system went off the rails because of a tape machine fault, a process crash, or an excessively long procedure.
The most notable issues occurred during "rush" week at the beginning of each semester when thousands of students need to buy books. At times, the lines at all fifteen cash registers extended deep into the warehouse-sized store. The collective increase in volume of data revealed choke points that needed refinement or re-engineering. To simultaneously optimize transaction processing and maintain the vital daily workflow required careful change planning and lots of testing. Over the course of my tenure, I was able to streamline the system to handle all loads - I could launch the nightly process and go home with confidence that it would complete successfully by the morning.
I ntrospective by nature, I wondered if a computer program could modify itself or be the author of another program. This naturally led to a concentration on artificial intelligence courses including computer vision, robotics, computational linguistics, natural language processing, and expert systems. After graduation, in a research position with Honeywell, I experimented with natural language interfaces to query databases. Using the C language and early versions of Microsoft Windows, I detected similarities between the event-driven programming model and the rule-execution loop of an expert system.
At MicroAge, I was tasked with righting a failed attempt to create a PC-based distributed order entry system. The intent was to eliminate the personnel who, over the phone, manually keyed in orders from franchisees. It was my job to pick up the pieces and deliver a working version within three months. I examined the prior design and identified several programs with many overlapping components. I proposed a completely new architecture which combined all functionality on a Windows-like interface. With some great team-members, we delivered on time.
A few years later, I accepted a position with Microsoft as the third consultant in the Phoenix office. My first assignment was at the colorful Mirage in Las Vegas. Originally planned as a three-week project, the consultation rapidly expanded to diverse projects. Over the next seven years, consulting with customers across the Southwest area, I specialized in database optimization and system architecture.
As Microsoft was shifting focus from the desktop platform to mission-critical enterprise systems, I moved up to Redmond to assist with this transition. I worked with select clients wishing to adopt the latest Microsoft server technologies. One of these customers, Barnes & Noble, was ramping up their online bookstore capacity. Implementing a scaled duplicate of the BN.com order processing data center on campus, I worked with customer developers to improve throughput and other Microsoft engineers to resolve product issues.
After twelve years with Microsoft, I decided to pursue personal interests including music. Eventually, I joined a startup managed by a talented graphic designer. At Motivara, I deliver customized software solutions ranging from interactive presentations to responsive websites.
Presently, I also volunteer my software engineering skills at kynamatrix Research Network. One of the initiatives involves defining a scalable algorithm to assist those left homeless in the aftermath of disaster. An emergency urban environment with service centers and residential areas can more effectively support survivors during the rebuild process. The plan incorporates existing service providers and proposes technology assistance in the form of robotic construction and autonomous systems.
email: jwdunn.scientist at gmail dot com


(#) FrameLayout can be replaced with `` tag
!!! WARNING: FrameLayout can be replaced with `` tag
This is a warning.
Id
: `MergeRootFrame`
Summary
: FrameLayout can be replaced with `` tag
Severity
: Warning
Category
: Performance
Platform
: Android
Vendor
: Android Open Source Project
Feedback
: https://issuetracker.google.com/issues/new?component=192708
Affects
: Kotlin and Java files and resource files
Editing
: This check can *not* run live in the IDE editor
See
: https://android-developers.googleblog.com/2009/03/android-layout-tricks-3-optimize-by.html
Implementation
: [Source Code](https://cs.android.com/android-studio/platform/tools/base/+/mirror-goog-studio-main:lint/libs/lint-checks/src/main/java/com/android/tools/lint/checks/MergeRootFrameLayoutDetector.kt)
Tests
: [Source Code](https://cs.android.com/android-studio/platform/tools/base/+/mirror-goog-studio-main:lint/libs/lint-tests/src/test/java/com/android/tools/lint/checks/MergeRootFrameLayoutDetectorTest.kt)
Copyright Year
: 2011
If a `` is the root of a layout and does not provide
background or padding etc, it can often be replaced with a `` tag
which is slightly more efficient. Note that this depends on context, so
make sure you understand how the `` tag works before proceeding.
(##) Example
Here is an example of lint warnings produced by this check:
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~text
res/layout/simple.xml:1:Warning: This can be replaced with
a tag [MergeRootFrame]
<FrameLayout
^
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Here is the source file referenced above:
`res/layout/simple.xml`:
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~xml linenumbers
<FrameLayout
xmlns:android="http://schemas.android.com/apk/res/android"
android:layout_width="match_parent"
android:layout_height="match_parent" />
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
You can also visit the
[source code](https://cs.android.com/android-studio/platform/tools/base/+/mirror-goog-studio-main:lint/libs/lint-tests/src/test/java/com/android/tools/lint/checks/MergeRootFrameLayoutDetectorTest.kt)
for the unit tests for this check to see additional scenarios.
The above example was automatically extracted from the first unit test
found for this lint check, `MergeRootFrameLayoutDetector.testMergeRefFromJava`.
To report a problem with this extracted sample, visit
https://issuetracker.google.com/issues/new?component=192708.
(##) Suppressing
You can suppress false positives using one of the following mechanisms:
* Using a suppression annotation like this on the enclosing
element:
```kt
// Kotlin
@Suppress("MergeRootFrame")
fun method() {
setContentView(...)
}
```
or
```java
// Java
@SuppressWarnings("MergeRootFrame")
void method() {
setContentView(...);
}
```
* Using a suppression comment like this on the line above:
```kt
//noinspection MergeRootFrame
problematicStatement()
```
* Using a special `lint.xml` file in the source tree which turns off
the check in that folder and any sub folder. A simple file might look
like this:
```xml
<?xml version="1.0" encoding="UTF-8"?>
<lint>
<issue id="MergeRootFrame" severity="ignore" />
</lint>
```
Instead of `ignore` you can also change the severity here, for
example from `error` to `warning`. You can find additional
documentation on how to filter issues by path, regular expression and
so on
[here](https://googlesamples.github.io/android-custom-lint-rules/usage/lintxml.md.html).
* In Gradle projects, using the DSL syntax to configure lint. For
example, you can use something like
```gradle
lintOptions {
disable 'MergeRootFrame'
}
```
In Android projects this should be nested inside an `android { }`
block.
* For manual invocations of `lint`, using the `--ignore` flag:
```
$ lint --ignore MergeRootFrame ...`
```
* Last, but not least, using baselines, as discussed
[here](https://googlesamples.github.io/android-custom-lint-rules/usage/baselines.md.html).


HELLO AND WELCOME TO CONNECTING DOTS
The objective of the game is to connect 4 dots.
New Game
Play Again


Programming language: on building Lisp, falling out of grace and reviving in the JVM ecosystem.
-
Podcasting Pearl #7: On Lisp and Clojure
-
Podcasting Pearl #6: A Conversation with Ronny Kohavi.
Online Experimentation: on trust, best practices and moving the needle.
-
Podcasting Pearl #5: Humor Us.
Psychology: this podcast made me smile.
-
Podcasting Pearl #4: Scale your analytics on the Clickhouse Data Warehouse.
DB engineering: ClickHouse: open-source, column oriented DB engine.
-
Podcasting Pearl #3: The curse of the Black Lotus.
Economics: nurturing bubble markets.
-
Podcasting Pearl #2: Turn big unknowns into focused projects.
Product Management: working on the unknowns, understanding what better means, and building for it.
-
Podcasting Pearl #1: Feature requests aren't demand.
Product Management: deciding what to build, what to prioritize, and what to avoid.


Development Roles
Reusable modules make it possible to divide the application development and deployment process into distinct roles so that different people or companies can perform different parts of the process.
The first two roles, Java EE product provider and tool provider, involve purchasing and installing the Java EE product and tools. After software is purchased and installed, Java EE components can be developed by application component providers, assembled by application assemblers, and deployed by application deployers. In a large organization, each of these roles might be executed by different individuals or teams. This division of labor works because each of the earlier roles outputs a portable file that is the input for a subsequent role. For example, in the application component development phase, an enterprise bean software developer delivers EJB JAR files. In the application assembly role, another developer may combine these EJB JAR files into a Java EE application and save it in an EAR file. In the application deployment role, a system administrator at the customer site uses the EAR file to install the Java EE application into a Java EE server.
The different roles are not always executed by different people. If you work for a small company, for example, or if you are prototyping a sample application, you might perform the tasks in every phase.
Java EE Product Provider
The Java EE product provider is the company that designs and makes available for purchase the Java EE platform APIs and other features defined in the Java EE specification. Product providers are typically application server vendors that implement the Java EE platform according to the Java EE 6 Platform specification.
Tool Provider
The tool provider is the company or person who creates development, assembly, and packaging tools used by component providers, assemblers, and deployers.
Application Component Provider
The application component provider is the company or person who creates web components, enterprise beans, applets, or application clients for use in Java EE applications.
Enterprise Bean Developer
An enterprise bean developer performs the following tasks to deliver an EJB JAR file that contains one or more enterprise beans:
Writes and compiles the source code
Specifies the deployment descriptor (optional)
Packages the .class files and deployment descriptor into the EJB JAR file
Web Component Developer
A web component developer performs the following tasks to deliver a WAR file containing one or more web components:
Writes and compiles servlet source code
Writes JavaServer Faces, JSP, and HTML files
Specifies the deployment descriptor (optional)
Packages the .class, .jsp, and.html files and deployment descriptor into the WAR file
Application Client Developer
An application client developer performs the following tasks to deliver a JAR file containing the application client:
Writes and compiles the source code
Specifies the deployment descriptor for the client (optional)
Packages the .class files and deployment descriptor into the JAR file
Application Assembler
The application assembler is the company or person who receives application modules from component providers and may assemble them into a Java EE application EAR file. The assembler or deployer can edit the deployment descriptor directly or can use tools that correctly add XML tags according to interactive selections.
A software developer performs the following tasks to deliver an EAR file containing the Java EE application:
Assembles EJB JAR and WAR files created in the previous phases into a Java EE application (EAR) file
Specifies the deployment descriptor for the Java EE application (optional)
Verifies that the contents of the EAR file are well formed and comply with the Java EE specification
Application Deployer and Administrator
The application deployer and administrator is the company or person who configures and deploys the Java EE application, administers the computing and networking infrastructure where Java EE applications run, and oversees the runtime environment. Duties include setting transaction controls and security attributes and specifying connections to databases.
During configuration, the deployer follows instructions supplied by the application component provider to resolve external dependencies, specify security settings, and assign transaction attributes. During installation, the deployer moves the application components to the server and generates the container-specific classes and interfaces.
A deployer or system administrator performs the following tasks to install and configure a Java EE application:
Configures the Java EE application for the operational environment
Verifies that the contents of the EAR file are well formed and comply with the Java EE specification
Deploys (installs) the Java EE application EAR file into the Java EE server