The Difference Between CSS and XSLT

The Difference Between CSS and XSLT

They're Both Style Sheets, Right? YES

Many people believe that CSS is for HTML and XSL or XSLT is for XML, but that's not strictly true. While both are style sheets, they serve two vastly different purposes

The reason is that CSS is much easier to use, easier to learn, thus easier to maintain and cheaper. There are WYSIWYG editors for CSS and in general there are more tools for CSS than for XSL. But CSS's simplicity means it has its limitations. Some things you cannot do with CSS, or with CSS alone. Then you need XSL, or at least the transformation part of XSL

What CSS Can Do

• Modify the font size, color, family, and style of text in markup
• Define the location and size of an element
• Change the background image and color of elements
• Create a new look and feel for markup pages to display on the Web

What CSS Cannot Do

• Change the order of elements in a document
• Make computations based on the content of the document
• Add content to the document
• Combine multiple documents into one

What XSLT Can Do

• convert data in a standard XML format to SQL statements, tab-delimited text files, or other database formats for data sharing
• transform XSLT style sheets into new style sheets
• turn Web pages (written in XHTML) to VoiceML or XHTML Basic for handheld devices
• add CSS style sheets to XML documents for view in a browser

If all you're looking for is a style sheet to manipulate the way your content looks in a document, then you should use CSS. But if you're looking to actually transform one document into another, then XSLT is your tool

This diagram shows the role of XSL and CSS. XML documents can be rendered in three different ways: (1) if the document doesn't have to be transformed, use CSS. Otherwise, use XSL-T, the transformation language of XSL, in one of two ways: either (2)generate the style properties together with the rearranged text, using a sub-language of XSL called XSL-FO (XSL Formatting Objects); or (3) generate a new XML or HTML document and provide a CSS style sheet for that new document.

source

http://webdesign.about.com/library/weekly/aa101901a.htm

http://www.w3.org/Style/CSS-vs-XSL 

XPath Tutorial

XPath is a language for finding information in an XML document. XPath is used to navigate through elements and attributes in an XML document "w3schools"  so we can say that XPath - is a set of syntax rules for defining parts of an XML document

To Read  More about the Expressions,Predicates and Functions  ==> Hit This Link

  To Read how to use XPath in .Net  ==> Hit This Link

 

XML Namespace

Namespace help to avoid conflict between two xml objects (xml data) of the same name.

In the following example we have 2 roots called table so how we can differentiate between them? And if you make search in your Xml document with the 2 same name how to determine the element you want!! So we can solve this problem by using namespace prefixes, follow this structure

First: 2 root with no namespace

Problem with prefix

After we differentiate between 2 Xml objects using prefix we also have a problem with prefix, imagine one of department of your company choose the same name for namespace like other department in the same company that choose the same name.

 

Solution

Use Uniform Resource Identifier by using URL, The purpose is to give the namespace a unique name. However, often companies use the namespace as a pointer to a web page containing namespace information

The namespace is defined by the xmlns attribute in the start tag of an element

The namespace declaration has the following syntax. xmlns:prefix="URI"

.Net Video

Check This Link

Benefits of XML Schemas

Benefits of XML Schemas

• XML Schemas are created using basic XML, while DTDs utilize a separate syntax.
• XML Schemas fully support the Namespace Recommendation.
• XML Schemas enable you to validate text element content based on built-in and user-defined datatypes.
• XML Schemas enable you to more easily create complex and reusable content models.
• XML Schemas enable the modeling of programming concepts such as object inheritance and type substitution

 

97 Things Every Software Architect Should Know

 97Things Every Software Architect Should Know

The following are the 97 axioms selected for the book, 97 Things Every Software Architect Should Know, which will be published by O'Reilly Media in early 2009. The contents are now being edited for publishing - you can see them here. All edits will be contributed back to the 97 Things web site on this page.

read more

Here's agood blog that interested about software Architect