[humanmarkup-comment] HMI.glossary My revised glossary

[Ranjeeth Kumar Thunga <rkthunga@humanmarkup.org>]

It looks VERY nice.  Thanks again Joe.
The idea about an explanatory paragraph is very good, and I shall
incorporate it into my future documents.

The only thing I'll need to remove is the request for individual submissions
(all submissions should be on the public board).

Also, we'll probably need definitions for frameworks and taxonomies here...
;-)


Ranjeeth Kumar Thunga

----- Original Message -----
From: Joseph Norris
To: OASIS Comment
Sent: Wednesday, October 24, 2001 7:19 PM
Subject: [humanmarkup-comment] HMI.glossary My revised glossary


(note: this document was sent earlier, but it did not make it to the
comments board for some reason. - Joe)

*****************


HMI.GLOSSARY
last modified: 24 October 2001
------------------------------


Introduction
------------

This glossary was created to assist researchers and people who that are
interested in the work of the HumanMarkup Technical Committee.

By making working definitions and concepts explicit, researchers will be
able to 1) understand the group's current usage of a specific term and 2) be
able to propose changes, elaborations, and updates to the glossary words and
definitions.

If there is a term you would like to add, define, or elaborate on please
email Joseph Norris at jwnorris@humanmarkup.org and your submission will be
promptly added to this glossary, which is to be a living document.


Purpose
-------

For the purpose of defining the vocabulary of the HumanMarkup Language,
apart from its actual use in XML Namespaces, XML Schemata, UML Models, RDF
Models and RDF Schemata, This glossary attempts to define the uses of
various term found on our website. Where appropriate the acronyms XML, RDF,
or UML will precede a definition that is specific to those systems or
usages.

Glossary Definitions
--------------------


Anthropomorphism -- is a known problem in creating "humanized" systems. An
animated agent that uses human gestures to indicate disinterest, feign
fatigue, and so on to the human can provoke observable anger.

Construct - Something constructed especially by mental synthesis <form a
construct of a physical object by mentally assembling and integrating
sense-data>

CWS/CMS -- California Health and Human Services Agency Data Services Child
Welfare Service Case Management System. (Occurs in a UML Use-Case Diagram
Example)

Domain - different fields/disciplines where HumanML that contain
nodes/properties that will map to databases/knowledge bases. (Not RDF Schema
ConstraintProperty)

Driver Language -- top-level document, which collects all the modules
together. This document only references other DTDs, and does not contain any
markup declarations in itself.

Genre - a class of internal or external visual and non-verbal states that
can be encoded in XML to enhance human to human communication.

Grammar - the system of rules and interactive matrixes that will be used by
HumanML to create coherent, interdependent, and interrelated modules that
will make explicit internal and external communication enhancement forms.

HLAL (vs. LLAL) High Level or Low Level Authoring Languages

Human - you and me. The computer is a medium that humans communication
though; the computer itself does not enhance the message and meaning of
communications, merely it is an enhances conveyance device. HumanMarkup.org
will enhance and reduce human miscommunication through the use of computer
technology.

Human Object - An instance of a Human class derived from a Human model.
Contains attributes, states and behaviors specific to this instance of the
Human class.

HumanML - the set of XML applications, modules, schemes, personality
engines, and attitude-emotion interfaces being developed, in an open-source
format, by the members of HumanMarkup.Org

Interface -- a named set of operations that characterize the behavior of an
element

Interpretative Matrix -- is a conceptual device to describe how the
HumanMarkup Language is designed to work. It is not a computational
construct, nor anything other than a description of how HumanMarkup
processors would operate in the computational environment of the Internet.
The markup of any particular piece of input that uses HumanMarkup would (we
think) be using tags based on elements used in classes and attributes with
values that give intensities for how much that class modifies a statement or
action or state of mind of the individual acting.

Knowledge Base -- A database of rules about a subject used in AI
applications.
Language - using advanced computer technologies such as XTM, XSD, RDF, and
others HumanMarkup will establish recognized language standards that will
markup human communication in ways to enhance the communication.

Meta-Language - literally a language about a language. HumanMarkup will
remove uncertainty, doubt, and misunderstanding from human to human
communication through the explicit markup of human emotions, attitudes, and
intentions.

