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

Sun Feb 16 13:32:16 EST 2020

The model is frozen and should be kept frozen. I don’t plan any changes for the public review release.

Only heavy errors could be a reason to update the model which I don’t expect.

I’m aware of several minor issues. We have to live with these for the public review release. We can include them in a list of issues we are aware of and add the list to the review package.
I can start such a list.

Jay:
In this sense, your examples could be changed that they validate with the XSD bases on the frozen model.

Achim

From: Jay Greenfield [mailto:nightcleaner at gmail.com]
Sent: Sunday, February 16, 2020 18:02
To: A. G.
Cc: Wackerow, Joachim; DDI - Structural Reform Group
Subject: Re: [DDI-SRG] [MRT] DDI-CDI Model

Arofan

Ok

I will wait

Actually if Larry is mindful that all our dataset types inherit from InformationObject when he updates the diagrams, then I am sure I will find the materials I need to update the Architecture, Model Details Description and Examples documents where these diagrams come into play

Recall that InformationObject now inherits from Identifiable but we don’t need to include this class in our diagrams because we don’t want to draw additional attention to a temporary arrangement beyond the “Identifiable” that appears in the InformationObject class

In the meantime I will send you draft versions of the three documents so you can assess what we are using and need in the way of diagrams and coordinate with Larry

Jay

Sent from my iPhone

Jay Greenfield
202.271.3179

On Feb 16, 2020, at 10:31 AM, A. G. <ilg21 at yahoo.com> wrote:

Jay:

Please be aware that Larry is updating diagrams in the Data Description portion of the model this weekend, so any changes you make will have to be merged with what he is doing, a thing which I cannot accomplish. Could you wait to look at what he has done. I will check with him tomorrow and see where he is with this. I am not sure how much he could get done without a frozen model, although I know he was looking at this.

Cheers,

Arofan

On Sunday, February 16, 2020, 10:27:12 AM EST, Jay Greenfield <nightcleaner at gmail.com> wrote:

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<mailto: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

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/

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

_______________________________________________
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
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.icpsr.umich.edu/pipermail/ddi-srg/attachments/20200216/72e756c4/attachment-0001.html 