[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]
Subject: [humanmarkup-comment] HM.DipCom: use-cases, contacts
|
A
codelist, as you mentioned during a past TC meeting, would be important to get
in order to work into HumanML. Much of this, or
all of this, would fall into signs and rules for combining these signs.
Semantic noise, I am inferring, are aspects of communication that may
still be represented within HumanML, and still need to be addressed, but may not
be apparent within a formal diplomatic codelist...am I on
target?
Before
a codelist, it may be helpful to flesh out a couple of very specific use-cases,
specifically as you mentioned in the past a way for an offline way of
gathering and interpretig diplomatic data perhaps. I remember going
through this exercise in the past, and what I have been finding in my own work
is that this process is critically important. It will be a good way to
think clear about this topic, as its hard to extract requirements when a
clear vision isn't in mind. If someone would like to develop a use-case,
that would be wonderful.
Finding resources establishing a DipCom systems
might be good place to start. The books that you had found Len are not
terribly expensive, and could be a good review. There were several
contacts that Owen had provided me a while back who I could provide expertise in
this regard. Additionally, with the State Department being a formal member
of OASIS, they would probably be more than happy to oblige. I will
have to hold off at least a bit longer with establishing contacts
for DipCom, unless someone would like to run with it right
now.
Ranjeeth Kumar Thunga
-----Original Message-----
From: Bullard, Claude L (Len) [mailto:clbullar@ingr.com] Sent: Wednesday, August 21, 2002 2:01 PM To: 'Joseph Norris'; OASIS Comment Subject: RE: [humanmarkup-comment] HM.diplomatic_communications.requiremen ts First,
cultures, media types, ideologies, etc. are domains of codes.
One
can define the domain in terms of its codes. Code systems
are
synonymous with vocabularies.
Codes have sign systems that have both signs and rules for combining the
signs correctly. The rules include structural rules (grammar,
syntax)
and
linguistic rules (which combinations of signs make "sense" or
convey
a useful relationship).
One
has to note that analysis of communication behavior, that is to infer intent,
requires
analysis of the source's decisions of code choices, perhaps within the
framework of
the
communication protocol, or in short, why was a particular code or
sign
chosen
among others. A coding protocol sets expectations and the
the
codes used should not violate expectations. If they do, then it is time to
evaluate and perhaps, renegotiate. At the very least, a
surprise should be
responded to with "What?" unless conveying surprise is part of the
code. Otherwise, surprise creates semantic
noise.
Aspects of code use that can create semantic noise are such
things as:
1. Competence. Is the code user capable of using the code
correctly
(according to the rules for the code). This is both selecting
the
correct code and interpreting a code correctly.
2. Emphasis. Is the code emphasizing the right part of the
message.
3. Attitude toward other party(ies). Does the attitude of the
user include such preconceptions
as
dominance over the receiver or vice versa?
4. Attitude toward message. Perceived value of
message.
First
you need the codes themselves. The use of HumanML should enable
the
formal construction of these codes with container domains that can
be
invoked to create the right "inflection" for the message as well as
aid in
interpretation and analysis.
len
--- --- |
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]
Powered by eList eXpress LLC