OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help

obix-xml message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]

Subject: RE: [obix-xml] Schema update

Shouldn't we be using well known standards for these?

Unless I am mistaken, what you are calling batching is defined by
WS-Enumeration and WS-Transfer

Web Service Enumeration (WS-Enumeration) "describes a general SOAP-based
protocol for enumerating a sequence of XML elements that is suitable for
traversing logs, message queues, or other linear information models. It
brings enumeration capabilities to the WS-* suite of specifications,
enabling an application to ask for items from a list of data that is held by
a Web service. In this way, WS-Enumeration is useful for reading event logs,
message queues, or other data collections."

WS-Enumeration recognizes that "there are numerous applications for which a
simple single-request/single-reply metaphor is insufficient for transferring
large data sets over SOAP. Applications that do not fit into this simple
paradigm include streaming, traversal, query, and enumeration. In its
simplest form, WS-Enumeration defines a single operation, Pull, which allows
a data source, in the context of a specific enumeration, to produce a
sequence of XML elements in the body of a SOAP message. Each subsequent Pull
operation returns the next N elements in the aggregate sequence."

The Web Service Transfer (WS-Transfer) specification "describes a general
SOAP-based protocol for accessing XML representations of Web service-based
resources. It enables state transfer over SOAP by defining how to invoke a
simple set of familiar verbs (Get, Post, Put, and Delete) using SOAP. An
application protocol may be constructed to perform these operations over

WS-Transfer "defines two types of entities: (1) Resources, which are
entities addressable by an endpoint reference that provide an XML
representation; (2) Resource factories, which are Web services that can
create a new resource from an XML representation. Specifically, it defines
two operations for sending and receiving the representation of a given
resource and two operations for creating and deleting a resource and its
corresponding representation."
Toby Considine      ! "There are seldom good 
UNC Chapel Hill     ! technological solutions to 
Chapel Hill, NC     ! behavioral problems."
Phone (919)962-9073 ! 
Fax (919)962-1102   !             -- Ed Crowley
tobias@fac.unc.edu  !          
-----Original Message-----
From: Aaron Hansen [mailto:ahansen@tridium.com] 
Sent: Monday, January 24, 2005 4:32 PM
Cc: obix-xml@lists.oasis-open.org
Subject: Re: [obix-xml] Schema update

Lets talk some more about batching at the next telecon before you go for 
it on the multiple poll request/response.

I think all top level messages should return an error (even 
unsubscribe), and thus, locale would necessary for each.

We'll talk about the other issues in Dave's email at the next telecon.

Some additional schema notes:
1. Error, include, unit, object, and range item types all have id and 
display elements.  What I'd like is for id and display to always have 
the same sequence location, no matter what the parent element.
2. Default values are needed for boolean elements of the include type.

Regarding the code generation difference between the 'has more children' 
options.  Since there really isn't any significant difference and only 
one option is schema enforceable, the solution seems obvious to me: 


drichards@trane.com wrote:

>I posted an updated schema.  Apparently I could have done it as a revision
to the original, but I didn't know that so it's a separate doc.  Here are
some comments to go along with it:
>This schema includes cleanups and corrections from the .5 version.  The
>known deviation from the documentation is the <ext> element of the read
>The base messagetype is defined but currently NOT used.  There have
>been some new comments around 'locale' which is the only element currently
>the base.  Also, of the twelve messages defined, three do not use 'locale'
>three others already inherit existing message types.  So it seems a bit
>premature to say there is such thing as a generic messsage type.  Is the
>additional complexity warranted right now?
>From the last meeting, what do we want the multiple Poll request to look
like - or more
>interestingly, the multiple Poll response?  Should I just do it and then we
can discuss the result?  Does this mean there is also a multiple
>Should 'Unsubscribe' be able to return an error?
>What is the philosophy for lists/arrays?  In our current scheme, each
element must be a different id.  Do we want an indexing method?
>Do we really need the first level <object> element in the write request?
We could just use the <children> element.
>Another interesting note:  For the min and max facets, the values are many
times not fixed but rather related to other points.  Do we want to have a
'ref' attribute or something to say that the value is dependent on another
point?  Still providing the current value, of course.  The issue will be
that if you also try to change the other value, the indicated min/max values
may no
>longer be valid when you try to write.
>Items that may want to be more restricted than xs:string:
>1) All the 'id' elements and atributes
>2) ParamType/Name attribute
>3) UnitType/Symbol
>4) enum element used for values
>5) ServiceType/Service element
>6) subscriptionId elements (all uses)
>7) vendorUrl and productUrl elements of About Response

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]