- From: Eli Israel <Eli@SemanticWorld.Org>
- Date: Tue, 12 Aug 2003 14:15:04 +0300
- To: "Roger L. Costello" <costello@mitre.org>
- Cc: <www-rdf-interest@w3.org>
I had considered a slightly different approach to this problem - in the spirit of semantic web services, a service could specify its input and output in terms of an ontology. For example, given a class 'Lenth' with properties 'inchRepresentation' and 'centimeterRepresentation' we may have a simple measurement conversion service that tells you it will take in Length.inchRepresentation and return Length.centimeterRepresentation. I think this architecture has the advantage of also supporting calculations/processes that are given to change - tax calculations, stock analysis, weather reports, etc. An attached piece of code would have to hit the internet to tackle these. Also - attaching code ties you into a particular language. Eli Israel www.Unicorn.com www.SemanticWorld.org ----- Original Message ----- From: "Roger L. Costello" <costello@mitre.org> To: <www-rdf-interest@w3.org> Cc: "Costello,Roger L." <costello@mitre.org> Sent: Sunday, August 10, 2003 5:19 PM Subject: ANN: Enhancing Data Interoperability with Ontologies, Canonical Forms, and Include Files > > Hi Folks, > > Several weeks ago we had an excellent discussion on expressing the > relationship of entities that use different units-of-measure. The more > general problem is - how do we express relationships that require a > transformation between the entities? > > Based upon our discussions I have synthesized an approach to expressing > transformation relationships, and an approach that applications can take > to use this relationship information to enhance interoperability. Here > is the URL to the paper I have written: > > http://www.xfront.com/interoperability/CanonicalForms.html > > Comments are welcome. /Roger >
Received on Tuesday, 12 August 2003 07:15:41 UTC