SI
SI
discoversearch

We've detected that you're using an ad content blocking browser plug-in or feature. Ads provide a critical source of revenue to the continued operation of Silicon Investor.  We ask that you disable ad blocking while on Silicon Investor in the best interests of our community.  If you are not using an ad blocker but are still receiving this message, make sure your browser's tracking protection is set to the 'standard' level.
Technology Stocks : Novell (NOVL) dirt cheap, good buy? -- Ignore unavailable to you. Want to Upgrade?


To: rudedog who wrote (34314)10/16/2000 10:17:34 AM
From: PJ Strifas  Respond to of 42771
 
Again, my perspective is how will MSFT "manage" the open access to their "stack" and services for outside vendors? It's a tough question since they want to "own" that access and therefore "promote" their products over competitors.

Since it is based on "open standards" such as XML and SOAP I do believe the future is much brighter than the past could have been. There is no reason not to believe that other companies (NOVL included) can not participate within the .NET strategy and succeed!

Regards,
Peter J Strifas



To: rudedog who wrote (34314)10/19/2000 4:14:55 PM
From: PJ Strifas  Respond to of 42771
 
>>XML is not vendor specific - neither is SOAP. The >>programming framework, like every MSFT programming >>framework, "works best" on the MSFT stack - but it has to >>also work in the broader market.

Doing some research on this topic and I found this:
techrepublic.com

Experts sift through XML standards to pick top contenders
Oct 19, 2000 - Loraine Lawson

If you're waiting to adopt XML until a dominant standard emerges, Gartner experts have a word of advice: Don't.

Ultimately, your company can't afford to wait for a single standard to win out, the experts say.

Gartner Research analysts Rita Knox, Marti Harris, Debra Logan, David McCoy, and Wes Rishel discussed XML standards during a panel discussion Wednesday afternoon at the Gartner Symposium/ITxpo in Orlando, FL. (TechRepublic is an independent subsidiary of Gartner.)

Currently, there are more than 350 versions of XML. Panel members agreed that the number will go down, though they added that it's unlikely that there will be only one standard in the near future.

"There are no winning standards yet for generic process representation," McCoy said. "At this point, we're too early to say."

However, all of the Gartner panelists did endorse employing some flavor of XML—which is widely recognized as the next standard for open data transfer—in a current business integration application.

So how can a developer or net admin know which standard to use? Here's a look at the standards highlighted during the panel discussion:

Oasis' ebXML
The National Learning Infrastructure's Instructional Management System (IMS)
Microsoft's BizTalk XLANG
RosettaNet
------

So is the .NET strategy is really an open-standards play as the marketing hype contends? That depends on how the actual XML standard develops - so the jury is still out. With 350 different flavors of XML, it should be a very interesting standard proposal to say the least!

My friends and I have a saying whenever we read that Company XYZ is supporting "Standard123" - Is it checkbox support? Meaning that some research done by "suits" (read CxOs) merely check off boxes (ie, NDS is LDAP-compliant in the literate so check that off) to find the right technology for their company without ever testing the software.

So MSFT is going to build this "framework" where their flavor of XML is the glue that binds things together. Some people will call this "open" I see it as a replay of Java and MSFT's J++. They will embrace XML and extend it into their architecture thereby keeping people within their bounds. If not, they aren't the smart businesspeople everyone is so eager to call them.

Regards,
Peter J Strifas