WSIA 5/22/2002: [wsia][wsia-requirements][R905 and 601]

[Monica Martin <mmartin@certivo.net>]

On "Consumer with multiple Producers", this was a question to the WSIA.
If we see this or a similar requirement in the simple portal or
SmartBuyer scenarios, let's ensure we have captured the nature of the
requirement in our document.  On the list on the original email, I
attempted to separate the myriad of conditions/paths we seemed to be
identifying given the discussion on the elist.  Thanks for the
suggestion on the requirement. Rich Thompson also provided feedback.
Here is a combined suggestion that include everyone's requests. Comments
welcome.
 
A Consumer MUST be capable of being combining different Presentation
Fragments in a single document. Specification of restrictions MAY be
required for supported markup types or Presentation Fragments. When
used, any such specification of restrictions MUST be minimized.
Restrictions SHOULD be type specific. If a markup type (such as HTML)
mandates uniqueness of tokens in a single document, a page MUST be
composed in a way that guarantees uniqueness. In particular, multiple
Presentation Fragments generated by the same Producer SHOULD be capable
of being combined.
 
Thanks. Monica

	-----Original Message----- 
	From: Sean Fitts 
	Sent: Wed 5/22/2002 8:22 AM 
	To: Monica Martin; Rich Thompson; wsia@lists.oasis-open.org 
	Cc: 
	Subject: Re: WSIA 5/21/2002: [wsia][wsia-requirements][R905 and
601]
	
	


	Not sure that I parsed your notes correctly, but I see the
phrase
	"Consumer with multiple Producers?  Need justification."
Doesn't
	the simple portal scenario provide this?  If not, the
"SmartBuyer"
	scenario certainly does.
	
	Suggested rewording:
	
	Consumer's MUST be able to construct documents containing
multiple
	Presentation Fragments from one or more Producers.  The
specification
	MAY place restrictions on the supported markup types or
Presentation
	Fragments.
	
	
	I don't think we need to say any more than this.  Other
requirements
	about the division of labor between Consumer and Producer will
guide
	the specific mechanisms provided to support this requirement.
	
	Sean
	
	At 05:43 PM 5/21/2002 -0700, Monica Martin wrote:
	>Several ideas:
	>
	>Composition of presentation fragments onto a page
	>
	>Composition of different presentation fragments onto a page
	>
	>Composition of different presentation fragments generated by a
producer
	>(May be the same as above)
	>
	>Restrictiions on presentation fragments (or markup types)
	>
	>Guarantee uniqueness of tokens in a single document defined by
the
	>presentation format
	>
	>
	>
	>
	>
	>E905 and E601
	>
	>Notes: [mm1: Namespace entity rewriting Javascript; Consumer
with
	>multiple Producers? Need justification. Include with
presentation
	>fragments (Consumer passes Producer a key).]
	>
	>
	>
	>Suggested text:
	>
	>Different Presentation Fragments SHOULD be capable of being
combined in
	>a single document. Restructions MAY be specified on markup
types or
	>Presentation Fragments.  In particular, if a presentation
format (such
	>as HTML) mandate uniqueness of tokens in a single document, a
page
	>SHOULD be composed in a way that guarantees uniqueness. In
particular,
	>Presentation Fragments generated by the same Producer SHOULD be
capable
	>of being composed.
	>
	>
	>
	>Comments and arrows welcome.
	>
	>Thanks.
	>Monica J. Martin
	>
	>Program Manager
	>
	>Drake Certivo, Inc.
	>
	>208.585.5946
	>
	>
	>
	>         -----Original Message-----
	>         From: Rich Thompson
	>         Sent: Fri 5/17/2002 1:33 PM
	>         To: wsia@lists.oasis-open.org
	>         Cc:
	>         Subject: [wsia][wsia-requirements][R130]
	>
	>
	>
	>         Here are the modified requiremetns documents ... the
'a' version
	>is prior
	>         to accepting changes and rearranging the requirements
by
	>functional
	>         categories. In addition to those changes, the 'b'
version has
	>consistent
	>         capitalization of words like 'MUST' and Consumer. I
also noted
	>and
	>         implemented the global change of 'property' to
'context data'.
	>
	>         (See attached file: WSIA reqs 2002-05-17a.doc)(See
attached
	>file: WSIA reqs
	>         2002-05-17b.doc)
	>
	>         Requirements still needing attention include:
	>               R201
	>               R203
	>               R130
	>               Overlap between R601 & E905
	>               Overlap between R702 & E904
	>               Monica's recent email:
	>                  WSIA Web Services SHOULD provide the
capability for
	>those
	>                  Presentation
	>                  Fragments, returned by the Producer, can be
requested
	>and relayed
	>                  through the Consumer.
	>                  WSIA Web Service SHOULD provide the
capability for
	>Presentation
	>                  Fragments to reference end-user requests for
external
	>resources.
	>
	>
	>
	>
	
>----------------------------------------------------------------
	>To subscribe or unsubscribe from this elist use the
subscription
	>manager: < http://lists.oasis-open.org/ob/adm.pl>