OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help

wsrp-interfaces message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]

Subject: [wsrp-interfaces] [wsrp][interfaces] 8/8 Agenda

Both to follow Thomas' lead and because I thought I heard Rich mention
he is mostly focused on the details of what is currently specified vs.
dealing with new issues, I suggest we use the discussion tomorrow to
start to analyze and clarify the .3 draft.  For tomorrow let's focus on
getdescription() and registerconsumer().  I have attached a list of
questions I generated during my review today to stimulate the
discussion.  The goal is to understand what parts are understood and
agreed to vs. still up for discussion vs. isn't addressed yet by the
spec but will likely need to be (i.e. currently pending/deferred).

Conference call details remain the same:
8am PDT
ID: 8814427


Problem:  getDescription(entity) has no way of knowing if the consumer is registered.  We can get Unregistered attacks.  Is this okay?

Problem:  Don't we want modes/viewstates to be extensible -- i.e. a string not a bit-vector?

Question:  Why do entities have WSDLs as they aren't services?  I.e. what is the wsdl url of an entity?

Question:  Why is registrationData a property list?  Why shouldn't the bulk of this be typed like the entity information?  Put another way, what are the standard set of properties we define?  Are there some that we perdefine as required?

Question:  Do we care about allowing the consumer to ask get me the description of all the entities that this user has access to?  I.e. should the producer be able to restrict the description based not only on whether the consumer is registered but also who the user is (what role)?

Question:  What is the intended use of name field defined in EntityType?  Is it needed now that we have entityHandle?

Question:  Can/should the consumer be able to pass a list of locales it wants results in?  To minimze lookup/processing/size?

Question:  Do we need to state that the order of the values in the locale based arrays are tied to the order in the locales fields?

Question: Are entityProperties restricted to persistent state -- I assume not given scope is in the definition?  However don't we need a bunch more information then this if a consumer is going to render the edit screen for a producer?  How is this extra information passed?

Question:  Do we need to distinguish between short and full titles?

Question: Do we need to allow locale based keywords?

Question:  Do we need to allow a consumer to pass "capabilties" to the getDescription so the producer can "negotiate"/"resolve" its behavior/description?  I.e. negotiate who manages the persistent store?  Needed for simple producers that don't support registration???

Question:  Should we remove "cacheability" until we get around to defining caching?  I.e. define those things we know and keep a list of those things still to be discussed?  I.e. like URL erwrieting etc?

Question:  We would like the portlet to return a flag indicating whether it uses [entity] sessions or not.  Usage:  Portal can distinguish for its page developers portlets that may perform differently on the page.

Property data type:

Problem:  Should we overload "Property" definition as we currently do?  I.e. should we have a simpler datatype Property that merely has name, type, value and a second derived type that deals with scope/required?  I.e. distinguish between places in the protocol we just want an AVList vs. where properties are actually being defined?

Question:  How are array types passed as "strings" I.e. what is the form of an array -- comma separated???

Question:  From a WSRP perspective, why isn't the default scope "Entity" rather then "session"?

Question:  What are the valid values of "scope"?

Question:  What does required mean?


Question:  Why do you state "registrationData ... MUST match that which the Producer declared in response to getDescription()"?  Shouldn't the consumer only have to supply the "required" elements?  Shouldn't they be allowed to oversupply here as well i.e. pass there extensions?

Question:  Should the following paragraph page 16:23 read "The Consumer MAY persistently store the consumerHandle"?

ConsumerContext data type:

Question:  Why is userID in here?  Shouldn't it be a User "object" that contains the ID, roles, and another object that refs to the "profile" information?

Question: Is "sendTransparentState" needed?  It only seems to apply to setProperties.

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]

Powered by eList eXpress LLC