[Digir-cvs] SF.net SVN: digir: [406] tapirlink/trunk/README.txt

[<rd...@us...>]

Revision: 406
          http://digir.svn.sourceforge.net/digir/?rev=406&view=rev
Author:   rdg
Date:     2007-07-22 14:23:45 -0700 (Sun, 22 Jul 2007)

Log Message:
-----------
Adjustments in documentation.

Modified Paths:
--------------
    tapirlink/trunk/README.txt

Modified: tapirlink/trunk/README.txt
===================================================================
--- tapirlink/trunk/README.txt	2007-07-19 02:37:10 UTC (rev 405)
+++ tapirlink/trunk/README.txt	2007-07-22 21:23:45 UTC (rev 406)
@@ -49,8 +49,8 @@
 Although TapirLink is based on the DiGIR PHP provider, it is
 NOT compatible with the DiGIR protocol. TapirLink is only 
 compatible with the TAPIR protocol (version 1.0 of the 
-protocol, as specified in 
-http://www.tdwg.org/dav/subgroups/tapir/1.0/docs/).
+protocol, as specified at: 
+http://www.tdwg.org/activities/tapir/specification/
 
 A single instance of TapirLink can provide access to multiple 
 TAPIR resources, each one with its own address. After 
@@ -70,33 +70,30 @@
 
 http://example.net/tapirlink/tapir.php/myres/
 
-TapirLink can only map conceptual schemas that follow the 
-DarwinCore pattern: concepts are defined as global elements 
+TapirLink can map conceptual schemas that either follow the 
+DarwinCore pattern or the CNS configuration file pattern. In the
+DarwinCore pattern, concepts are defined as global elements 
 of an XML Schema document having a "substitutionGroup" attribute 
 referencing dwe:dwElement (where "dwe" is a prefix for the 
 namespace "http://rs.tdwg.org/dwc/dwelement"). Please note that 
 this is NOT the original format of DarwinCore. It comes from 
-a more recent version.
+a more recent version of the schema. 
 
 TapirLink allows each resource to map one or more conceptual 
-schemas following the DarwinCore pattern. But the idea is that 
-it will only be able to serve instances of a single "class" or 
-"entity". In other words, when mapping multiple conceptual 
-schemas, each mapped concept will actually refer to an 
-"attribute" or "property" of the same underlying class.
+schemas, but it will only be able to serve instances of a single 
+"class" or "entity". In other words, when mapping multiple 
+conceptual schemas, each mapped concept will actually refer to an 
+"attribute" or "property" of the same underlying class. In search 
+responses, instances of that class will be bound to instances of 
+the "indexingElement" defined in the output model.
 
-In search responses, instances of that class will be bound 
-to instances of the "indexingElement" defined in the output 
-model.
+This means that TapirLink has limited use with response structures 
+that relate instances of different classes, for example multiple 
+specimens, each one with multiple identifications. However, in 
+these cases sometimes it is possible to use fixed value mappings,
+especially when response structures include metadata elements 
+(for example "collection code") enclosing all instances of a class.
 
-This means that you cannot use TapirLink if you want to get back 
-response structures relating instances of different classes, 
-for example multiple specimens, each one with multiple 
-identifications. However, you can get back response structures 
-that include metadata elements enclosing all instances of a class. 
-Metadata concepts (for example "collection code"), when mapped 
-to a fixed value can be used in these cases.
-
 FEATURES
 ========
 
@@ -112,11 +109,11 @@
 * Log only requests can be accepted.
 * Complete filter parsing. "Equals" and "like" can be case sensitive 
   or not.
-* Max element repetitions and max element levels.
+* Max element repetitions and max element levels settings.
 * Multiple resources can be exposed from a single TapirLink instance.
 * Each resource can map one or more conceptual schemas based on the 
-  new DarwinCore pattern.
-* User-friendly web configuration interface including a UDDI 
+  new DarwinCore pattern or the CNS configuration file format.
+* User-friendly Web configuration interface including a UDDI 
   registration form and the possibility to import DiGIR configuration.
 * A simple client for testing.
 * An LSID authority resolver (see: www/lsid-authority/readme.html)
@@ -124,8 +121,9 @@
 LIMITATIONS
 ===========
 
-* Any XML Schema used as a response structure should not redeclare the same prefix
-  or the same namespace more than once.
+* Any XML Schema used as a response structure should not include or 
+  import other schemas that redeclare the same prefix and associate
+  it with a different namespace.
 
 INSTALLATION
 ============


This was sent by the SourceForge.net collaborative development platform, the world's largest Open Source development site.