Removed command.c (telnet-style interface)

[pazpar2-moved-to-github.git] / etc / pazpar2.cfg

diff --git a/etc/pazpar2.cfg b/etc/pazpar2.cfg
index da8e9c7..3ccbda5 100644 (file)
--- a/etc/pazpar2.cfg
+++ b/etc/pazpar2.cfg
@@ -1,21 +1,28 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<pazpar2 xmlns="http://www.indexdata.com/pazpar2/1.0">
+<?xml version="1.0" encoding="UTF-8"?> <pazpar2 xmlns="http://www.indexdata.com/pazpar2/1.0">
 
 <!-- NOTE: This is not yet a functional config file. It's meant as a scratchpad/
      discussion area to figure out just how the heck to structure this kind of
      configuration.
 -->
 
-<service>
-    <listen port="9004"/>
-    <proxy host="localhost" port="80"/>
-</service>
+<server>
+  <listen port="9004"/>
+  <proxy host="localhost" port="80"/>
+
+  <service>
+    <!-- <metadata name="title"/> -->
+  </service>
+</server>
 
 <!-- Need to figure out where to get ZeeRex records for targets from -->
 
-<queryprofile/>  <!-- Like a CCL profile? Or do these need to be 
-                       dynamically generated from Zeerex??  -->
+<queryprofile/>  <!-- Like a CCL profile++ . Can optionally refer to XSLT to 
+       convert ZeeRex into queryprofile. Multiple profiles can exist.  -->
 
-<retrievalprofile/>   <!-- Specify what stylesheets to use to normalize records?? -->
+<retrievalprofile>
+  <requestsyntax>marc21</requestsyntax>
+  <nativesyntax name="iso2709" format="marc21" encoding="marc-8" mapto="marcxml"/>
+  <map type="xslt" stylesheet="marc21.xsl"/>
+</retrievalprofile>
 
 </pazpar2>