But in the case of BIM, GIS, facility management, emergency management - still up to the application developers to support or build in at least essential parts of the model or artifacts?
DEBORAH MACPHERSON, CSI CCS, AIA
Specifications and Research
Cannon Design
1100 Wilson Boulevard, Suite 2900
Arlington, Virginia 22209
Direct Line 703 907 2353
4 Digit Dial 6353
dmacpherson@xxxxxxxxxxxxxxxx
cannondesign.com
ü Please consider the environment before printing this email.
From: ontology-summit-bounces@xxxxxxxxxxxxxxxx [mailto:ontology-summit-bounces@xxxxxxxxxxxxxxxx] On Behalf Of Cory Casanave
Sent: Tuesday, April 26, 2011 1:49 PM
To: Ontology Summit 2011 discussion
Subject: Re: [ontology-summit] Legacy Software to Web Services
Deborah ,
Re: MDD (Model Driven Development) uses a core concept of a UML-like data model that can then allow the instances of the same data to be shared is multiple service contexts (Human consumer, EAI, etc).
Not necessarily, MDA/MDD uses precise models to produce additional artifacts of value such as acquisition specifications, documentation, adapters or executable code. The source models may be UML, process models, ontologies or anything with sufficient precision to support automated execution or production of derivative value. Using MDA/MDD with ontologies as the source models is very practical.
-Cory Casanave
From: ontology-summit-bounces@xxxxxxxxxxxxxxxx [mailto:ontology-summit-bounces@xxxxxxxxxxxxxxxx] On Behalf Of Duane Nickull
Sent: Tuesday, April 26, 2011 12:53 PM
To: Ontology Summit 2011 discussion
Subject: Re: [ontology-summit] Legacy Software to Web Services
Peter – can I peruse the calendars and take a look and propose a date?
Duane
On 4/26/11 7:26 AM, "Brand Niemann" <bniemann@xxxxxxx> wrote:
Duane, Thanks. I would like to see a demo ASAP for my work to help Cory on SMIF. Thanks, Brand
From: ontology-summit-bounces@xxxxxxxxxxxxxxxx [mailto:ontology-summit-bounces@xxxxxxxxxxxxxxxx] On Behalf Of MacPherson, Deborah
Sent: Tuesday, April 26, 2011 10:00 AM
To: Ontology Summit 2011 discussion
Subject: Re: [ontology-summit] Legacy Software to Web Services
Thanks very much. I will look at these and a demonstration would be a great Ontolog program sometime if Peter and everyone else feel the same. Even just walking through the OASIS reference model would be helpful
DEBORAH MACPHERSON, CSI CCS, AIA
Specifications and Research
Cannon Design
1100 Wilson Boulevard, Suite 2900
Arlington, Virginia 22209
Direct Line 703 907 2353
4 Digit Dial 6353
dmacpherson@xxxxxxxxxxxxxxxx
cannondesign.com
ü Please consider the environment before printing this email.
From: ontology-summit-bounces@xxxxxxxxxxxxxxxx [mailto:ontology-summit-bounces@xxxxxxxxxxxxxxxx] On Behalf Of Duane Nickull
Sent: Tuesday, April 26, 2011 2:01 AM
To: Ontology Summit 2011 discussion
Subject: Re: [ontology-summit] Legacy Software to Web Services
Deborah:
I would start by reading these documents:
1. http://pubs.opengroup.org/onlinepubs/7699909399/toc.pdf
This one is entitled: Navigating the SOA Open Standards Landscape Around Architecture
And then the second level OASIS Reference Model for SOA
http://docs.oasis-open.org/soa-rm/v1.0/soa-rm.pdf
And then the follow on:
http://docs.oasis-open.org/soa-rm/soa-ra/v1.0/soa-ra-cd-02.pdf
This will give you a clear indication that semantics is a difficult question. Having said that, I have found that Adobe’s approach used within LiveCycle ES is a very simple data model and process modeling format that has gained huge traction. MDD (Model Driven Development) uses a core concept of a UML-like data model that can then allow the instances of the same data to be shared is multiple service contexts (Human consumer, EAI, etc).
I can give a demonstration on this to the group if required or even privately.
Duane
On 4/25/11 9:05 AM, "Cory Casanave" <cory-c@xxxxxxxxxxxxxxx> wrote:
I agree – federation is THE problem for information technologies this decade. That is why we are pursuing SIMF:
http://www.omgwiki.org/architecture-ecosystem/doku.php?id=semantic_information_modeling_for_federation_rfp
Both in standards and in our own practice and development. We would very much like to collaborate with others who have the same goals.
-Cory
From: ontology-summit-bounces@xxxxxxxxxxxxxxxx [mailto:ontology-summit-bounces@xxxxxxxxxxxxxxxx] On Behalf Of MacPherson, Deborah
Sent: Monday, April 25, 2011 11:18 AM
To: Ontology Summit 2011 discussion
Subject: Re: [ontology-summit] Legacy Software to Web Services
Thanks Cory - I think the main problem Building Information Models are facing are the federation. I don't see how this could work WITHOUT ontologies. Will continue on with this open architecture design and keep your comments in mind. Thanks
DEBORAH MACPHERSON, CSI CCS, AIA
Specifications and Research
Cannon Design
1100 Wilson Boulevard, Suite 2900
Arlington, Virginia 22209
Direct Line 703 907 2353
4 Digit Dial 6353
dmacpherson@xxxxxxxxxxxxxxxx
cannondesign.com
ü Please consider the environment before printing this email.
From: ontology-summit-bounces@xxxxxxxxxxxxxxxx [mailto:ontology-summit-bounces@xxxxxxxxxxxxxxxx] On Behalf Of Cory Casanave
Sent: Monday, April 25, 2011 10:57 AM
To: Ontology Summit 2011 discussion
Subject: Re: [ontology-summit] Legacy Software to Web Services
Deborah,
Consider SOA interfaces, “canonical data models” and similar structural approaches as viable when it is practical to assert a single standard structure for information exchange or access. You can actually get quite a bit of mileage out of such structural standards. The idea with a standard structural approach is that it can be sufficiently general to cover your business needs and it provides a single standard to adapt existing systems (usually manually). This works particularly well where the structural (SOA or information) model is used with a model driven architecture (MDA) pattern so that it is technology neutral and expressed in business terms.
Where structural approaches start having trouble is where there is a lot of variation – perhaps because of independently conceived models/interfaces/vocabularies that need to come together or due to different authorities, user viewpoints or perspectives. In these cases the standard structures tend to be brittle and difficult to federate or evolve. Ontologies can provide as conceptual hub between different ways to represent or analyze the same or related information. Since the ontologies are built around the domain, not the technology or a specific use case, they tend to be more flexible. In addition some of the axioms available in ontologies allow for better federation of independently conceived models or integration of diverse viewpoints.
There is not a “hard line” between these approaches and the technologies are frequently confused with the techniques. You can do ontological modeling in “structured” languages (like UML) and structured applications in OWL – it is the practice as much as the technology that will impact your results.
Hope this helps a bit (and the opinions expressed are my own)!
Regards,
Cory Casanave
Model Driven Solutions
From: ontology-summit-bounces@xxxxxxxxxxxxxxxx [mailto:ontology-summit-bounces@xxxxxxxxxxxxxxxx] On Behalf Of MacPherson, Deborah
Sent: Monday, April 25, 2011 10:38 AM
To: Ontology Summit 2011 discussion
Subject: [ontology-summit] Legacy Software to Web Services
Hi John, Everyone
I am seeking a brief explanation for how ontologies can help bridge the gap from legacy software to web services. For example - the role of ontologies versus APIs, middleware, and relational databases - a process model or short narrative of all the parts that would need to work together.
For facility and geospatial data, most likely a large set of RDF assertions and small set of Tiny Ontologies All Stitched Together (TOAST) could solve many of our current problems. However to pitch this better, a concise explanation is needed for exactly where an ontology should live in relation to projects at firms behind firewalls versus accessible across an enterprise/industry. And what the effect is on legacy software and databases i.e. not losing or recreating data, instead bringing them up to speed for more precise information sharing and requirements tracking.
Thank you,
Deborah
DEBORAH MACPHERSON, CSI CCS, AIA
Specifications and Research
Cannon Design
1100 Wilson Boulevard, Suite 2900
Arlington, Virginia 22209
Direct Line 703 907 2353
4 Digit Dial 6353
dmacpherson@xxxxxxxxxxxxxxxx
cannondesign.com
ü Please consider the environment before printing this email.
---
Adobe LiveCycle Enterprise Architecture - http://www.adobe.com/products/livecycle/
Adobe MAX 2011 - http://technoracle.blogspot.com/2011/03/adobe-max-2011.html
TV Show - http://tv.adobe.com/show/duanes-world/
Blog – http://technoracle.blogspot.com/
Music – http://22ndcenturyofficial.com/
Twitter – http://twitter.com/duanechaos/
---
Adobe LiveCycle Enterprise Architecture - http://www.adobe.com/products/livecycle/
Adobe MAX 2011 - http://technoracle.blogspot.com/2011/03/adobe-max-2011.html
TV Show - http://tv.adobe.com/show/duanes-world/
Blog – http://technoracle.blogspot.com/
Music – http://22ndcenturyofficial.com/
Twitter – http://twitter.com/duanechaos/