[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Re: [wsrp] Default property type for setPortletProperties
Yes. The comment plus the encouragement to use xsi:type would make it clear. Thanks Subbu Rich Thompson wrote: > > Subbu, > > Would moving the comment about the default type (perhaps with > encouragement to always use xsi:type on Property.value elements) to > the Property section (5.1.16) alleviate your concerns? > > Rich > > > *Rich Thompson/Watson/IBM@IBMUS* > > 07/05/05 11:18 AM > > > To > wsrp <wsrp@lists.oasis-open.org> > cc > > Subject > Re: [wsrp] Default property type for setPortletProperties > > > > > > > > > > > This section deals with registration properties. I think it left this > room so that Consumers could always send a particular set of > properties, presumably to be ignored by most Producers. > > Rich > > *Subbu Allamaraju <subbu@bea.com>* > > 07/05/05 09:59 AM > > > To > wsrp <wsrp@lists.oasis-open.org> > cc > > Subject > Re: [wsrp] Default property type for setPortletProperties > > > > > > > > > > > > > Rich Thompson wrote: > > > > > I don't see where the use of xsi:type is required, could you provide a > > pointer? > > I have not checked this either. > > > Section 7.1.1 explicitly leaves room for the generation of properties > > not described by a ProperyDescription. Elsewhere we are silent about > > allowing undescribed properties (i.e. they are not prohibited) ... I > > think the default on the type was put in to cover the edge case of an > > undescribed property which did not carry an xsi:type attribute. > > Do you remember why it leaves room to skip descriptions in 1.0? > > Subbu > > > > > Rich > > > > > > *Subbu Allamaraju <subbu@bea.com>* > > > > 07/03/05 07:19 PM > > > > > > To > > wsrp <wsrp@lists.oasis-open.org> > > cc > > > > Subject > > [wsrp] Default property type for setPortletProperties > > > > > > > > > > > > > > > > > > > > Sec 8.12 has a sentence (from V1) that reads as follows: > > > > "Each property declaration includes a name and type (default = > > xsd:string)" > > > > This is a bit odd since getPortletPropertyDescription describes the > > property of each property, and the type is also included via the > > xsi:type attribute on the Property value. So, what is the purpose of > > saying that, by default, the property is of type xs:string? > > > > Any comments? > > > > Regards, > > Subbu > > > > --------------------------------------------------------------------- > > To unsubscribe from this mail list, you must leave the OASIS TC that > > generates this mail. You may a link to this group and all your TCs in > > OASIS > > at: > > https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php > > > > > > > --------------------------------------------------------------------- > To unsubscribe from this mail list, you must leave the OASIS TC that > generates this mail. You may a link to this group and all your TCs in > OASIS > at: > https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php > >
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]