Changes between Version 101 and Version 102 of DASISH/XSD and XML

Timestamp:

08/20/13 08:17:49 (11 years ago)

Author:

olhsha

Comment:

--

DASISH/XSD and XML

@@ -526 +526 @@
 be replaced when the schema is updated."
 
+=== Resolution ===
+
+Not discussed yet. 
+
 == New-Or-Existing-Source-Info JAXB-generated class ==
 
@@ -534 +538 @@
 to find the one with given external-id/uri.  If it is not found then the source is new. 
 
+=== Resolution ===
+
+The schema stays intact.  For the backend-code: the server should check if the source is indeed new, see  https://trac.clarin.eu/ticket/362 for more detail.
+
 
 ==    External_id (Data Base) vs URI (schema) vs UUID-based class (Java code) ==
@@ -542 +550 @@
 encapsulating  UUI.  Any such class  has a string field "identifier" (corresponding to external_id) plus hash, plus internal constants for hash.
 
+=== Resolution ===
+
+The schema stays intact. For the back-end code: the URI must be of the form  "http(s):/<dasish-server>/externalID.  See https://trac.clarin.eu/ticket/363 for more detail.
+
+ UUI-based classes are used to generate proper UUID-string representing the external identifier of a resource. The role of hash-functions must be  discussed with the Peter,
 
 == Body: must be some serialization/deserialization mechanism ==
@@ -549 +562 @@
 -- "body" in JAXB-generated  class is a list of objects
 
-For now, I use simple "serialize" and "deserialize" Helpers' procedures  which should be replaced by
-some proper marshalling-demarshalling. For simple serialization I treat the first element of the list
-of objects above  as a text  whcich corresponds to the DB column "body_xml"
+For now, I use simple "serialize" and "deserialize" Helpers' procedures  which should be replaced by some proper marshalling-demarshalling. For simple serialization I treat the first element of the list
+of objects above  as a text  whcich corresponds to the DB column "body_xml".
+
+=== Resolution ===
+
+The schema  stays intact. For the back-end code: still needs to be discussed "how we are going to parse annotation bodies". See https://trac.clarin.eu/ticket/364 for more detail.
 
 
@@ -557 +573 @@
 
 Misprint in timeStamp: timeSatmp.
+
+=== Resolution ===
+
+The schema must be fixed.  See https://trac.clarin.eu/ticket/365
 
 == Cached Representation Info ==
@@ -564 +584 @@
 
 GET api/sources/<sid>/cached/<cid>/content
+
+=== Resolution ===
+
+The schema stays intact. For the back-end (and the database!):  the cached representation for now should be stored in the database
+as a BLOB. See:http://dba.stackexchange.com/questions/803/blobs-or-references-in-postgresql/815#815. 
+
+Also, see https://trac.clarin.eu/ticket/366
+
 
 == Version ==
@@ -581 +609 @@
 class "Version". 
 
+=== Resolution ===
+
+Fix the schema: URI must be added to the version-type. The ticket: https://trac.clarin.eu/ticket/367
 
 ==  LISTS of Resources, like "PermissionS" and "CachedRepresentationS",