I argue that the same points we made when we chose to inline the resources
and not put a URL are also equally applicable here.
I argue against this. Rich, Andre - what exactly is the crux of the problem?
Maybe we can change the schema of the "schema" element to something else so
that things _will_ work?
Gil
-----Original Message-----
From: Rex Brooks [mailto:]
Sent: Wed, December 18, 2002 16:01
To: Rich Thompson;
Subject: RE: [wsrp-wsia] [I#202] The field schema in Modeldescription
has no WSDL encoding
Importance: Low
Yes, please. Anything that contributes toward businesses and
institutions, especially standards bodies, achieving a common best
practice for schemaLocation is IMHO a very good thing.
Ciao,
Rex
At 8:49 AM -0500 12/18/02, Rich Thompson wrote:
>Part of what Andre is commenting on is that the wsdl subgroup is dropping
>the schema element for v1 as the current stacks do not deal with it well.
>An attribute that points to an external schema would be a good replacement
>for v1 ... I would propose it be called schemaLocation as it has been in
>several other specs.
>
>Rich Thompson
>
>
>
>
>Gil Tayar <>
>12/18/2002 04:49 AM
>
> To:
> cc:
> Subject: RE: [wsrp-wsia] [I#202] The field schema in
>Modeldescription has no WSDL encoding
>
>
>Sorry - I should have made that clearer - if the status is "Active" and
>not "Tentative Resolve" or "Resolved", then the "Resolution" is just
>something proposed by the issuer, or maybe by somebody else.
>-----Original Message-----
>From: Andre Kramer [mailto:]
>Sent: Wed, December 18, 2002 11:43
>To: 'Gil Tayar';
>Subject: RE: [wsrp-wsia] [I#202] The field schema in Modeldescription has
>no WSDL encoding
>
>The "Resolution:"s in my new issues, of course, should all be a
>"Proposal:" for discussion.
>
>regards,
>Andre
>-----Original Message-----
>From: Gil Tayar [mailto:]
>Sent: 18 December 2002 09:05
>To:
>Subject: [wsrp-wsia] [I#202] The field schema in Modeldescription has no
>WSDL encoding
>
>Issue: 202
>Status: Active
>Topic: interface
>Class: Minor_Technical
>Raised by: Andre Kramer
>Title: The field schema in Modeldescription has no WSDL encoding
>Date Added: 18-Dec-2002
>Document Section: v0.85/7.1.9
>Description:
>The Schema type in ModelDescrition has no good representation in WSDL and
>no value as an ANY.
>Resolution:
>"Use a url to point to a schemafilename.xsd file containing a XML schema
>document.
><attribute name=""shemaURL"" type=""xsd:string"" use=""required""/> [In
>practice, can't use schemaLocation and anyURL is broken in JAXRPC.] The
>JSR168 should then publish a schema at a well known URL for any
>extensions it requires, above string arrays and named strings (string name
>value pair collections) and stringValue properties, including container
>elements in <extensions/> (that are a JSR168 type and point at the JSR168
>xsd using the schemaURL attribute) for the string types in the WSRP wsdl,
>so that they can be carried in WSRP Extensions elements in a more
>well-typed manner."
>
>
>
>----------------------------------------------------------------
>To subscribe or unsubscribe from this elist use the subscription
>manager: <http://lists.oasis-open.org/ob/adm.pl>
--
Rex Brooks
Starbourne Communications Design
1361-A Addison, Berkeley, CA 94702 *510-849-2309
http://www.starbourne.com *
----------------------------------------------------------------
To subscribe or unsubscribe from this elist use the subscription
manager: <http://lists.oasis-open.org/ob/adm.pl>
