I think they don't define it because it is a common well known (to them)
idea that is used across many specs.
Here is a quick definition I found:

So if the user agent is FOP (+ how the document is eventually viewed)
then the values and decisions are determined by FOP.
My point is that these are typically things that *may* take one value or
another so we should allow users of FOP to alter what values are used.


On Thu, 2002-06-06 at 03:59, Peter B. West wrote:
> Keiron,
> You have nicely summarised the references to the user agent in the spec 
> (except for the first one, invalid markup error handling, which I think 
> you have added.)  However, my problem with the notion in the spec of 
> user agent remains.  The authors have never bothered to define it, and 
> we are left to work out what, exactly, it is from the various 
> references.  The references that we have - certainly the references to 
> non-interactive agents - are all to configuration items.  At the moment 
> these things are, as I said, in the XML files.  It would, prima facie, 
> be straightforward to get this from the configuration, in whatever form 
> that eventually takes, whether we continue to use the XSLT, or introduce 
> the properties into the CVS tree.  I.e., whatever form the expression of 
> the properties takes, we would need to extract certain key property 
> values from the configuration.
> Assuming that we have no plans to go into the interactive presentation 
> business as yet, we can disregard the interactive elements.  Even where 
> an interactive agent would presumably expose the options for 
> modification, those elements would still require initial values.  For 
> our purposes, I think that "user agent" functions should be merged into 
> configuration.
> Incidentally, I think the multi-properties, title and hot links elements 
> should be in the "Interactive" list.  The aural properties 
> (pause-before, pause-after, voice-family) are not necessarly 
> interactive.  It would be quite feasible to produce an audio file 
> rendering of a document within FOP.
> Peter

To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]

Reply via email to