RE: Proposal for solving XOP/MTOM rec issues
"Martin Gudgin" <[email protected]>
| Newsgroups | gmane.text.xml.distributed |
|---|---|
| Message-ID | <DD35CC66F54D8248B6E04232892B633806FC58BF@RED-MSG-43.redmond.corp.microsoft.com> |
[inline] Gudge > -----Original Message----- > From: [email protected] > [mailto:[email protected]] On Behalf Of Hervé Ruellan > Sent: 14 September 2005 08:19 > To: [email protected] > Subject: Proposal for solving XOP/MTOM rec issues > > > Dear all, > > I've just check the current issues against XOP, MTOM and RSHB > recs. Here > are some draft proposal for resolving them. > > 34rec > ----- > "startinfo" parameter. > > I found one occurence of "startinfo" instead of "start-info" > in XOP and > one in MTOM. > > I think that in both cases these should be changed to "start-info". +1 > > 35rec > ----- > "action" parameter examples. > > There are two examples in XOP where the "action" parameter value is a > relative URI. > > I think that in both cases the value should be changed to an absolute > URI as specified in the SOAP spec. +1 > > Comment at [1] > -------------- > Possible defect in XOP. > > The commentator thinks that the language used to describe the > conditions > for an element information item to be optimized does not > specify clearly > that such an element information item must have only character > information items in its [children]. > > I think that the language used specify that the element > information item > must only have character information items in its [children]. > However, > this could be made explicit by adding a note in XOP 3.1 and > in MTOM 2.3.1. I also believe the current language is sufficient. But I would not be averse to adding clarifying text. > > Regards, > > Hervé. > > [1] > http://lists.w3.org/Archives/Public/xmlp-comments/2005Aug/0004.html > > > >