Group: programming
Topic: attribute-value pairs as information
Topic: computational mail
Topic: data record
Topic: electronic mail headers
Topic: examples of coordination systems
Topic: help in UserInterface
Topic: implementing distributed systems and applications
Topic: information filters
Topic: parameter passing by message
Topic: problem of information overload
Topic: responses to electronic mail
Topic: semi-structured text
Topic: text markup and structured text
Topic: translation of data
Topic: XML schemas
| |
Summary
A semistructured message contains markup that can be used for automatic processing. For example, email contains headers that list a subject line, the sender, and the receipient. A filter can use this information to automatically reject a message or move it to a mail box.
With XML, more information is available for processing. Processing is more reliable if a schema validates the XML. (cbb 3/07)
Subtopic: coordination
Quote: automatic filtering/routing of email is immensely valuable; especially for advisory and bug-handling organizations [»boreNS9_1988]
| Quote: semistructured messages are useful; particularly for group coordination and communication systems [»maloTW4_1987]
| Subtopic: flexibility
Quote: semistructured messages increase flexibility by allowing nonstandard communications [»maloTW4_1987]
| Subtopic: processing messages with structured templates
Quote: InformationLens provides structured templates with alternatives and rules for receivers to automatically filter and classify mail [»maloTW4_1987]
| Quote: semistructured messages enable automatic processing by encouraging senders to use structured information [»maloTW4_1987]
| Subtopic: message type
Quote: local augmentation for semi-structured messages--local document types specialize the lower levels of a shared type hierarchy [»leeJ3_1988]
| Quote: to combine XML processing components reliably, it is essential to verify their inputs and outputs; most components do not accept arbitrary XML documents [»vandE_2004]
| Subtopic: translating between type hierarchies
Quote: if two groups share some views then can automatically translate mismatched views to a shared, parent view
| Quote: want to translate between type hierarchies for semi-structured messages; preserve meaning while allowing autonomy for different groups [»leeJ3_1988]
| Quote: if translate between type hierarchies for semi-structured messages, need to notify other groups of changes [»leeJ3_1988]
| Quote: a view of semi-structured messages is a set of message types and their relations; no translation needed if the same [»leeJ3_1988]
| Subtopic: examples, alphabetical
Quote: Agenda can define actions that execute when an item is added to a category
| Quote: Agenda can assign conditions for automatically adding items to a category [»kaplSJ7_1990]
| Quote: Agenda can tentatively assign an item to a category
| Quote: GenBank satellite databases are updated by email submissions similar to researcher submissions [»cinkMJ5_1991]
| Subtopic: programs over frame hierarchies
Quote: ZOG integrates programs with frames; the global consistency helps novices
| Subtopic: manual sort
Quote: Andrew's Advisor system now sorts incoming mail by day; students process one day's messages and cross-post those they miss [»boreNS9_1988]
| Quote: with human message sorting, Advisor can use fine-grained helpboxes that contain real requests; high-content and worth reading [»boreNS9_1988]
| Subtopic: problems with automatic processing
Quote: automatic message generation can lead to chain reactions; prevent by aging, time-outs, or absorption; e.g., cyclic forwarding [»manbU10_1990]
| Quote: no automated routine can distinguish useless from relevant communications; especially when a user's tasks and interests change [»hiltSR7_1985]
| Quote: Agenda's program-initiated actions can cascade and surprise users who continually fine-tune their database [»kaplSJ7_1990]
| Quote: Andrew's Advisor system first tried automatic filing of messages by subject; 50% misclassification, too cluttered [»boreNS9_1988]
|
Related Topics
Group: programming (339 topics, 10149 quotes)
Topic: attribute-value pairs as information (57 items)
Topic: computational mail (11 items)
Topic: data record (57 items)
Topic: electronic mail headers (3 items)
Topic: examples of coordination systems (23 items)
Topic: help in UserInterface (33 items)
Topic: implementing distributed systems and applications (41 items)
Topic: information filters (22 items)
Topic: parameter passing by message (31 items)
Topic: problem of information overload (23 items)
Topic: responses to electronic mail (11 items)
Topic: semi-structured text (17 items)
Topic: text markup and structured text (25 items)
Topic: translation of data (26 items)
Topic: XML schemas (16 items)
|