From: Adam Dickmeiss Date: Mon, 19 Apr 2004 13:43:44 +0000 (+0000) Subject: Prepare examples. More info on syntax rules X-Git-Tag: YAZPROXY.0.8~10 X-Git-Url: http://jsfdemo.indexdata.com/cgi-bin?a=commitdiff_plain;h=a654dca0f59fd27228816703c8bb959f2970ca4e;p=yazproxy-moved-to-github.git Prepare examples. More info on syntax rules --- diff --git a/doc/reference.xml b/doc/reference.xml index 15274ea..2bd922d 100644 --- a/doc/reference.xml +++ b/doc/reference.xml @@ -117,14 +117,16 @@ Proxy Configuration Header The proxy config file must have a root element called - proxy. All information except an optional XML - header must be stored within the proxy element. + proxy and scoped within namespace + xmlns="http://indexdata.dk/yazproxy/schema/0.8/. + All information except an optional XML header must be stored + within the proxy element. <?xml version="1.0"?> - <proxy> - <!-- content here .. --> - </proxy> + <proxy xmlns="http://indexdata.dk/yazproxy/schema/0.8/"> + <!-- content here .. --> + </proxy>
@@ -142,7 +144,7 @@ <?xml version="1.0"?> - <proxy> + <proxy xmlns="http://indexdata.dk/yazproxy/schema/0.8/"> <target name="server1" default="1"> <!-- description of server1 .. --> </target> @@ -306,19 +308,6 @@
- - -
syntax @@ -344,18 +333,55 @@ type should be XML. The proxy will use preferred record syntax USMARC/MARC21 against the backend target. - To accept USMARC and offer MARCXML XML records but reject - all other requests the following configuration could be used: - - <proxy> + + If attribute stylesheet is given, the proxy + will convert XML record from server via XSLT. It is important + that the content from server is XML. If used in conjunction with + attribute marcxml the MARC to MARCXML conversion + takes place before the XSLT conversion takes place. + + + If attribute identifier is given that is the + SRW/SRU record schema identifier for the resulting output record (after + MARCXML and/or XSLT conversion). + + + If sub element title is given (as child element + of syntax, then that is the official SRW/SRU + name of the resulting record schema. + + + If sub element name is given that is an alias + for the record schema identifier. Multiple names + may be specified. + + + MARCXML conversion + To accept USMARC and offer MARCXML XML plus Dublin Core (via + XSLT conversion) but the following configuration could be used: + + <proxy> <target name="mytarget"> + .. <syntax type="usmarc"/> - <syntax type="xml" marcxml="1"/> - <syntax type="*" error="238"/> + <syntax type="xml" marcxml="1" + identifier="info:srw/schema/1/marcxml-v1.1" + <title>MARCXML<title> + <name>marcxml<name> + <syntax> + <syntax type="xml" marcxml="1" stylesheet="MARC21slim2SRWDC.xsl" + identifier="info:srw/schema/1/dc-v1.1"> + <title>Dublin Core<title> + <name>dc<name> + <syntax> + <syntax type="*" error="238"/> + .. </target> - </proxy> - + </proxy> + + +
diff --git a/doc/using.xml b/doc/using.xml index f6106f8..d6ed178 100644 --- a/doc/using.xml +++ b/doc/using.xml @@ -25,7 +25,7 @@ except any log files you ask for. - + Using the Proxy to Log APDUs Suppose you use a commercial Z39.50 client for which you do not @@ -126,6 +126,21 @@ ]]> + + + Exposing a Z39.50 server behind a firewall + + .. + + + + + Offering SRW/SRU/Z39.50 service + + .. + + +