Changes between Version 5 and Version 6 of Setting_Schema_Location


Ignore:
Timestamp:
Jul 25, 2012, 2:12:31 PM (12 years ago)
Author:
Klaus Thoden
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • Setting_Schema_Location

    v5 v6  
    1 According to the [http://www.thaiopensource.com/relaxng/design.html#section:17 documentation of Relax NG], there is no way of telling a document the location of the Relax NG Schema as it is possible with a DTD. As our main editor at the moment is [http://www.oxygenxml.com oxygen], either a processing instruction has to be entered into the xml-file, or a validation scenario has to be entered into oxygen (via Dokument > Validieren > Konfiguriere Validierungsszenario).
     1According to the [http://www.thaiopensource.com/relaxng/design.html#section:17 documentation of Relax NG], there is no way of telling a document the location of the Relax NG Schema as it is possible with a DTD.
    22
    3 In order to keep things clean and not confuse the user with relative paths to a local copy, a link to the Relax NG schema on this server can be entered. However, as this server can be reached only via https, oxygen itself has to be configured to accept a secure connection.
     3In order to keep things clean and not confuse the user with relative paths to a local copy, a link to the Relax NG schema on this server can be entered. The stable version is situated at
     4{{{
     5https://it-dev.mpiwg-berlin.mpg.de/svn/mpdl-project-content/trunk/schema/schema/echo/echo.rnc
     6}}}
     7
     8However, as this server can be reached only via https, the validators themselves have to be configured to accept a secure connection.
     9
     10== Oxygen ==
     11
     12As our main editor at the moment is [http://www.oxygenxml.com oxygen], either a processing instruction has to be entered into the xml-file, or a validation scenario has to be entered into oxygen (via Dokument > Validieren > Konfiguriere Validierungsszenario).
    413
    514For this purpose, the SSL certificate of the it-dev server has to be downloaded (attached is a PEM-encoded version, see [http://www.gtopia.org/blog/2010/02/der-vs-crt-vs-cer-vs-pem-certificates/ this blog entry] on how to display and convert that file) and stored in the Java keystore. On Mac OS, this can be done via Keychain (Schlüsselbundverwaltung).
     
    1120
    1221
    13 You can also paste the following snippet directly into the {{{Info.plist}}} (in Java/Properties)
     22You can also paste the following snippet directly into the {{{Info.plist}}} (in !Java/Properties)
    1423{{{
    1524                        <key>javax.net.ssl.trustStoreProvider</key>
     
    2130Note that the {{{Info.plist}}} file is overwritten with every update of Oxygen.
    2231
    23 The link to the latest version of the schema root is {{{https://it-dev.mpiwg-berlin.mpg.de/svn/mpdl-project-content/trunk/schema/schema/echo/echo.rnc}}}
     32== Jing (Command line) ==
     33When using Jing, the common keystore of the Java Virtual Machine is used. It might be adviseable to build an own keystore which contains only the certificate of above server:
    2434
     35{{{
     36keytool -import -file it-dev.mpiwg-berlin.mpg.de.crt -keystore itdev.keystore
     37}}}
    2538
    26 Fingerprints of the key:
     39A password (at least 6 characters) has to be entered and confirmed.
     40
     41The command
     42{{{
     43java -Djavax.net.ssl.trustStore=itdev.keystore -Djavax.net.ssl.trustStorePassword=<password> -jar $ECHO_SCRIPTS_DIR/share/thirdparty/jing-20091111/bin/jing.jar -c https://it-dev.mpiwg-berlin.mpg.de/svn/mpdl-project-content/trunk/schema/schema/echo/echo.rnc <textfile.xml>
     44}}}
     45
     46== Fingerprints of the key ==
    2747
    2848SHA1: {{{FA 59 20 79 0E 28 80 18 CA 2D 00 F1 B2 18 EA B7 00 F1 51 BE}}}