Main extensions of ISO/IEC 19763-3 MFI Ontology registration Edition2

1
Main extensions of ISO/IEC 19763-3 MFI Ontology
registration Edition2
WG2 N1132

• HE Keqing (HE Yangfan) and OKABE, Masao
• Editors
• ISO/IEC 19763-3 MFI Ontology registration project
• 2008.05.26-30

2
Motivations to Ed2

• By nature,
• ontologies evolves gradually and
• ontologies are reused mutually.
• So, it is required that MFI Ontology registration
  can register mulch versions of an ontology and
  keep track with them.
• Evolution_Information_Model package
• Several other requirements Basic_Model package

3
Two packages

• MFI Ontology registration Ed2 introduces the
  notion of package of MOF and consists of two
  packages.
• One is Basic_Model package and
• the other is Evolution_Information_Model
  package.
• Evolution_Information_Model package
• consists of new metaclasses that
• store evolution information (relation
• between previous and new versions)
• of ontologies.
• Basic_Model package is similar to
• Ed1 but has several extensions.

4

5
Evolution_Information_Model package (1 of 2)

• Metaclass Evolution_Information has three
  mataclasses that shows previous version and new
  version of Ontology_Whole, Ontology_Component,
  Ontology_Atomic_Construct respectively.

6
Evolution_Information_Model package (2 of 2)

• Note
• To avoid unnecessary complexity
• of evolution management,
• neither folk-type evolutions nor
• versions merging are supported.
• So, the cardinality constraints of
• both previousVersion and newVersion are
  exactly one.
• Evolution_Information is not a subclass of
  Administered Item because all the administrative
  information can be gained from newVersion

7

8
Basic_Model package

• Basic_Model package mainly has three extensions
  compared to Ed1.
• New mataclasses Unregistered_Ontology_Whole and
  Unregistered_Ontology_Atomic_Construct are
  introduced
• to enable an ontology registered to import
  ontologies not registered etc.
• New mataclass Authoritative_Extent is
  introduced
• to enable Local_Ontology_Component and
  Local_Ontology_Atomic_Construct to be resused.
• Uses IRIs, rather than URIs.

9
1.-1 Unregistered_Ontology_Whole (1 of 3)

• In the case that an ontology registered in MFI
  Ontology registration registry import an
  ontology not registered in MFI Ontology
  registration registry, Ed1 has a problem since
  Ed1 does not support import directly.
• To resolve this problem, Ed2 introduces a new
  metaclass Unregistered_Ontology_Whole.
• An Unregistered_Ontology_Whole designates an
  ontology that is not registered in MFI Ontology
  registration registry and that is imported by
  an ontology that is registered in MFI Ontology
  registration registry.

10
1.-1 Unregistered_Ontology_Whole (2 of 3)

• Ed1 does not support ontology inclusion such as
  owlimport.
• So, in the case of
• Ed1 simply registers ontology A as follows,
  expanding import.

ontology
sentence
symbol
10
11
1.-1 Unregistered_Ontology_Whole (3 of 3)

• But, Ed1 has a problem in the case that ontology
  B is not registered because in that case ontology
  A cannot expand ontology B.
• So, if ontlogy B is not registered, Ed2 will
  simply register ontology A as it is as follows,
• Note
• Since ontology B is not registered, the
  information on the ontology component and
  ontology atomic construct of ontology B cannot be
  gained, but a part of the information on the
  ontology whole of ontology B can be gained from
  ontology A.

Registered_Ontology_Whole
Unregistered_Ontology_Whole
12
1.-2 Unregistered_Ontology_Atomic_Construct

• In the case that an ontology registered in MFI
  Ontology registration registry uses some
  non-logical symbol that is defined in an ontology
  not registered in MFI Ontology registration
  registry, Ed1 cannot distinguish this
  non-logical symbol from the one defined in this
  ontology registered.
• To resolve this problem, Ed2 introduces a new
  metaclass Unregistered_Ontology_Atomic_Construct
  .
• An Unregistered_Atomic_Construct designates a
  non-logical symbol that is not defined in an
  ontology registered in MFI Ontology registration
  registry but that is used by an ontology that is
  registered in MFI Ontology registration registry.

13
1. -3 No Unregsitred_Ontology_Component

• A metaclass Unregsitred_Ontology_Component is
  not introduced even in Ed2 since no language can
  refer an sentence in other ontology.

14
2. Authoritative_Extent (1 of 3)

• In addition to Reference_Ontology_Component and
  Reference_Ontology_Atomic_Construct,
• relatively stable Local_Ontology_Component and
  Local_Ontology_Atomic_Construct should be able
  to
• be reused by other Local_Ontology_Whole and
  Local_Ontology_Component.
• To enable it, ED2 introduces a new metaclass
  Authoritative_Extent, which represents
  authoritative extent as a partial order.

15
2. Authoritative_Extent (2 of 3)

• A Ontology_Whole with authoritative_Extent Lm
  can consists of (reuse) other Local_Ontology_Compo
  nent with authoritative_Extent Ln iff Lm Ln.

For Unregistered_Ontology_Whole and
Unregistered_Ontology_Atomic_Construct
For Reference_Ontology_Whole, Reference_Ontology_
Component and Reference_Ontology_Atomic_Construct
For Local_Ontology_Whole, Local_Ontology_Component
and Local_Ontology_Atomic_Construct
16
2. Authoritative_Extent (3 of 3)

• Now, for example, as for Ontology_Component,
• Reference_Ontology_Component
• is a class of Ontology_Component
• whose value of authoritative_Extent
• is reference.
• Local_Ontology_component
• is a class of Ontology_Component
• whose value of authoritative_Extent
• is not either reference or unregistered.

17
3. Uses IRIs, rather than URIs.

• To support non-European characters, including
  Hungul, Chinese and Japanese character.
• IRI RFC 3987 Internationalized Resource
  Identifiers (IRIs),
• IETF Proposed Standard
• Note
• URI is still valid since URI is a subclass of
  IRI.

18
Basic_Model package (1 of 4)
metaclasses that are directly referred in the
main extensions
other modified or newly introduced metaclasses
related to the main extensions
19
Note Metamodel of Ed1

20

• Thank you!
• Comments and suggestions are highly appreciated.