Modules - a self contained language unit that will add layers of
communication enhancements as needed by the creator and the listener of a
particular communication.

Node- In a tree structure as used in directory or database management and
programming, a point where two or more lines or branches of the tree meet.

Ontology - HumanMarkup, by studying the nature of language and
communication, will, by use of XML and related technologies, be able to
enhance human communication and reduce human miscommunication through the
explicit markup of internal and external human traits.

RDF (Resource Description Format) - A recommendation from the W3C for
defining Web content. It provides a data modeling language that can be used
to catalog an entire Web site, an HTML page or an element within the page.
RDF provides a common way to create metadata about a Web resource.

RDF CWM-- Closed World Machine

RDF Properties -- see http://www.w3.org/TR/rdf-schema/#s2.2.2 2.2.2.
rdf:Property rdf:Property represents the subset of RDF resources that are
properties, i.e., all the elements of the set introduced as 'Properties' in
section 5 of the Model and Syntax specification [RDFMS]
http://www.w3.org/TR/REC-rdf-syntax/.

RDF Reification-- is the process of treating a triple as a nameable resource
about which further assertions can be made such as "probability 80%"
"approved by President" or "is true". In particular, every triple has the
four properties belongs to class Statement", "has subject S", "has verb V
(AKA Predicate P)", and "has object O" automatically: these need not be
written down explicitly.
A class can never be declared to be a subclass of itself, nor of any of its
own subclasses.


RDF subClass -- See http://www.w3.org/TR/rdf-schema/#s2.3.2 2.3.2.
rdfs:subClassOf this property specifies a subset/superset relation between
classes. The rdfs:subClassOf property is transitive. If class A is a
subclass of some broader class B, and B is a subclass of C, then A is also
implicitly a subclass of C. Consequently, resources that are instances of
class A will also be instances of C, since A is a sub-set of both B and C.
Only instances of rdfs:Class can have the rdfs:subClassOf property and the
property value is always of rdf:type rdfs:Class. A class may be a subclass
of more than one class.

Redefinable components -- The various use of parameter entities in the HTML
DTDs were analyzed to discover how they were being used. Various categories
were introduced to handle the different uses: in the case of DTDs these are
still implemented using parameter entities, but with a convention the
parameter entity names have a suffix giving their category. In an W3C XML
Schema implementation, many of the categories have more direct analogs. The
categories include:.content for general content models .class for
substitution groups .mix for mixed content models .attrib for attribute
groups

Representation - a method of making something visible, clearer, and more
explicit. HumanMarkup will use various types of visual, audio, and spatial
representations of internal states, contexts, and other human communication
traits.

Sign - (Semiotics) An act or gesture used to convey an idea, a desire,
information, or a command. HumanMarkup will allow visual, verbal, and
nonverbal signs to be made explicit via XML.

Signal - (Semiotics) An indicator, such as a gesture, that serves as a means
of communication. HumanMarkup will allow all forms of signals to me made
explicit via XML.

Signal Boundary -- (Semiotics)

Stereotypes -- Stereotypes are constraints or sets of constraints, rather
like facets in datatypes but less narrow.

Symbol -- (Semiotics) something that represents something else by
association, resemblance, or convention, especially a material object used
to represent something invisible. HumanMarkup will make visible and clear
what is murky and unclear. Symbols, often misunderstood and misinterpreted,
can be made more meaningful and clear in human communication.

Syntax - The rules governing the structure of a language. The modules, XML
applications, and other technologies developed and employed by the
HumanMarkup.org project will create a uniform and universally recognized
standards for human communication.

Term - Language of a certain kind; chosen words. Words, idioms, figures of
speech, and other complex terms often used in familiar communication can be
marked-up with explicit HumanMarkup data that can make a term, expression,
or complete text more meaningful to audiences of difference cultures,
languages, ages, and belief systems.

Token - (Semiotics) something serving as an indication, proof, or expression
of something else. Since human communication is so often misunderstood,
HumanMarkup can a form the basis of a community of trust based on the
recognized standards.

UML actor -- A coherent set of roles those users of use cases play when
interacting with these use cases.

