Web services

[Mikael Karlsson]

No,
they map W3C XML Schema (XSD) to ASN.1 schema.
/Mikael

Example from the first reference page 
http://java.sun.com/developer/technicalArticles/WebServices/fastWS/


<xsd:complexType name="ComplexTypeSimple">
  <xsd:sequence>
    <xsd:element name="varBoolean" type="xsd:boolean"/>
    <xsd:element name="varInt" type="xsd:integer"/>
    <xsd:element name="varString" type="xsd:string"/>
  </xsd:sequence>
</xsd:complexType>
<xsd:element name="paramRefComplexTypeSimple"
    type="xsd1:ComplexTypeSimple"/>

becomes:

ComplexTypeSimple ::= SEQUENCE {
  varBoolean BOOLEAN,
  varInt INTEGER,
  varString UTF8String
} 

ParamRefComplexTypeSimple ::= ComplexTypeSimple

måndag 07 november 2005 23:26 skrev Tony Rogvall:
> 7 nov 2005 kl. 23.03 skrev Mikael Karlsson:
> > Interesting!
> >
> > It seems also that some discovered that sending those XML messages
> > on the line
> > take some bandwidth and processing power for binding (oops what a
> > surprise)
> > so there is a proposal for "Fast Web Services" which in practice
> > seems to be
> > an ASN.1 representation of XML Schema.
> > Since Erlang has an ASN1 encoder/decoder this might be something to
> > look
> > closer at.
>
> If they do it the XML way (with out reading) they MUST surely embed
> the XML string
> into the request. The addition of the isWBXML flag is my own
> invention to make the
> size of the PDU a LOT smaller...
>
> Request ::= SEQUENCE
> {
> 	isWBXML	BOOLEAN,
> 	data	 OCTET STRING	 -- Put you XML or WBXML request data here
> }
>
> Response ::= SEQUENCE
> {
> 	isWBXML	BOOLEAN,
> 	data	 OCTET STRING	 -- Put you XML or WBXML response here
> }
>
> This is very similar to how Nokia is using Corba/Java RMI in the NPS
> (Nokia Profile Server)
>
> 	String resolve (String request, String sessionID)
>
> The request is of course XML and the response is... XML
>
> /Tony
>
> > Refs:
> > http://java.sun.com/developer/technicalArticles/WebServices/fastWS/
> > http://asn1.elibel.tm.fr/xml/fws.htm
> > http://asn1.elibel.tm.fr/xml/tutorial-fws.htm
> >
> > /Mikael
> >
> > måndag 07 november 2005 10:33 skrev Joe Armstrong (AL/EAB):
> >> How about rnc? - I have a relax NG verifyer (in Erlang)
> >> which I might be persuaded to part with.
> >>
> >> /Joe
> >>
> >>> -----Original Message-----
> >>> From: owner-erlang-questions@REDACTED
> >>> [mailto:owner-erlang-questions@REDACTED]On Behalf Of Ulf Wiger
> >>> (AL/EAB)
> >>> Sent: den 7 november 2005 09:37
> >>> To: chandru; Anindya Mozumdar
> >>> Cc: erlang-questions@REDACTED
> >>> Subject: RE: Web services
> >>>
> >>>
> >>>
> >>> One thing notably missing in this regard is support for
> >>> XMLSchema.
> >>>
> >>> Any takers?  (:
> >>>
> >>> /Uffe
> >>>
> >>>> -----Original Message-----
> >>>> From: owner-erlang-questions@REDACTED
> >>>> [mailto:owner-erlang-questions@REDACTED] On Behalf Of chandru
> >>>> Sent: den 7 november 2005 09:18
> >>>> To: Anindya Mozumdar
> >>>> Cc: erlang-questions@REDACTED
> >>>> Subject: Re: Web services
> >>>>
> >>>> On 07/11/05, Anindya Mozumdar <anindya@REDACTED> wrote:
> >>>>> Hi,
> >>>>>     I am relatively new to both Erlang and Web Services, so
> >>>>
> >>>> pardon my
> >>>>
> >>>>> rather silly question - Are there are any
> >>>
> >>> API's/implementations in
> >>>
> >>>>> Erlang for Web Services (SOAP, WSDL and UDDI), like the
> >>>>
> >>>> ones readily
> >>>>
> >>>>> avaiable in Java ?
> >>>>
> >>>> There is a basic soap-client and soap-server written by
> >>>
> >>> Erik Reitsma.
> >>>
> >>>> I have version 0.2 of it and I can send it to you if you want
> >>>> it. But it is quite basic. The good news is that the most of
> >>>> the tools you need to build Web Services are already
> >>>> available :-) You have yaws/inets for a webserver,
> >>>> ibrowse/inets for a HTTP client and xmerl for XML parsing.
> >>>> You just have to implement the bits you need from various
> >>>> standards :-)
> >>>>
> >>>> cheers
> >>>> Chandru