Re: issue 168 proposal: xsi:type of external references in Encodi ng (fwd)

Sounds good to me, thanks.

Jean-Jacques.

Noah Mendelsohn wrote:

> Proposed further clarifications set off in >> ..<<:
>
> "This specification does not constrain the type of resource that can be
> referenced through the <att>href</att> attribute information item. In the
> case
> of an XML resource, the type MAY be defined by the <att>xsi:type</att>
> attribute information item >>on the referenced resource<< or by an
> associated
> XML Schema >>(note, however that schema validation of referenced resources
> is
> OPTIONAL)<<. For non-XML resources, other typing means >>MAY<< be used,
> although the specification of such typing means is outside the scope of
> this
> specification.  >>When no such type information is available, the
> referenced
> resource is considered to be 'untyped'.<<"
>
> I'm not 100% comfortable with the last part, but if we're mapping from
> serializations to graphs, and if graph nodes are generally typed, we have
> to say something about the interpretation in the case where no type
> information is available.  I'm more or less convinced that the other
> changes proposed above are desireable.
>
> ------------------------------------------------------------------------
> Noah Mendelsohn                                    Voice: 1-617-693-4036
> Lotus Development Corp.                            Fax: 1-617-693-8676
> One Rogers Street
> Cambridge, MA 02142
> ------------------------------------------------------------------------
>
> "Jean-Jacques Moreau" <moreau@crf.canon.fr>
> Sent by: xml-dist-app-request@w3.org
> 12/20/01 07:51 AM
>
>
>         To:     "Champion Mike" <Mike.Champion@SoftwareAG-USA.com>
>         cc:     xml-dist-app <xml-dist-app@w3.org>
>         Subject:        Re: issue 168 proposal: xsi:type of external references in Encodi       ng
>   (fwd)
>
> Mike, thanks for your input. I would suggest further amendments to your
> text,
> and in particular removing the second sentence since typing information
> may be
> provided outside the target resource, for example directly within the SOAP
> enveloppe, even for non-XML resources albeit in a non-standard fashion:
>
> "This specification does not constrain the type of resource that can be
> referenced through the <att>href</att> attribute information item. In the
> case
> of an XML resource, the type MAY be defined by the <att>xsi:type</att>
> attribute information item or by an associated XML Schema. For non-XML
> resources, other typing means need to be used, although the specification
> of
> such typing means is outside the scope of this specification."
>
> Jean-Jacques.
>
> "Champion, Mike" wrote:
>
> > Here's a quick attempt at translating it into spec-ese:
> >
> > "The SOAP 1.2 specification does not constrain the type of resource
> > referenced by the href attribute. It is the responsibility of the target
> > resource to define any type information.  In the case of XML, the type
> can
> > be defined by an XML schema associated with the target resource, or by
> the
> > xsi:type information item.  For non-XML target resources, other means to
> > define the type will have to be provided outside the SOAP framework."
> >
> > Use, revise, or ignore as you see fit ...
> >

Received on Thursday, 20 December 2001 12:05:52 UTC