Missing 3.3 elements with extension base Reference

[wlthomas]

19 occurrences of elements which extended a basic reference were not transferred in original input to 4.0. This was noted during the TC review but was not corrected. The attached file lists all instances. These are described in detail on the comparison spreadsheet at https://ddi-alliance.atlassian.net/wiki/spaces/DDI4/pages/3048439811/DDI-L+4.0+BETA+-+Review+Information#%5BmediaInline%5D

See sheet RED-extended reference

ListOfMissingExtendedReference_from_3-3.txt

[wlthomas]

We are not going to extend references it should be moved up with additional information. Wendy go back and see what was discussed. Also check on the continued need for each of these and then determine how to fix this in the simplest way.

[wlthomas]

I have attached a spreadsheet listing the 19 extended reference types with their contents and suggested approaches. Some extensions are tightly tied to the item referenced, in other cases sets of references could be grouped under types. I still need to located and add references to earlier discussions. IssueDetails_No36.xlsx

[wlthomas]

Notes from TC meeting 2024-03-21 Should be addressed in 4.0 BETA 2 Add additional notes on previous discussions Group instances to see what could be managed in the same way

[wlthomas]

FROM TC minutes 2022-02-19 Reference:

Reference properties outside of the identification is the issue

Reference is an entity and will act differently with serialization - RDF is a URI, XML / JSON model

Review specifics of properties - Wendy will document

Example: Where you need to know a context of what you are referencing add another reference for context.

Including extra properties

Option is to create Complex types

Reference becomes an element in the complex

Where is such extended content needed