Having problems with message search?
Good write up on the working list. I have some work to do here.
<len>
fewest bags'oSemantic with them when
referenced. The semantic levels are the tough part of
this because we can add globals almost endlessly. We
should practice parsimony and as in RDF get very good
at writing very prescise <rdf:description> nodes.
</len>
referenced. The semantic levels are the tough part of
this because we can add globals almost endlessly. We
should practice parsimony and as in RDF get very good
at writing very prescise <rdf:description> nodes.
</len>
<ranjeeth>I am curious what you meant...I am assuming you mean that semantic meta information shouldn't be haphazardly included (rather, it should be methodically included).</ranjeeth>
I meant that a precise and concise description is very hard to
write. When the semantic or process for using the
node is described rather than given explicitly, the
interpretation becomes interpretable. And so on
to madness and shouting. :-) Even the simplest
description gets tortured. I just got the editorial comments
on the Golem article; it is tough to get past a good
editor and Sperberg-McQueen is a very good editor.
So, back to the forge for Len....
For all of its formality, an RDF is an opinion and so is a schema.
My appeal to the authority of the semioticians is to get an opinionated
framework for which we can comfortably assume
others have already done the required shouting.
It's a start, or as Sean has seen me write before,
a suitable means to start the fight. To integrate with
the other initiatives, we have to cleanly keep our framework
inside a boundary for precisely what it describes and don't
attempt to coordinate their work. XML schema design can be
like planting pine trees: they grow fast and kill every
other plant in their vicinity, and like planting Kudzu, can
become so entwined it takes fire to kill off the surface
growth, and poison so strong to kill the roots, nothing
else grows there.
In other words, don't create complex barriers to competition; enable simple
bridges to allies. HumanML should be a simple bridge.
HumanML concerns itself with the "human" aspects
of communication, but that will be insufficient circumscription
since anything done with markup has a human aspect.
I suspect we will find the sweet spot in the
markup and authoring of genre at the high
organizational end, and gestures at the primitives
with emotional states being the middle level .
Unlike TEI, we are not exclusively focused on
texts; we are taking on the challenge of emotional
descriptions to enable transformation into
rendered versions and annotation for stored
versions. In short, provide a trusted means to
markup the interpretive process.
o Reduce miscommunication through a
standard framework of referents to descriptions
of emotional states
o Enhance communication by enabling emotional
states to be identified and used to query if requests and
responses do not conform to predicted ranges for
sequence and frequency within a genre.
o Create communication through authoring tools
that use genre-based schema to organize sequences
and frequencies of emotional expressions
If we plan to do less, we will have less to do.
Len
http://www.mp3.com/LenBullard
Ekam sat.h, Vipraah bahudhaa vadanti.
Daamyata. Datta. Dayadhvam.h
-----Original Message-----
From: Ranjeeth Kumar Thunga [mailto:rkthunga@...]
Sent: Monday, February 26, 2001 10:42 AM
To: humanmarkup@yahoogroups.com
Subject: [humanmarkup] HumanMarkup and other InitiativesWe are starting out by creating a focused framework, which Len will be providing through the first draft schema for. >From the article on language creation that he provided, there seem to be two crucial points 1) A hastily designed new language could cause irreparable problems later on as the language develops 2) the *design pattern* for the growth of a language is more important than the *actual development of the language* itself.This initial Schema would provide the basic design set for future growth into a broad set of initialtves. There are a lot of possible directions under the humanmarkup scope--all of them are focused around this single purpose. It would be beneficial for interested parties within these initiatives could be able to lead discussion in the future on how to inculcate human characteristics within the various current XML initiatives.Here is a working list to start with:================HumanMarkupPURPOSE: reduce human miscommunication and enrich human communication, through XMLInterrelations with other endeavors:Text Encoding Initiative: Embed human characteristics within the framework of encoding meta-information in the written word.FLBC/KQML (formal language for business communication):Interact with current agent based systems for communication, to possibly integrate their standards in communication, or vice versa.WAI:-Provide standards for textual/non-textual conveyance of human qualities through markup-Provide standard paradigms for communication settings-Create a data model for communication constructs, including 'purpose', 'main-point', and 'to-do'Semantic WebEmbed semantic information relating to the human qualities of the communication-eg. how do the main points in the speaker's statements correlate to his argument-eg. what is the emotional force behind the 'warning' the speaker gave regarding failure to perform-eg. what are the questions that the supervisor asked of usXML Fragment Interchange:-How to address communication scenarios in which there are no formally defined scenario or genre(ex. a passing 'shout out', a casual 'whisper', or a glance from afar)RDF: Formally provide a description of the communicators, the setting (or genre), and the formal purpose of each communication sessionXML Protocol: Provide a system of communicating human thoughts and ideas through the same request/response systems currently used in system-system communications.XML Query: Determine various ways to extract a particular message out of a communication stringe.g. Did George Bush really answer the question as to whether he was going to raise taxes...if so, what did he say?e.g. Which times did the opponent answer all the questions...which time did the opponent dodge the questions?
To unsubscribe send an email to:
humanmarkup-unsubscribe@yahoogroups.com
Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service.
Send Email