Changes between Version 115 and Version 116 of DASISH/XSD and XML


Ignore:
Timestamp:
08/26/13 15:28:29 (11 years ago)
Author:
olhsha
Comment:

--

Legend:

Unmodified
Added
Removed
Modified

  • DASISH/XSD and XML

    v115 v116  
    543543As regards all future schema updates, please make sure to remember to update all available scenario xml documents on trac.clarin.eu accordingly, and preferably, with as little delay as possible. It might also be a good idea to validate all of these documents against the revised schema with a reliable XML parser like e.g. the Xerces-J XML parser. Also, if you like, you can check by validating some of our current "real-life" mock xml documents that we have been using recently for client development ([source:DASISH/t5.6/client/trunk/chrome/markingcollection/content/markingcollection/annotator-service/test/mockjax/mocks]).
    544544
    545 Olha: sure. We have not make any changes yet (before getting you opinion). Unfortunately, I will be away 27/08 - 14/09 due to urgent family circumstances. I hope that we can wait till I'm back.
     545''Olha'': sure. We have not make any changes yet (before getting you opinion). Unfortunately, I will be away 27/08 - 14/09 due to urgent family circumstances. I hope that we can wait till I'm back.
    546546
    547547=== Resolution ===
    … …  
    562562Could 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).
    563563
    564 Olha: we agree with you. See resolution below.
     564''Olha'': we agree with you. See resolution below.
    565565
    566566=== Resolution ===
    … …  
    578578''Stephanie:'' Apropos this subject, could you please clarify whether you intend to use "external-id (Ticket #362: externalID, see even discussion topic above)" for the database only? You use the wording "For the time being", which made us wonder whether the statement "URI is external_id" will be true even in the longer perspective, or, if not, where / how the externalID is going to be put in from the schema side, an thus within the context of the resulting, serialized xml documents? Furthermore, why is the nomenclature "external_id" used? Won't the value of URI always be an internal id, like e.g. http://dasish.eu/annotations/AID20130808114716, that needs to be created and set via a corresponding backend functionality?
    579579
    580 Olha: The term "external_id"  comes from the Data Base  and is used for communication with the client.  It is a string which satisfies UUID-format, e.g. "00000000-0000-0000-0000-000000000003". The URI in the xsd is of the form  like you mentioned above  e.g. http://dasish.eu/annotations/00000000-0000-0000-0000-000000000003. An external Id is generated by the backend whenever a resource is recognized as new in the  corresponding "add"-method. It is sent to the client as a respond to the "Add" request.
     580''Olha'': The term "external_id"  comes from the Data Base  and is used for communication with the client.  It is a string which satisfies UUID-format, e.g. "00000000-0000-0000-0000-000000000003". The URI in the xsd is of the form  like you mentioned above  e.g. http://dasish.eu/annotations/00000000-0000-0000-0000-000000000003. An external Id is generated by the backend whenever a resource is recognized as new in the  corresponding "add"-method. It is sent to the client as a respond to the "Add" request.
    581581
    582582 "Internal_id" in the database is not visible to a client.  It is "next-in-the-table"  number generated by the database whenever the corresponding resource is added. It is a primary key of the resource. It is used for joint tables (e.g. when you connect an annotation to a source) and for quick search by key, since it is just a number, not a string.
    … …  
    610610
    611611
    612 Olha: Yes it will be replaced. t. When I wrote the code I needed some quick solution that would provide me with the serialized version. Once we decide to use Marchaller and Unmarchaller, I will remove helpers. 
     612''Olha'': Yes it will be replaced. t. When I wrote the code I needed some quick solution that would provide me with the serialized version. Once we decide to use Marchaller and Unmarchaller, I will remove helpers. 
    613613
    614614== Source ==
    … …  
    674674''Stephanie:'' When removing the URI attribute for lists of resources, please make sure that the integrity of the references is still guaranteed.
    675675
    676 Olha: lists are not stored in the DB but generated by the backend on the fly when they are needed. For instance, once the client want to GET an annotation (which schema contains the lists of source-infos), the backend looks up a joint table "annotations_resources" and the table "source"  and  generate a list of resources for the annotation.
     676''Olha'': lists are not stored in the DB but generated by the backend on the fly when they are needed. For instance, once the client want to GET an annotation (which schema contains the lists of source-infos), the backend looks up a joint table "annotations_resources" and the table "source"  and  generate a list of resources for the annotation.
    677677