RE: [AMG] Figure 2.1 suggested revision.

Hi all,

	XMLP Service Consumer could be more descriptive. And of course the
relationship is many to many.

cheers

|-----Original Message-----
|From: xml-dist-app-request@w3.org [mailto:xml-dist-app-request@w3.org]On
|Behalf Of Williams, Stuart
|Sent: Wednesday, March 14, 2001 1:26 AM
|To: 'Jean-Jacques Moreau'
|Cc: Henrik Frystyk Nielsen (E-mail); John Ibbotson (E-mail); Krishna
|Sankar (E-mail); Lynne Thompson (E-mail); Marc Hadley (E-mail); Mark A.
|Jones (E-mail); Martin Gudgin (E-mail); Nick Smilonich (E-mail); Oisin
|Hurley (E-mail); Scott Isaacson (E-mail); Yves Lafon (E-mail);
|'xml-dist-app@w3.org'
|Subject: RE: [AMG] Figure 2.1 suggested revision.
|
|
|Jean-Jacques,
|
|Where I was coming from is that gradually the notion of a
|'client'/'user' of
|the XML protocol seems to be ebbing out of our glossary. It is a concept
|that I think is important not least beacuse to some it extent it delineates
|the boundary between the provider of XMLP and the user of XMLP. In doing
|this it also sets the boundary on what needs to be defined in the specs. we
|develop.
|
|The recent rewording around handler has removed references to "XML protocol
|application" and the two proto definitions for "XML protocol processor" now
|place responsibility on the processor to invoke the handlers. In
|the process
|we loose the notion of a thing that 'uses' the XMLP layer and/or some
|(logical) container for a collection of handlers at a node. The suggested
|revisions to the diagram were an attempt to reflect the recent glossary
|changes.
|
|Personnally I would prefer not to loose the concept of a user/client of the
|XMLP layer and I was reasonably comfortable with it as a container for a
|bunch of handlers. If "XMLP Application" is not a good terms for that
|concept, and there seems some reluctance to accept the term, then
|lets think
|of a new name for it. We've had:
|
|	Layer Client
|	XMLP Service user
|	XMLP Application
|
|My personal favorite remains Layer Client... but it seemed to cause
|confusion for some.
|
|Stuart
|
|> -----Original Message-----
|> From: Jean-Jacques Moreau [mailto:moreau@crf.canon.fr]
|> Sent: 13 March 2001 10:47
|> To: Williams Stuart
|> Cc: Henrik Frystyk Nielsen (E-mail); John Ibbotson (E-mail); Krishna
|> Sankar (E-mail); Lynne Thompson (E-mail); Marc Hadley
|> (E-mail); Mark A.
|> Jones (E-mail); Martin Gudgin (E-mail); Nick Smilonich (E-mail); Oisin
|> Hurley (E-mail); Scott Isaacson (E-mail); Yves Lafon (E-mail);
|> 'xml-dist-app@w3.org'
|> Subject: Re: [AMG] Figure 2.1 suggested revision.
|>
|>
|> "Williams, Stuart" wrote:
|>
|> > Basically, I've been trying to match the picture with our
|> eveloving glossary
|> > definitions. What I've done is to 'pull' the handlers back
|> inside the XML
|> > protocol layer and dispatch them directly from the XML
|> protocol processors.
|>
|> I tend to see handlers as belonging to the application space,
|> as Henrik, and hence it feels funny to
|> see them down below the XPLayer. Aren't you actually looking
|> for a new service provided by that layer,
|> ie dispatching to handlers, and if so, shouldn't you
|> introduce instead a new primitive (or adapt an
|> existing one)?
|>
|> Jean-Jacques.
|>
|
|

Received on Wednesday, 14 March 2001 10:39:11 UTC