OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

 


 

   Re: [xml-dev] Demand for web services

[ Lists Home | Date Index | Thread Index ]

The previous messages try to illustrate that this sentence couldn't be
applied to Web Services. I'll try to express my opinion that this
sentence couldn't be applied even for XML if you won't make additional
explanations.

As far as I know it's too dangerous to say that the separation of
content from presentation is advantage of XML or it's the main
necessity that forced the appearance of XML. So, I wouldn't be so
courageous to say this without any explanations.

There were a few discussions about this problem in Russian XML
community. Thus I have the following point of view: «In the most cases
the separation is meaningless when there are none of semantic links
between these separated parts».  Well, let's consider the process what
we do when separating data with the help of XML. First of all, we have
to make the whole document tagged.  We have to emphasize blocks of
sense in content using XML-tag. We have to express our vision of data
presentation using XML-tags, especially in the case of applying XSLT
to combine presentation and context. Consider for a moment, the only
thing you have already done is tagging and only by this you'll get a
great ability to future convenient processing. If the main idea of
this process was "plain" separation you wouldn't be able to apply your
favorite tools for processing. Just try to separate txt files
carefully in two parts and try to make from these any complicated
things.

Here you can find one of the common architecture error: «If some of
information blocks in content and presentation are strongly related
(tied) then you must express this relationship in your XML model». You
can easily imagine the document in which some piece of presentation
model are the native part of content.  So the adherence of the rule
«separate and be victorious over complexity» will lead to the loss of
semantic links and force to intricate application design.

In my opinion the separation isn't the principle feature neither in
XML nor in Web Services.


-- 
Regards, 
          ~ Xasima Xirohata ~




 

News | XML in Industry | Calendar | XML Registry
Marketplace | Resources | MyXML.org | Sponsors | Privacy Statement

Copyright 2001 XML.org. This site is hosted by OASIS