is
exactly counter to *the* core goal for any ontology.
Hard or easy, the utility gained fully merits its costs.
best regards,
Dan Corwin
Kashyap, Vipul wrote:
Physical vrs Informational
Natural vrs Artificial
Real vrs Imaginary
Composite vrs Characteristic
Individual vrs
any class or instance
desired.
Perhaps the specific discriminants listed above could help in more
precisely discussing the less-general (domain-specific) layers of your
strawman, or the benefits of distinguishing them.
Best regards,
Dan Corwin
s "Assessment"
(like the ones found in the above paper); (3) build on top of that
foundation, *separately* for each of SOAP's four disjoint aspects.
regards,
Dan Corwin
Ogbuji, Chimezie wrote:
Thanks for that drill down, Tom. It gives a good backdrop to call out
important d
ises my own ambitions
for a POC, and for similar COI use cases it may support.
Next steps for any POC design should be critical reviews that
seek ways to improve or simplify it. Please email feedback on
these or related "architecture" thoughts to the list. Thanks.
best regards,
Dan Corwin
Vipul -
Sorry I missed today's TC. Here is more feedback on the project
plan, continuing the thread I began last night ...
DC>> Your project plan handles "patient recruitment" only if you assume
that patient records are in DCM and protocol requests come in SDTM.
Neither assumption is valid, s
designs before going any further on enumerating tasks.
In 6-9 months, given clear designs, any small part-time group can
easily create all we need to properly demo our full use case, and
*also* illustrate general-purpose COI models. It would be a shame
to blow that opportunity by defining group work tasks prematurely.
regards,
Dan Corwin
Kashyap, Vipul wrote:
[DC] I've been exploring designs that can implement your spreadsheet
rows as a web service of "predicates" helpful to achieving this.
The simplest design [1] just wraps a shell of customized JSPs
that can make such mappings around any working EMR system.
[VK] Yes, this c
Agents" under BIONTDSEDCM Use Case Scenarios
I'd like to discuss both in Tuesday's telcon, as proposals for
the F2F brainstorming session about next steps. Questions and
feedback coming first by email from the group would be welcome.
best regards,
Dan Corwin
Kashyap, Vipul wro
are better
known. Use Case specs are nice, but debating Requirements
is often a more productive way to expose them.
Cheers,
Dan Corwin
Rachel Richesson wrote:
I apologize
for the delay. Attached are
the latest use-case write-ups based upon last week’s discussion. I
appreciate the
xample, resolution of a
whole LSID could be an excellent time to expand the embedded
SAID metadata into normal RDF, exposing it to a reasoner.
Feedback welcome,
Dan Corwin
10 matches
Mail list logo
