Changes between Version 96 and Version 97 of DASISH/XSD and XML

Timestamp:

08/19/13 08:05:00 (11 years ago)

Author:

olhsha

Comment:

--

DASISH/XSD and XML

@@ -512 +512 @@
 
  {{{GET api/annotations?link="http://en.wikipedia.org/wiki/Sagrada_Fam%C3%ADlia"&access=read}}}.
+
+
+= Issues with the schema =
+== Possible namespace pollution: Ticket 348 to be discussed with Peter  ==
+
+Peter: 
+"It looks like there might be some namespace pollution or some other anomaly that causes the jaxb a
+uto generated classes to omit the getter for notebooks from the ObjectFactory. This is an issue 
+when a jaxb root node is required, such as in the rest interface. A work around has been added 
+which makes it clear where the issue is and why the ObjectFactory is required, but this needs to 
+be replaced when the schema is updated."
+
+
+==    External_id (DataBase) vs URI (schema) vs UUID-based class (Java code) ==
+
+For the time being I treat them as "the same":  URI is external_id. Both are strings.
+
+Moreover, there is a class "DasishIdentifier" (with a bunch of superclasses, for each reasoure),
+extending UUI. It "envelopes" external_id" into UUID.
+
+
+== Body: must be some serialization/deserialization mechanism ==
+
+-- "body" in the DB it is just a text
+-- "body" in schema-generated class it 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"
+
+
+== Source ==
+
+Misprint in timeStamp: timeSatmp.
+
+
+
+== Cached Representation Info ==
+
+Missing in the schema: the attribute/elememt "where_is_the_file" which actually points to the location 
+where the file can be download. It is necessary to fulfill  
+
+GET api/sources/<sid>/cached/<cid>/content
+
+== Version ==
+
+MISSING in the schema:  attribute URI (corresponding to the external_id in the DB) is absent. Therefore it does not appear 
+in the  JAXB-generated class "Version" and the java class has one attribute less than the DB table "version"
+
+{{{
+CREATE TABLE version (
+    version_id SERIAL UNIQUE NOT NULL,
+    external_id UUID UNIQUE NOT NULL,
+    version text,
+);
+}}}
+
+For now I'm using attrribute "version:String" now to keep "external_id/URI" in the java 
+class "Version". 
+
+
+==  LISTS of Resources, like "PermissionS" and "CachedRepresentationS", 
+and version-siblingS connected to a particular source
+cannot be standalone tables in the relational DB ==
+
+According to the schema: a list of Cached representations is declared as a standalone resource 
+of type "CachedRepresentations". Every version referres to its own list of cached representations. 
+Every such list has it own ID.
+
+According to the Rel. database: it looks a bit strange to have such lists. Instead, i have made 
+a common joint table (verson_id, cached_representation_id). A pair (a, b) is listed in this table iff 
+the version with  the internal id "a" has cahced representation with intrenal id "b".