Lists Home |
Date Index |
Seems right, Sterling. Note that critics of Grice equate that
to the Relevance Principle. The paper I cited critiques
Grice's Maxims but notes that they have a loose validity.
Pragmatics concerns itself with the implications of speech
acts within a context/situation. So in two examples from the web:
If I understand it, http is designed to make it possible to
use the network with the fewest assumptions and implications
about the content's meaning when accessed. If I access a
product page, the implication that I am buying a product,
and secondarily, transacting a charge against my bank acount
shouldn't be valid unless I explicitly order it. The
legal restriction that I can't truncate a URI to access
a resource is architectural nonsense because the system
is designed to work that way. So it is the responsibility
of the resource administrator to explicitly restrict access
because the architectural design implicitly declares any
content to be public unless explicitly restricted. The law
should reflect the technical reality and not attempt to
legislate against the grain of the architecture.
Pragmatics make the obligation of the speaker to be
clear and the obligation hearer to map to the intent of the speaker
a field of study. Is it useful (in the YAGNI sense)?
There possibly will be pragmatic layer systems (see the
papers of Aldo de Moor, et al) that are useful. There
are cases such as illustrated above that I think are
easily made using this subfield and applying it to
In short: I think it worth understanding technically
and in domains outside our technology. If, as Peter notes,
we have to have webPsychs to use the system, we may
be into YAGNI but given the webPsychos, maybe not.
From: me [mailto:firstname.lastname@example.org]
Sent: Friday, February 24, 2006 3:05 PM
Subject: [xml-dev] Mailmen, Post, intent, and Duck Typing
Mr. Bullard, I have reduced you fri, 24 feb 2006 post and attempted to
summarize it for my understanding. Please tell me if I have it right.
Cooperative Principle is a concept by Grice:
it says to be useful a taxonomy should classify and order its objects
ways which correspond to how it might be used?
to use it requires efficient methods to access the designed content:
operationally: simple primitives for hardware
functionally: assumptions about the presentation to the user
http verbs imply: efficient coding
SOAP implies efficient physical means to retrieve the content
identifiers ( metawords) imply search recognition efficiency
design effort: implies a worthy value on return to a search hit.
The xml-dev list is sponsored by XML.org <http://www.xml.org>, an
initiative of OASIS <http://www.oasis-open.org>
The list archives are at http://lists.xml.org/archives/xml-dev/
To subscribe or unsubscribe from this list use the subscription