W3C home > Mailing lists > Public > w3c-wai-hc@w3.org > July to September 1997

RE: regarding Dictionary and RDF

From: Pawson, David <DPawson@rnib.org.uk>
Date: Thu, 25 Sep 1997 08:12:56 +0100
Message-ID: <81B329C63AEFD0119929006097AB82E40422C3@priory.rnib.org.uk>
To: w3c-wai-hc@w3.org
to follow up on what Daniel Dardailler said:

I agree we want to arrive at a requirement statement.

I still want some worked examples.
	- how browser recognizes that a dictionary is useful w.r.t.
	an HTML document without explicit mention in document.
DP: Suggest we tackle this on a default then priority basis.
	1. Default, left to stylesheet to determine (since the
knows the 'customer' capability -e.g. I am clever, I can deal with
this through to I don't know what to do with this, help me browser.
	2. Author intent. I would like the reader to use dictionary X,
	  knowing from the content the difficulties that may arise
	3. Browser does its best.

	- how author indicates that a dictionary is to be preferred
	for a specific use w.r.t. current document (, current entity).

DP: 	As above, for the entity being dealt with, ?? using some
	      characteristic. Indication that a dictionary is necessary 
		for this item

	- how browser detects text resources associated with an

DP:	 Bottom of the ladder. No one else has suggested how it might
	be interpreted, hence I must. This also caters for the lazy

	- how does the author community converge on a taxonomy for
	distinguishing different text resources associated with the
	same image in a widely-recognized way?

DP: How about putting a scoped indirect interpretation. The author
	scope is that of layer one - he/she knows about major routes
	only. The stylesheet world uses that selection, in the knowledge
	what the customer wants and has available. This keeps the author
	input 'simple' in terms of an n way switch, permitting the
	interpretation the flexibility to grow with technology to
	more and more 'routes' to resources.
Regards, DaveP
Received on Thursday, 25 September 1997 03:10:17 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 20:35:00 UTC