gnue/geas/doc odmg.txt

[Daniel E. Baumann]

CVSROOT:        /cvsroot/gnue
Module name:    gnue
Changes by:     Daniel E. Baumann <address@hidden>      02/02/08 01:10:32

Modified files:
        geas/doc       : odmg.txt 

Log message:
        Ran through ispell, fixed typos and misspellings.

CVSWeb URLs:
http://savannah.gnu.org/cgi-bin/viewcvs/gnue/gnue/geas/doc/odmg.txt.diff?tr1=1.2&tr2=1.3&r1=text&r2=text

Patches:
Index: gnue/geas/doc/odmg.txt
diff -c gnue/geas/doc/odmg.txt:1.2 gnue/geas/doc/odmg.txt:1.3
*** gnue/geas/doc/odmg.txt:1.2  Fri Feb  8 01:06:46 2002
--- gnue/geas/doc/odmg.txt      Fri Feb  8 01:10:32 2002
***************
*** 10,16 ****
    can be related to each other, and how objects can be named and
    identified
    - Object Definition Language (ODL) is used to specify application
!   object models adn is also used to explain the constructs of the
    Object Model
    - Object Model specifies constructs supported by ODMS:
  
--- 10,16 ----
    can be related to each other, and how objects can be named and
    identified
    - Object Definition Language (ODL) is used to specify application
!   object models 07 is also used to explain the constructs of the
    Object Model
    - Object Model specifies constructs supported by ODMS:
  
***************
*** 59,65 ****
    objects, Class Person defines both the abstract behavior and the
    abstract state of Person objects, the struct Complex defines only
    the abstract state of Complex number literals, in addition to the
!   struct definition and the primitive literal datatypes (boolean, car,
    short, long, float, double, octet, and string), ODL defines
    declarations for user-defined collection, union, and enumeration
    literal types.
--- 59,65 ----
    objects, Class Person defines both the abstract behavior and the
    abstract state of Person objects, the struct Complex defines only
    the abstract state of Complex number literals, in addition to the
!   struct definition and the primitive literal 0 (boolean, car,
    short, long, float, double, octet, and string), ODL defines
    declarations for user-defined collection, union, and enumeration
    literal types.
***************
*** 74,80 ****
    
      Subtyping and inheritance of Behavior
      =====================================
!     - ODMG Object Modle includes inheritance-based type-subtype relationships
      - the relationships are commonly represented in graphs; each node
      is a type and each arc connects one type, *supertype* and another
      type *subtype*
--- 74,80 ----
    
      Subtyping and inheritance of Behavior
      =====================================
!     - ODMG Object 1 includes inheritance-based type-subtype relationships
      - the relationships are commonly represented in graphs; each node
      is a type and each arc connects one type, *supertype* and another
      type *subtype*
***************
*** 98,104 ****
      behavior 
      - e.g, a Employee might have an operation for claculate_paycheck
      - Salaried_Employee and Hourly_Employee might each refine that
!     behavior to relflect specific needs
      - polymorphic nature of object programming would enable to correct
      behavior to be invoked at runtime, dependent on the actual type of
      the instance
--- 98,104 ----
      behavior 
      - e.g, a Employee might have an operation for claculate_paycheck
      - Salaried_Employee and Hourly_Employee might each refine that
!     behavior to 0 specific needs
      - polymorphic nature of object programming would enable to correct
      behavior to be invoked at runtime, dependent on the actual type of
      the instance
***************
*** 155,168 ****
      boss
      - not that since class EmployeePerson inherits behavior from (ISA)
      Employee, instances of EmployeePerson and ManagerPerson would
!     all support the behavior deifned within this interface
!     - only legal exception to name oveloading occurs when the same
      property declaration in a class and one of its inherited
      interfaces
!     - since propeties declared within an interface also have a
      procedural interface, such redundant declarations are useful
!     in situations where it is desireable to allow relationships to
!     cross distribution boundaries, yet they also constitue part of the 
      abstract state of the object
      
        Extents
--- 155,168 ----
      boss
      - not that since class EmployeePerson inherits behavior from (ISA)
      Employee, instances of EmployeePerson and ManagerPerson would
!     all support the behavior 0 within this interface
!     - only legal exception to name 0 occurs when the same
      property declaration in a class and one of its inherited
      interfaces
!     - since 0 declared within an interface also have a
      procedural interface, such redundant declarations are useful
!     in situations where it is 0 to allow relationships to
!     cross distribution boundaries, yet they also 0 part of the 
      abstract state of the object
      
        Extents
***************
*** 174,180 ****
        - if type A is subtype of type B, then extent of A is a subset
        of the extent of B
        - relational DBMS maintains an extent for every defined table
!       - OMDS schema designer can decide whether the system should
        automatically maintain the extent of each type
  
        Keys
--- 174,180 ----
        - if type A is subtype of type B, then extent of A is a subset
        of the extent of B
        - relational DBMS maintains an extent for every defined table
!       - 2 schema designer can decide whether the system should
        automatically maintain the extent of each type
  
        Keys
***************
*** 183,191 ****
        identified by the values they carry for some property or set of
        properties
        - these identifying properties are called *keys*
!       - in relational model, thse properties are called *candidiate
        keys*
!       - a *simple key* consustes of a single property
!       - a *compound key* consist of a set of properties
        - the scope of uniqueness is the extent of the type; type must
        have an extent to have a key
--- 183,191 ----
        identified by the values they carry for some property or set of
        properties
        - these identifying properties are called *keys*
!       - in relational model, 1 properties are called *0
        keys*
!       - a *simple key* consists of a single property
!       - a *compound key* consists of a set of properties
        - the scope of uniqueness is the extent of the type; type must
        have an extent to have a key