Hi Roger,
I
have a small observation: I don't know that #4 (SOAP format) actually makes
sense the way it is worded...that is, if you consider the data to be the message
payload (vs. including the message envelope), then #4 would not really be an
option, as the message envelope would SOAP-based, and once the envelope is
"opened" (stripped away) by the ultimate receiver (or temporarily by an
intermediary), what would be left is the payload. Then, the question becomes the
format of the data that comprises the payload - i.e. is it XML (option #3), an
MP3 attachment (#5), an MPEG attachment (#6), etc.
Joe
Joseph Chiusano
Associate
Booz Allen Hamilton
700 13th St. NW, Suite 1100
Washington, DC 20005
O: 202-508-6514
C: 202-251-0731
Hi
Folks,
I am interested in putting together
a list of examples for each of these:
- A service which
serves up its data to its customers in RSS format.
- A service which
serves up its data to its customers in HTML format.
- A service which
serves up its data to its customers in XML format.
- A service which
serves up its data to its customers in SOAP format.
- A service which
serves up its data to its customers in audio (MP3)
format.
- A service which
serves up its data to its customers in video (MPEG)
format.
Also, I am interested in examples
of:
- A service which
serves up its data to its customers in two or more different
formats.
If you know of a service which fits
one of the above, please send me:
-
The name of the
service
-
A 1-2 sentence description of the
service
-
What format(s) does the service
serve up
Thanks!
/Roger
|