[DDI-SRG] [MRT] DDI-CDI Model

[Jay Greenfield]

Achim:

I suggest you don’t change any of the string types. At this point that would invalidate ALL the examples I developed in a big way and perhaps ones that Larry and others have developed too.

Mostly the new model and XSD you produced from it passes regression testing. There is, however, one problem introduced when we moved InformationObject from the Process package to the DataDescription package. As a result one of my examples now won’t validate against the XSD. I have a workaround in the event the model remains frozen. Alternatively, I can test a possible fix on my copy of the current model and you can apply it if the model becomes unfrozen.

Because of this change in the location of InformationObject and because of a number of changes I introduced into the process model, it would be good to update two or three diagrams across Process and DataDescription. I can update the diagrams on my copy of the current model as you suggest below. Is that OK?

Finally, because the DDI-CDI namespace was changed, a bunch of the headers in the example XMLs needed to be changed too. Do we consider the namespace to be settled now? It is:

<DDI xmlns="http://ddialliance.org/Specification/DDI-CDI/XSD/"


Jay

On Feb 16, 2020, at 9:08 AM, Wackerow, Joachim <Joachim.Wackerow at gesis.org> wrote:

The model is now frozen; version is 2020-02-16.
 
All the next tasks should be based on this version.
 
Please review the change log file for the changes and review the model for any errors.
 
Hilde will use now the master file DDI-CDI_PublicReviewRelease_2020-02-16.eap to update the documentation. Please notice that it is not possible to make any changes to the model while this task.
I can make only very urgent changes after this step.
Then, I can also include diagram folders into the master EA file, if people provide me copies of their EA files.
 
The 2020-02-16 files are available at: https://drive.google.com/drive/folders/1iy2OpMkMfTx6xuw7BubZIPHxvFVsMGKZ <https://drive.google.com/drive/folders/1iy2OpMkMfTx6xuw7BubZIPHxvFVsMGKZ>
 
I put now following model identification into the model itself as constants (DDICDI-DataTypes-ModelIdentification):
·        acronym : String [1] = DDI-CDI
·        majorVersion : Integer [1] = 0
·        minorVersion : Integer [1] = 5
·        subtitle : String [1] = Public Review Release 2020-03
·        title : String [1] = DDI - Cross-Domain Integration
·        uri : String [1] = http://ddialliance.org/Specification/DDI-CDI/ <http://ddialliance.org/Specification/DDI-CDI/>
 
The URI is used as prefix for the UUIDs in the Canonical XMI.
 
I didn’t have time enough to simplify the various string types.
 
I run into an EA issue regarding assigning types to attributes. I wanted to assign a string instead of ValueString to some attributes. EA shows the change, but the exported XMI doesn’t. Only the search type dialog shows in some vague way that the type is not changed. It is necessary to delete the attribute, to create a new one, and to assign a string. I will explore the issue more later. It seems to be only related to the string type.
 
Achim
_______________________________________________
DDI-SRG mailing list
DDI-SRG at icpsr.umich.edu <mailto:DDI-SRG at icpsr.umich.edu>
http://lists.icpsr.umich.edu/mailman/listinfo/ddi-srg <http://lists.icpsr.umich.edu/mailman/listinfo/ddi-srg>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.icpsr.umich.edu/pipermail/ddi-srg/attachments/20200216/dd8ec1c2/attachment-0001.html