RE: An argument for bridging information models and ontologies at the syntactic level

 
> The main point of emphasis for me is
> that a separation of concerns is maintained so you aren't modeling
> relations such as hasCode, for instance, in OWL.  Jim's point 
> about this
> being a basic tenant of Engineering principles is absolutely 
> correct.  

This is a critical separation of concerns that I believe is not well understood
and practiced.

For instance I would distinguish between information models/ontologies that seek
to capture the
semantics of the information; as opposed to implementation/data models that seek
to capture the structure
and storage of the data in the context of an application using a particular
technology.

In general people end up modeling data structures using OWL/RDF which is not
what they were intended for
in the first place.

---Vipul

The information transmitted in this electronic communication is intended only
for the person or entity to whom it is addressed and may contain confidential
and/or privileged material. Any review, retransmission, dissemination or other
use of or taking of any action in reliance upon this information by persons or
entities other than the intended recipient is prohibited. If you received this
information in error, please contact the Compliance HelpLine at 800-856-1983 and
properly dispose of this information.

Received on Wednesday, 26 March 2008 18:54:40 UTC