UML aggregation -- a special form of association that specifies a whole-part
relationship between the aggregate (whole) and the component part. (From
Tutorial 1 at http://www.celigent.com/omg/umlrtf/tutorials.htm)

UML association -- a relationship between two or more classifiers that
involves connections among their instances. (From Tutorial 1 at
http://www.celigent.com/omg/umlrtf/tutorials.htm)

UML Class - a description of a set of objects that share the same
attributes, operations, methods, relationships, and semantics.

UML component -- a modular, replaceable, and significant part of a system
that packages implementation and exposes a set of interfaces

UML constraint -- a semantic condition or restriction.

UML CWM -- Common Warehouse Metamodel

UML dependency -- a relationship between two modeling elements, in which a
change to one modeling element (the indep. element) will affect the other
modeling element (the dependent element)

UML extend -- A relationship from an extension use-case to a base use case,
specifying how the behavior for the extension use case can be inserted into
the behavior defined for the base use-case.

UML generalization -- a taxonomic relationship between a more general and a
more specific element

UML include -- An relationship from a base use case to an inclusion
use-case, specifying how the behavior for the inclusion use-case is inserted
into the behavior defined for the base use case.

UML Interfaces -- are classes that function as operators to access, define,
include, exclude or make clear relationships between other classes when a
program is written using those other classes as opposed to building a
Module.

UML node -- a run- time physical object that represents a computational
resource.

UML realization -- a relationship between a specification and its
implementation

UML Stereotypes -- Used to define specialized model elements based on a core
UML model element, usually a class typified by a specialization constraint
which usually requires a value, a Boolean, number, string, etc, such as an
Actor, where an Instance of the Human Class with a Name participates in a
Use-Case, or an Interface which is special kind of Class that gives access
to other Classes in a Package.

UML Use-case analysis - An object-oriented method for designing information
systems by breaking down requirements into user functions. Each use case is
a transaction or sequence of events performed by the user. Use cases are
studied to determine what objects are required to accomplish them and how
they interact with other objects.

UML(Unified Modeling Language) - An object-oriented analysis and design
language from the Object Management Group (OMG). Many design methodologies
for describing object-oriented systems were developed in the late 1980s. UML
standardizes several diagramming methods, including Grady Booch's work at
Rational Software, Rumbaugh's Object Modeling Technique and Ivar Jacobson's
work on use cases. There are nine kinds of diagrams that are supported under
UML. See: http://www.omg.org/technology/documents/formal/uml.htm

Vocabulary - The sum of words used by, understood by, or at the command of a
particular person or group. HumanMarkup.org will set the standard for being
the vocabulary of vocabularies. Through the explicit markup of the internal
and external traits of human to human communication, one can see how all the
vocabularies used by so many different people can be made more clear to each
and every new audience.

XML Application -- Software engineered using XML as the basis.

XML Application- HumanMarkup recognizes that XML technologies will
revolutionize the Internet. As more people come to rely upon the Internet as
a communications medium, we shall employ the advanced XML technologies to
enhance communication and reduce miscommunication.

XML datatypes "datatypes" -- see http://www.w3.org/TR/xmlschema-2/RDF
instances "types"--see http://www.w3.org/TR/rdf-schema/ Section 2.1 The Type
System

XML Infosets -- Information Sets, see:
http://www.w3.org/TR/2000/WD-xml-infoset 20001220/   1. Introduction This
technical report defines an abstract data set called the XML Information Set
(Infoset). Its purpose is to provide a consistent set of for use in other
specifications that need to refer to the information in a well-formed XML
document [XML].

XML Module -- An entity that collects the various declarations relating to a
distinct type of content. There are some core (required) modules, which give
the minimum declarations that a document type always needs in order to
still, be HTML (or whatever language is being modularized), but most modules
are optional.  See:
http://www.w3.org/TR/xhtml-m12n-schema/schema_module_defs.html

XML Namespaces -- are simply URIs for a piece of XML, so that you can be
sure that a certain piece of data belongs to whatever language the URI says
it belongs to.

Disclaimer: This is glossary is in the process of being updated constantly.
Please contribute your ideas and definitions to jwnorris@humanmarkup.org

Notes On last Update (JWN):
****************************
1) rGlossary was spell checked
2) List of words was alphabetized
3) An introductary statement was made
4) Submissions were solicited from readers of the glossary for new
submissions, edits, and additions.


Cordially,

Joe Norris
HumanML_Write Facilitator
jwnorris@humanmarkup.org