PLease explain XMLDocument use ???

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

dear all,

I have benn going through a .net possibility such as amanging XMLDocument
and xml transmorf function.
In that set of features I am really swimming deep under the water, I have
nearly no more heirs. In fact I do not know the real benefit of using those
XMLDocument or XLS transformation files.

In that my problem is that I do not really see when this can of feature can
be use, and the real benefit of those, concrete examples.

For me at a first step xml format was for being able to read the same file
either from a windows application or web browser, but if you open a xml file
with browsser sure it open it but as raw data, so wht is the need.

I really need some real light to help me understand this XML approah and
real application case to make me understand better when to use them

Thnaks a lor for you help
regards
Serge
 
Hi Serge,

One of the reasons I use XML for relational databases, is that you don't
have to pay for any licenses, and you can share and manipulate the data
across disparate platforms such as UNIX, Linux, Windows.

With Sun Microsystems servers and the latest UNIX XML parsers, you can
get extreme performance with block-level full-text indexing. Add PERL to
the mix with inverted tree capabilities, and you are blasting your way
to the future. By using XML, you would also be geared up for
server->server communications with other businesses.
 
XML shines when sending data between different systems, working with data
from customers, vendors, etc. We have created XML files that are cached for
static data....I have seen some work done where pages were rendered from XML
via XSLT and to me it's a nightmare.

Does anyone use XML/XSLT to render web pages?
 
serge said:
I really need some real light to help me understand this XML approah and
real application case to make me understand better when to use them
Click to expand...
To exchange documents in an environment where neither side wants to
depend on the technology the other party uses you need a common language
in which to write these documents. XML is the defacto standard-language.

XML is a flexible way to create common information formats and share
both the format and the data. Because data is represented as plain text
in XML documents virtually any computer system can parse XML documents
and use the data. XML is therefore the preferred data format most of the
time.

XSL or XSLT is used to transform an XML document to another document
structure. The transformation target is usually plain text, HTML code or
another XML schema. Although XSLT can be difficult to understand at
first, it is an immensely powerful tool. If you need to convert an XML
document to another format, for example when integrating disparate
systems, or you want to present XML data in an HTML page, XSLT is often
perfect technology to use.

Anders Norås
http://dotnetjunkies.com/weblog/anoras/
 
Hi Serge,

First off, you may want to read up on Service Oriented Architecture.
Here's a link to one of Pat Helland's recent articles
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnbda/html/dataoutsideinside.asp

XML is useful if you need to communicate complicated data in a standardized
way.

It is best used when communicating from system to system, as some of the
other responders have implied.
Since I can create a schema that defines the RULES that a valid XML document
must follow, I can pass a schema to my trading partner, and they can write
software that will meet the schema, and I can commit to them that I can
accept the data they write. This is a Dramatic improvement over current
practice when integrating systems.

That said, I've also used XML as a mechanism to store "semi-structured"
data. This is data that, from the standpoint of the storage system, is
essentially a BLOB, but has a structure. For example, if I have a wide
range of XML documents stored in SQL Server 2005 (Yukon), I can store the
documents into an XML field and query on the data in a very flexible manner.
I could have 10 rows in an inventory table, where the first five rows store
data about computers, and the next five rows store data about monitors. The
XML structure can be defined so that there are common elements dealing with
inventory tags and locations, and embedded elements dealing with resolution
(for monitors) or CPUs (for computers). I can issue a single XQuery against
this table and retrieve all the inventory tags, and another XQuery against
the table and retrieve all the CPU information for the rows that deal with
computers.

This ability to store semi-structured data is very powerful in many ways.

I also use XSLT to transform XML documents into other formats, although I'm
not well versed in the XSLT language (I use tools mostly). For example, I
have a workflow system that manages any number of different workflow
documents. Each document type comes with an XSLT that allows my GUI to
display information about the workflow item without my GUI needing to know
anything about the structure and format of the workflow document itself
(another example of semi-structured data).

XML is not a silver bullet. It doesn't solve every problem. However, it is
a very useful technology to add to your tool belt.

--
--- Nick Malik [Microsoft]
MCSD, CFPS, Certified Scrummaster
http://blogs.msdn.com/nickmalik

Disclaimer: Opinions expressed in this forum are my own, and not
representative of my employer.
I do not answer questions on behalf of my employer. I'm just a
programmer helping programmers.
--
 
Hi Nick,
That said, I've also used XML as a mechanism to store "semi-structured"
data.
Click to expand...

That's a good point that I forgot to mention. With traditional database
tables you tend to be constrained into columns, but with XML you can
have really natural and varied data structures. It's a bit like using
pen and paper where you can slot things in where it makes most sense
instead of having to conform to what the database is telling you.
 
Back
Top