Page History

page-info

:title}

h2. Pre Interview:

|| Item || Information/Response ||
| {color:#000000}{*}Date{*}{color}{color:#000000}: {color} | 12/18/2009

 |
| {color:#000000}{*}Requirement # unique id{*}{color} _<SemCon Ops Initiative>.<analysts initials><requirement number>

_ \\
e.g. Init1dbw1

 \\
(eventually linked to Use Cases) | Init1pm12 |
| *Originator/Customer's Name*:

 | [Hannes Niedner|mailto:hannes@sdsc.edu] \- [forum

 posting|https://cabig-kc.nci.nih.gov/Vocab/forums/viewtopic.php?f=43&t=111]\\ |
| *Originator/Customer's Company*:

 | San Diego Supercomputer

 Center \\ |
| *Summary of requirement pre-interview, by Reviewer:

* | It appears that the current construct of the CDE carries too many dependencies that make it hard to adopt (by parties other than the author).

  For this, and other reasons, there is a proliferation of difficult to reuse CDEs.

  One possible solution could be by expressing the ValueDomain as either XSD, RDF or OWL, then it would be much easier to reuse existing CDEs since one apply "runtime semantics" controlled by the adopters.

  Another option is to distribute the metadata repositories across organizations, allowing Information Technologists to create and annotate their own metadata.

  This issue has been discussed at length, and attached are some supporting documents.

 \\ |
| *Recommended Next Step* Enter one: Follow-up interview, Observe, Use Case Template (text), Use Case Model (formalized/UML diagram), Group Discussion, Prototype, Waiting Room

 | Followup

 interview \\ |
\\
{scrollbar:icons=false}