At 06:03 PM 9/29/2002, you wrote:
>I'm new to xml and want to make the most of my time regarding the learning
>curve. From what I have read, some xml is proprietary and then you have
>your pure xml.
That's about right, with one caveat. XML itself is all "pure" XML: either
it follows the rules of XML, which are public and open, or it doesn't, in
which case it isn't really XML, it's just something that claims to be.
Individual XML tag sets may be proprietary, or they may be publicly
specified and open.
XML application software may likewise be open source, non-proprietary etc.,
or it may be proprietary. Some such software (parsers, stylesheet
processors etc.) is very generic and general-purpose; other such software
(usually built on top of the generic stuff these days) is tailored for a
particular application and/or a particular tag set.
Accordingly, you could develop your own XML tag set and place it into the
public domain -- and then use SQL Server, VB.NET to build your
infrastructure. In principle, because your XML is still "pure" (which it
can be if you avoid designing it to be tightly coupled with your VB.NET
environment) you can then turn around and write code for the same data in,
If you want to be the purest of the pure, however, you may want to develop
in Java or on some other platform that doesn't lock you in as severely as
does .NET into one or another company's architecture.
As you can tell, it's not really either/or. The main thing is that XML
supports the separation from data (with the logical formatting of the data
that can be provided by a good tag structure) from processing; and as long
as you maintain that discipline you'll be better off even if you develop on
a proprietary platform, because you've preserved your option to shift
platforms, or share across platforms, without having to reformat all your
data or start fresh with it.
If you had time and inclination, one thing that might be fun would be try
something completely new, like Java or Python, for your exploration; then
after you have a handle on what you're doing and how things in XML fit
together, turn and see how it goes in MS-land.
I hope that helps.
Wendell Piez mailto:[log in to unmask]
Mulberry Technologies, Inc. http://www.mulberrytech.com
17 West Jefferson Street Direct Phone: 301/315-9635
Suite 207 Phone: 301/315-9631
Rockville, MD 20850 Fax: 301/315-8285
Mulberry Technologies: A Consultancy Specializing in SGML and XML