Changes between Version 108 and Version 109 of DASISH/XSD and XML

Timestamp:

08/26/13 09:18:00 (11 years ago)

Author:

sroth

Comment:

Added comment regarding issue section: "New-Or-Existing-Source-Info JAXB-generated class"

DASISH/XSD and XML

@@ -554 +554 @@
 It is ok, but it makes code a bit hairy. Can we remove the choice and let the backend todecide if the source is new or old, simply by looking through all the sources
 to find the one with given external-id/uri.  If it is not found then the source is new. 
+[[BR]][[BR]]
+''Stephanie:'' Both Olof and I are somewhat unsure whether it is really necessary to differentiate between new and existing sources when sending POST, PUT, DELETE and GET requests from within the client, especially if the backend implementation is going to be changed to simply check whether the given URI already exists in the DB or not.
+Could you please rethink whether we actually need to keep this concept in the schema document, DASISH-schema.xsd? This decision also has consequences for how the behavior of the client needs to be tuned (cf. [source:DASISH/t5.6/client/trunk/chrome/markingcollection/content/markingcollection/annotator-service/test/mockjax/mocks POST/GET] mock docs named above).
 
 === Resolution ===