The Universal Description, Discovery and Integration (UDDI) specifications define a way to publish and
discover information about Web services. The term "Web service" describes specific business
functionality exposed by a company, usually through an Internet connection, for the purpose of
providing a way for another company or software program to use the service.
Web services are becoming the programmatic backbone for electronic commerce. For example, one
company calls another's service to send a purchase order directly via an Internet connection. Another
example is a service that calculates the cost of shipping a package of a certain size or weight, so many
miles via a specific carrier.
At first glance, it would seem simple to manage the process of Web service discovery. After all, if a
known business partner has a known electronic commerce gateway, what's left to discover? The tacit
assumption, however, is that all of the information is already known. When you want to find out which
business partners have which services, the ability to discover the answers can quickly become difficult.
One option is to call each partner on the phone, and then try to find the right person to talk with. For a
business that is exposing Web services, having to staff enough highly technical people to satisfy
random discovery demand is difficult to justify.
Another way to solve this problem is through an approach that uses a Web services description file on
each company's Web site. After all, Web crawlers work by accessing a registered URL and are able to
discover and index text found on nests of Web pages. The "robots.txt" approach, however, is
dependent on the ability for a crawler to locate each Web site and the location of the service description
file on that Web site. This distributed approach is potentially scalable but lacks a mechanism to insure
consistency in service description formats and for the easy tracking of changes as they occur.
UDDI takes an approach that relies upon a distributed registry of businesses and their service
descriptions implemented in a common XML format.
another way to bloat up the web while not accepting that commerce on the web is not ever going to do what they (corp. america) would like it to. I long for the days when E-(insert annoying buzzword here) was a glimmer in satan's eye, and we all had crappy "homepages" that we managed to hide somewhere on the corp. website.
At least then we didn't have to support this garbage and M$ didn't give a fuck about the web.
I would like to take the person who decided to use the web as a service (application, whatever buzzword they would like to apply) out behind the barn and beat them, in my opinion this is all just bad rehash of the terminal based computing of the past, done up with preety colors and lag ass speed
I think your questions are very well answered in the press release, BSDi code will continue to be merged into FreeBSD as before. I am hoping this is not just a statement to keep us from flaming them to death, but it makes sense
from the point of view of a NeXTStep freak (well used to be) you got close enough and made a good point..thanks
(plus you made me try and remember how it all worked out)
oh yea I got somthing wrong too NeXTStep 3.X(3?) also ran on Intel, SPARC, and HP
NeXTStep HW and OS until 3.3 (68040 hw)
OPENSTEP OS ran on NS (black hardware) Intel, SPARC (32), and HP
OPENSTEP Framework ran on Windows (nt?) and Solaris (this was to be able to create apps that ran across platforms with just a recompile
nice article, glad to see a rehash of history for the new folks running in terror from the land of blue screens and aliases for real commands done in python
http://minnie.cs.adfa.edu.au/Unix_History/
http://perso.wanadoo.fr/levenez/unix/
http://www.unix-wizards.com/tree.html
That has to be one of thee most short-bus esq theories I have heard. RedHat is in "the black" because they stopped spending money they didn't have, the recession hit them just as well as everyone else, While it is amazing that someone using a slightly unorthadox bussiness plan (taking a product and turning it into a service) could even function at all, it is not suprising in this age of worthless crap and superfulous garbage another company that makes somthing that isn't quite so bad survives.
Corporations ask for RedHat when they are planning on using linux for servers. I am thinking of building my first FreeBSD port/usr/ports/emulators/redhatloginscreen
and my second/usr/ports/sysutils/redhatuname
*8@)
everyone cross there fingers and hope that one of the following buys them.
1) Sun, They really should own everything cool
2) Apple, they already owe PARC everything why not
repay the favor
3) Insert random startup looking to achieve
legitimacy here
4) MS, if they study some of the original GUI
code they might mave somthing usefull for w3k
that really saddens me, I was hoping apple would'nt break the best feature of NeXTSTEP
which was quality USEABLE multitasking, only
other setup I have found to be neerly as tolerable
is FreeBSD on a fast box with decent ram and a light wm
For apple to have made the OPENSTEP code into a
clunky slow apple/linux/gnome'esk UI is preety sad
I can seeing p100's running 3.3 with over a hundred applications open, if you brought the one
on the bottom up, it was instantly useable.
really really sad
LinuxPPC seems nice enough I have installed it and
run it for a time on newer macintosh hardware.
But the X/GNOME/KDE GUI has nothing on what IMO
is the best GUI made, NeXTSTEP 3.3/OPENSTEP 4.X
had a very easy to use unified FAST, must I repeat
FAST interface that users were not scared of, on
a 33mhz 68040, I ran more applications than this
damned 233MXX laptop running linux could EVER run.
With a newer version of the Mach Kernel
and an upgrade from 4.3bsd to 4.4bsd-lite, the
under pinnings of MacOS X are second to none, granted people here don't like shelling out money for anything let alone as OS
but I for one will be shelling out my (insert $$ value here) for a version of NeXTSTEP running on
big hardware. I don't think I'll need the seperate
partition for linux anymore.
Once again she suprises me, Courtney Loves
battle with the record industry heartens me.
It also reminds me that those of us who love mp3,
for playing copyrighted songs which we have not payed for (there I came out and said it which of you lilly livered scapegoats is gonna bitch) are
not entirely the bad guys, one of these days I'll
figure out a way to honestly justify my mp3 habit.
till then, mp3 IS a crime and I am a criminal
*8@)
if you don't have to sign an agreement that
basicly is morally equivelent to an NDA, I will be VERY suprised.
If you do download whatever file they give to be hacked, be prepared to be REALLY fucking sued if
you release code publicly that breaks there watermark.
I really think this whole thing is just a big ploy to be able to buy and hide any code for breaking sdmi, NOT a way to further secure the format.
They simply want to buy the code, my bet is, you have to sign a contract saying that this code is theirs and you cannot under any circustances give the code away or sell it (yea right) to anyone else.
Welcome to Your Code or Your Life,
the game show where we will kill you if you don't
give us your code!!
I think if we let them have their cake, (a tested
"secure" digital audio format), we might just get to eat ours, (them leaving mp3 alone and struggling to get the new format adopted)
This bothers me, while realisticly they are just
trying to build an effectivly watermarked audio
sceme, I am torn between the ability of someone to
prevent "theft" of there material, and my right to
have an audio format that is playable on anything
I own.
Shows you just how unoriginal we are.
it'd be nice if more of this stuff would come out
and remind people just who created all the things they enjoy.
Moron: "OH MY GOSH LOOK I INVENTED THE TAG"
Satan: "umm I have been using blink tags in on my website since 1200 bc"
Simple, RedHat had all the right things in the right places at the right time. By having an easy
to install distribution they attracted people who
had heard the word linux and wanted to know more.
By having been around a little while they got people to be RedHat bigots, and anit-RedHat bigots. Those two groups of people are very important to market share in a FreeOS based market. People who hate your OS are more likely to talk about it than those who do. They also were
first (seemingly) to the spot of "most corperatized distribution" this made them safe for
business.
The best thing about RedHat's popularity is it keeps all the linuxoids distracted enough that
they don't come around messing with the OS's I love.
*8@)
one suggestion, never take apart a M$ natural keyboard (the old ones, not the new ones), it is a
pain to get apart and a REALLY big pain to put back together, I did get it working after spending
a half a day of work cleaning it out.
I am another person who prefers keyboards with CLICK, I liked the Zeos keyboards (but nothing else about em) they were not quite IBM quality
but still had some click to em.
Slashdot Mirror
this was better moderated as +3 Troll it is not interesting or a +2 don't fuck up a good thing morons
Nice fucking troll...^5
moderators, fear the inevitable trout slapping
The Universal Description, Discovery and Integration (UDDI) specifications define a way to publish and discover information about Web services. The term "Web service" describes specific business functionality exposed by a company, usually through an Internet connection, for the purpose of providing a way for another company or software program to use the service. Web services are becoming the programmatic backbone for electronic commerce. For example, one company calls another's service to send a purchase order directly via an Internet connection. Another example is a service that calculates the cost of shipping a package of a certain size or weight, so many miles via a specific carrier. At first glance, it would seem simple to manage the process of Web service discovery. After all, if a known business partner has a known electronic commerce gateway, what's left to discover? The tacit assumption, however, is that all of the information is already known. When you want to find out which business partners have which services, the ability to discover the answers can quickly become difficult. One option is to call each partner on the phone, and then try to find the right person to talk with. For a business that is exposing Web services, having to staff enough highly technical people to satisfy random discovery demand is difficult to justify. Another way to solve this problem is through an approach that uses a Web services description file on each company's Web site. After all, Web crawlers work by accessing a registered URL and are able to discover and index text found on nests of Web pages. The "robots.txt" approach, however, is dependent on the ability for a crawler to locate each Web site and the location of the service description file on that Web site. This distributed approach is potentially scalable but lacks a mechanism to insure consistency in service description formats and for the easy tracking of changes as they occur. UDDI takes an approach that relies upon a distributed registry of businesses and their service descriptions implemented in a common XML format.
another way to bloat up the web while not accepting that commerce on the web is not ever going to do what they (corp. america) would like it to. I long for the days when E-(insert annoying buzzword here) was a glimmer in satan's eye, and we all had crappy "homepages" that we managed to hide somewhere on the corp. website. At least then we didn't have to support this garbage and M$ didn't give a fuck about the web.
I would like to take the person who decided to use the web as a service (application, whatever buzzword they would like to apply) out behind the barn and beat them, in my opinion this is all just bad rehash of the terminal based computing of the past, done up with preety colors and lag ass speed
I think your questions are very well answered in the press release, BSDi code will continue to be merged into FreeBSD as before. I am hoping this is not just a statement to keep us from flaming them to death, but it makes sense
from the point of view of a NeXTStep freak (well used to be) you got close enough and made a good point..thanks
(plus you made me try and remember how it all worked out) oh yea I got somthing wrong too NeXTStep 3.X(3?) also ran on Intel, SPARC, and HP
NeXTStep HW and OS until 3.3 (68040 hw)
OPENSTEP OS ran on NS (black hardware) Intel, SPARC (32), and HP OPENSTEP Framework ran on Windows (nt?) and Solaris (this was to be able to create apps that ran across platforms with just a recompile
nice article, glad to see a rehash of history for the new folks running in terror from the land of blue screens and aliases for real commands done in python http://minnie.cs.adfa.edu.au/Unix_History/ http://perso.wanadoo.fr/levenez/unix/ http://www.unix-wizards.com/tree.html
That has to be one of thee most short-bus esq theories I have heard. RedHat is in "the black" because they stopped spending money they didn't have, the recession hit them just as well as everyone else, While it is amazing that someone using a slightly unorthadox bussiness plan (taking a product and turning it into a service) could even function at all, it is not suprising in this age of worthless crap and superfulous garbage another company that makes somthing that isn't quite so bad survives. Corporations ask for RedHat when they are planning on using linux for servers. I am thinking of building my first FreeBSD port /usr/ports/emulators/redhatloginscreen
and my second /usr/ports/sysutils/redhatuname
*8@)
I'm sorry, this borders on being really funny, and considering thread is almost on topic....umm haha
ok that is just wrong...editor wars aside
NO ONE argues for pico....
everyone cross there fingers and hope that one of the following buys them. 1) Sun, They really should own everything cool 2) Apple, they already owe PARC everything why not repay the favor 3) Insert random startup looking to achieve legitimacy here 4) MS, if they study some of the original GUI code they might mave somthing usefull for w3k
It'll be sad to see another part of computing history left behind for the vultures to feed on.
that really saddens me, I was hoping apple would'nt break the best feature of NeXTSTEP which was quality USEABLE multitasking, only other setup I have found to be neerly as tolerable is FreeBSD on a fast box with decent ram and a light wm
For apple to have made the OPENSTEP code into a clunky slow apple/linux/gnome'esk UI is preety sad
I can seeing p100's running 3.3 with over a hundred applications open, if you brought the one on the bottom up, it was instantly useable. really really sad
LinuxPPC seems nice enough I have installed it and run it for a time on newer macintosh hardware. But the X/GNOME/KDE GUI has nothing on what IMO is the best GUI made, NeXTSTEP 3.3/OPENSTEP 4.X had a very easy to use unified FAST, must I repeat FAST interface that users were not scared of, on a 33mhz 68040, I ran more applications than this damned 233MXX laptop running linux could EVER run.
With a newer version of the Mach Kernel and an upgrade from 4.3bsd to 4.4bsd-lite, the under pinnings of MacOS X are second to none, granted people here don't like shelling out money for anything let alone as OS but I for one will be shelling out my (insert $$ value here) for a version of NeXTSTEP running on big hardware. I don't think I'll need the seperate partition for linux anymore.
Once again she suprises me, Courtney Loves battle with the record industry heartens me. It also reminds me that those of us who love mp3, for playing copyrighted songs which we have not payed for (there I came out and said it which of you lilly livered scapegoats is gonna bitch) are not entirely the bad guys, one of these days I'll figure out a way to honestly justify my mp3 habit. till then, mp3 IS a crime and I am a criminal *8@)
if you don't have to sign an agreement that basicly is morally equivelent to an NDA, I will be VERY suprised. If you do download whatever file they give to be hacked, be prepared to be REALLY fucking sued if you release code publicly that breaks there watermark.
I really think this whole thing is just a big ploy to be able to buy and hide any code for breaking sdmi, NOT a way to further secure the format. They simply want to buy the code, my bet is, you have to sign a contract saying that this code is theirs and you cannot under any circustances give the code away or sell it (yea right) to anyone else. Welcome to Your Code or Your Life, the game show where we will kill you if you don't give us your code!!
I think if we let them have their cake, (a tested "secure" digital audio format), we might just get to eat ours, (them leaving mp3 alone and struggling to get the new format adopted)
This bothers me, while realisticly they are just trying to build an effectivly watermarked audio sceme, I am torn between the ability of someone to prevent "theft" of there material, and my right to have an audio format that is playable on anything I own.
s/THE TAG/THE TAG
yes I know I suck
yes I know I should
have hit preview
Shows you just how unoriginal we are. it'd be nice if more of this stuff would come out and remind people just who created all the things they enjoy. Moron: "OH MY GOSH LOOK I INVENTED THE TAG" Satan: "umm I have been using blink tags in on my website since 1200 bc"
ummm your .sig disagrees with your post
or is that the other way around
Simple, RedHat had all the right things in the right places at the right time. By having an easy
to install distribution they attracted people who
had heard the word linux and wanted to know more.
By having been around a little while they got people to be RedHat bigots, and anit-RedHat bigots. Those two groups of people are very important to market share in a FreeOS based market. People who hate your OS are more likely to talk about it than those who do. They also were
first (seemingly) to the spot of "most corperatized distribution" this made them safe for
business.
The best thing about RedHat's popularity is it keeps all the linuxoids distracted enough that
they don't come around messing with the OS's I love.
*8@)
one suggestion, never take apart a M$ natural keyboard (the old ones, not the new ones), it is a
pain to get apart and a REALLY big pain to put back together, I did get it working after spending
a half a day of work cleaning it out.
I am another person who prefers keyboards with CLICK, I liked the Zeos keyboards (but nothing else about em) they were not quite IBM quality
but still had some click to em.