Changes between Version 111 and Version 112 of DASISH/XSD and XML


Ignore:
Timestamp:
08/26/13 11:16:33 (11 years ago)
Author:
sroth
Comment:

Update of comment.

Legend:

Unmodified
Added
Removed
Modified
  • DASISH/XSD and XML

    v111 v112  
    570570encapsulating  UUI.  Any such class  has a string field "identifier" (corresponding to external_id) plus hash, plus internal constants for hash.
    571571[[BR]][[BR]]
    572 ''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, i.e. within the context of the resulting, serialized xml documents?
     572''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?
    573573
    574574=== Resolution ===