hi all,
yes, i also agree that these are great points, except for a quibble.
"Data models like schemas, structures, and data formats are
implementation details"
in Model Driven Architecture (MDA), the Platform Independent Model data
model is free of implementation details. as a developer who
4. Keeping the two (data models and conceptual models) separate allows them to
evolve independently.
[VK] I agree with this principle emphatically, as has been expressed in my
e-mails on the same topic. The semantic web community
needs to articulate in some manner, that SW specifications like RDF/O
Chimezie, excellent observation. Agree with principals you are
articulating.
I would add:
1. Data models like schemas, structures, and data formats are implementation
details.
2. Concept models operate at many levels. As an example, concept models may
represent the entire data model as a concep
It seems to me that we shouldn't throw out an important distinction just because
SNOMEDCT has terms that should be expressed in information model.
[VK] I did not mean to throw out the distinction, but to position the
distinction differently. For instance, I would still differentiate betwe
> Okay, for me, the difference is whether or not the underlying language
> is backed by a some knowledge reprsentation with a formal
> semantics. By
> knowledge representation I primarily mean a language that can
> facilitate
> inference [1].
I agree with the above, though I would probably
