ATTENDEES: Wendy, Jon, Jay, Dan G., Oliver, Larry
DMT-105 - Document needs final comment (will request via list)
- Discussed locations where relationship targets are pattern classes as this is not allowed in rules
- Raised the question of how to address the ability to link basic or descriptive or overview realizations to more specific pattern based classes as a specific extention of the metadata (adding later additional detail within a view or to detailed metadata external to the view).
Both specific issues and general approaches were discussed. The following are comments from the discussion in the order they appeared. They have been labeled to facilitate the work of DMT-120 in preparation for the IASSIST Sprint - Specific issues:
- Do we need a high level ProcessOverview similar to that done for Methodology?
General Issue Description: - We have a lot of the mechanics in place regarding patterns
- We've said that 105 is related to 67 where we want to describe how to use patterns to do more specific things
- This document should come before the actual gap analysis and work
- Jay is hoping to get to 67 this weekend - can go on agenda for next week
Possible approach: - Use of some of the overview types as extension bases?
- If we do that we could be giving people too many options of doing it the wrong way
- We want them to describe them in the same way therefore specific realizations of patterns
- Issues of semantic interoperability
Use cases: - Scenario where we want to take basic metadata and extend it
Possible approach: - We've thought about a controlled vocabulary for the high level descriptions of methodology - to identify which kind of description this is like a "subject" of methodology
- One way would be when we have a specific model that expands on a specific methodology - add a pointer to a specific instance of a detailed methodology
Specific issue: - What is the role of external material? Can we separate the pointer from external to internal. Should external be a pointer to non-DDI and therefore be renamed?
- Rather have more precision in terms of the target of the pointer DDI-Views model content, other versions of DDI should be considered external with examples of how to specify that the information is in a specific format other than that of the instance (i.e. DDI-Views)
Future work: - Prepare some use cases of these situations for Codebook, taking that basic information and extending into a different view which provides depth, or other specifics, can we provide a reference from a more general one to a more detailed one. Also layout a number of approaches to test use cases against. Do for IASSIST Sprint.
- We have some ideas but need to fill them out.
General Issue Description: - With the high level descriptions we created kind of an island and can't put things together in a continuous way. We need to go back to how we did what we did that doesn't create an island.
Ideas for unification: - Adding a specific type pointers - how to avoid malicious compliance.
- Use of non-pattern extension bases - yet avoid chaos
- A typing way of providing the specific link (i.e. if type="Sampling" target must be "SamplingPattern")
TO DO: File an issue as prep for IASSIST Sprint to get issue described, ideas for unification, and use cases so we can validate approaches against use cases, determine approach and fine tune at sprint. - DMT-120
TO DO: Create JIRA issue regarding documentation and possible renaming of ExternalMaterial DMT-121
TO DO: Set up another Tools Group meeting (Wendy will talk to Oliver about agenda items, what's needed)
FUTURE AGENDAS: - DAN will try to finish his items for 2 weeks. (Probably unable to attend next week)
- WENDY will get some things done for next week.
- JAY will try to have DMT-67 prepared for next week.
Agenda item for IASSIST Sprint for MT: - Qualitative - general review of modeling structure to update to current modeling decisions, this is a modeling review not as much a business content review
- Unification from pattern to general realizations to specific realizations
|