Meeting Minutes 12 December 2006 (01)
ONION Charter
Charter was reviewed and it was agreed that it will remain as a draft
until mid January so that all comments can be addressed'
http://ontolog.cim3.net/cgi-bin/wiki.pl?ONION (02)
Comment - Implicit Objective
Not currently stated in charter but an implicit objective is to explicitly
encourage the creation of Open International standards for those elements
of the Business of IT that are open, ethical, legal, and generic. (03)
Summary BCM Ontological Relations
The Chair of The OASIS BCM TC focused on the symbiosis of the Guidelines
for eBusiness and the best practice promoted by the ITSM / COBIT /
Security specifications. In particular -
Semantic relations between the Business Centric Methodology to ITSM / COSO
/ COBIT / Security are layer specific and provide building blocks to other
common terms. For example, the semantic bridge to Control Objectives for
Information and related Technology (COBIT) could be expanded to incoporate
Business Process Management (or BPM) which refers to practice of applying
IT engineering techniques to the policies and procedures used by
businesses to optimize and adapt their processes. (04)
Layers
BCM has four foundational layers that exploit template structures and
archetype definitions.
Implementation Layer focused on defining use of SOA, Protocols and other
IT infrastructure resources.
Conceptual Layer ensures that all elements, including SOA artifacts, have
unambiguos definitions. Such as those published in the ONION ontology.
Extension Layer explicitly adresses use of open source constructs and
domain specific componentry that has been defined by one or more Community
of Interest / Action / Practice. e.g. ACORD; HL7
Business Layer Templates include (05)
Comments on Current Draft
http://ontolog.cim3.net/file/work/ONION/reference/onionCPLv1.owl (06)
Reasonable Content
The validity of ONION content, such as necessary ontological statements
and domain specific extension layers, is measured by the majority of the
cOP membership declaring it fit for reasonable use. (07)
Distinctionary Construct
The distinctionary construct allow one ONION statement to be distinct from
other ontological statements.
Such that a commonly used term is first placed in the ONION as a type of a
broader term or concept and then another specialized term is added that
distinguishes each particular notion or concept from its peers. (08)
Leverage Existing Definitions
Whenever possible the ontological statements should leverage publically
available ontological definitions. For example -
http://www.ontologyportal.org/translations/SUMO.owl.txt
<rdfs:Class rdf:ID= "Process">
<rdfs:subClassOf rdf:resource ="#Physical"/>
<rdfs:comment>Intuitively, the class of things that happen
and have temporal parts or stages. Examples include extended events
like a football match or a race, actions like Pursuing and Reading,
and biological processes. The formal definition is: anything that lasts
for a time but is not an Object. Note that a Process may have
participants 'inside' it which are Objects, such as the players
in a football match. In a 4D ontology, a Process is something whose
spatiotemporal extent is thought of as dividing into temporal stages
roughly perpendicular to the time-axis.</rdfs:comment>
</rdfs:Class> (09)
Future Discussion Points proposed by Peter Brooks (010)
CMDB - Eventually I'd expect the CMDB (Configuration Management Database)
to be an instantiation of the ITSM ontology. (011)
Problem Management - ITSM consists of a series of processes. There are
some top-level descriptions of parts of processes, but I'd expect some
common definition of a process and its instantiation. "Problem
Management", for example, is a process. It is instantiated by a 'Problem'
(or a 'Problem Record') that has a number of properties - states,
ownership, metrics and relationships. (012)
Metrics - Is the ontology not the place to describe relationships? I see,
for example, that 'Metrics' are mentioned - but metrics relate to every
process, so are really, as above, a property of a process. (013)
Instantiated Elements -. If you had an ideal ontology driven application
(just a pipe dream, but I'm mentioning this to try to clarify my
understanding) then, if it instantiated the ITSM ontology, all you'd need
is some gui elements to interface to add, update, and report verbs in the
application and you'd have a fully functional application to support all
elements of Service Management (014)
Event - As far as detail is concerned, I'm surprised that there is a
'Businessevent', but no primitive 'event'. Surely events cause
incidents, problems and changes? In simple terms: event -> problem ->
incident and problem -> change so events are pretty essential. (015)
CI (Configuration Item) - The definition of a CI is too narrow, CIs
include people, organisations, and process elements - so a 'problem
record' is a CI. (016)
CI Relations - Again, as in 'Metrics' above, the fundamental thing about
CIs is their relationship to other CIs and the description of these
relationships ('is owned by', 'is caused by', 'is contained in','is
installed on','is escalated to', 'is solved by','is due to be
installed/updated on','is mirrored by' etc. etc.) is what enables
Configuration Management to take place. Without it, all you have is a
static asset management database. (017)
Administrivia
To facilitate participation in future conference calls I have been asked
to schedule them a little earlier.
To help members manage their schedules I will send a reminder
approximately 1 day before the scheduled event takes place.
Please note that as a member of the ONION CoP you are able to participate
in other ONTOLOG hosted events. In 2007 you will automatically receive
invitations to open information exchange sessions. (018)
Wishing you happy holidays (019)
thanks for you support (020)
--
Carl Mattocks
Chair OASIS Business Centric Methodology TC
co-Chair OASIS (ISO/TS 15000) ebXMLRegistry Semantic Content SC
ONTOLOG ONION CoP Leader
CEO CHECKMi
vmail(usa) 908 322 8715
www.CHECKMi.com (021)
_________________________________________________________________
To Post: mailto:onion-forum@xxxxxxxxxxxxxxxx
Msg Archives: http://ontolog.cim3.net/forum/onion-forum/
Subscribe/Unsubscribe/Config:
http://ontolog.cim3.net/mailman/listinfo/onion-forum/
Community Wiki: http://ontolog.cim3.net/cgi-bin/wiki.pl?ONION
Community Files: http://ontolog.cim3.net/file/work/ONION/
Community Portal: http://ontolog.cim3.net/ (022)
|