Jack,
The reason for combining the two engineering tracks was not because we think
the two topics are the same.
- Henson (01)
-----Original Message-----
From: ontology-summit-bounces@xxxxxxxxxxxxxxxx
[mailto:ontology-summit-bounces@xxxxxxxxxxxxxxxx] On Behalf Of Jack Ring
Sent: Wednesday, January 25, 2012 7:15 PM
To: Ontology Summit 2012 discussion
Subject: Re: [ontology-summit] FW: Track 1&2 Joint Mission and Session
Abstracts (02)
I think this is unfortunate. An understanding of and ability to clearly
communicate about a system is needed by a wide expanse of people of which
only about 10% engage in systems engineering. In fact, the larger confusion
among system engineering people is ambiguity about what means system. (03)
On Jan 25, 2012, at 8:31 AM, Obrst, Leo J. wrote: (04)
> All,
>
> Matthew West and Henson Graves came up with their joint Track 1&2 Mission
Statement, along with Session Abstracts. We discussed this a bit, and would
like the entire Ontology Summit 2012 community to see this, and comment.
>
> We think this merger of the two Tracks is useful.
>
> Thanks,
> Leo and Nicola
>
> -----Original Message-----
> From: Matthew West [mailto:matthew.west@xxxxxxxxxxxxxxxxxxxxxxxxx]
> Sent: Monday, January 23, 2012 2:49 PM
> To: 'Peter Yim'; 'Henson Graves'; 'Nicola Guarino'; Obrst, Leo J.
> Subject: Track 1&2 Joint Mission and Session Abstracts
>
> Dear all,
>
> Peter just put me on the hook to come up with an overall mission
> statement for Tracks 1&2, which it looks like we are going to merge
> (as long as Henson is happy with that), and also an abstract for the
> first two sessions. Here
> goes:
>
> Track 1&2: Ontology for Big Systems & Systems Engineering
>
> Mission
> We aim to bring key challenges to light with large-scale systems and
> systems of systems for ontology and identify where solutions exist,
> where the problems require significant research, and where we can work
> towards solutions as part of this summit. The areas to be considered
include:
> - working with and integrating the results of models using multiple
> modeling languages
> - the systems lifecycle and the issues of sharing data within and
> between lifecycle stages
> - the difference between requirements and the delivered system
> - systems of systems vs systems,
> - the nature of system components and the difference between these and
> the parts installed,
> - the connections between system components and what they carry,
> - systems behaviour,
> - federated systems both as a bit system, and as a solution to some of
> the challenges,
> - principles of how to construct good quality reusable models
> (ontologies)
> - the management of ontologies of and for large systems and the
> challenges in developing and maintaining them.
>
> session-03: Ontology for Big Systems & Systems Engineering - I: The
> Systems and Systems Engineering Problem Space
>
> Abstract
> In this session we want to look at the problems in big systems and
> systems engineering where ontology has a role to play. The aim is to
> uncover the various areas where challenges exist that the world of
> ontology can contribute to.
>
>
> session-04: Ontology for Big Systems & Systems Engineering - II: a
> response to the problem space and setting out the working program for
> this Summit Track
>
> Abstract
> In this session we will consider the output of the first session, and
> try to
> identify:
> - where there are solutions already available, if you know where to
> look,
> - where the problems require significant research,
> - where there is an opportunity to make useful progress within the
> timescale of the ontology summit.
>
> Regards
>
> Matthew West
> Information Junction
> Tel: +44 1489 880185
> Mobile: +44 750 3385279
> Skype: dr.matthew.west
> matthew.west@xxxxxxxxxxxxxxxxxxxxxxxxx
> http://www.informationjunction.co.uk/
> http://www.matthew-west.org.uk/
>
> This email originates from Information Junction Ltd. Registered in
> England and Wales No. 6632177.
> Registered office: 2 Brookside, Meadow Way, Letchworth Garden City,
> Hertfordshire, SG6 3JE.
>
>
>
>
>
> _________________________________________________________________
> Msg Archives: http://ontolog.cim3.net/forum/ontology-summit/
> Subscribe/Config:
> http://ontolog.cim3.net/mailman/listinfo/ontology-summit/
> Unsubscribe: mailto:ontology-summit-leave@xxxxxxxxxxxxxxxx
> Community Files: http://ontolog.cim3.net/file/work/OntologySummit2012/
> Community Wiki:
> http://ontolog.cim3.net/cgi-bin/wiki.pl?OntologySummit2012
> Community Portal: http://ontolog.cim3.net/wiki/ (05)
_________________________________________________________________
Msg Archives: http://ontolog.cim3.net/forum/ontology-summit/
Subscribe/Config: http://ontolog.cim3.net/mailman/listinfo/ontology-summit/
Unsubscribe: mailto:ontology-summit-leave@xxxxxxxxxxxxxxxx
Community Files: http://ontolog.cim3.net/file/work/OntologySummit2012/
Community Wiki: http://ontolog.cim3.net/cgi-bin/wiki.pl?OntologySummit2012
Community Portal: http://ontolog.cim3.net/wiki/ (06)
_________________________________________________________________
Msg Archives: http://ontolog.cim3.net/forum/ontology-summit/
Subscribe/Config: http://ontolog.cim3.net/mailman/listinfo/ontology-summit/
Unsubscribe: mailto:ontology-summit-leave@xxxxxxxxxxxxxxxx
Community Files: http://ontolog.cim3.net/file/work/OntologySummit2012/
Community Wiki: http://ontolog.cim3.net/cgi-bin/wiki.pl?OntologySummit2012
Community Portal: http://ontolog.cim3.net/wiki/ (07)
|