Differences between version 3 and revision by previous author of SGML.
Other diffs: Previous Major Revision, Previous Revision, or view the Annotated Edit History
| Newer page: | version 3 | Last edited on Thursday, October 16, 2003 10:17:01 pm | by StuartYeates | Revert |
| Older page: | version 2 | Last edited on Monday, October 6, 2003 1:51:00 pm | by AristotlePagaltzis | Revert |
@@ -3,9 +3,12 @@
It evolved from earlier generalized markup languages developed at [IBM], including General Markup Language (GML) and ISIL. Despite the name, it's not itself a markup language, but a description of how to specify one. Such a specification is called a [DTD]; a good example for MetaData. The premier markup language defined in terms of [SGML] is [HTML]. While disregarded in [HTML] for a long time, the philosophy of [SGML] is that documents should be described in terms of their structure, rather than the "document image". They can then be displayed or output in any form appropriate for any media.
However, the standard is excessively complex, so no [SGML] parser to date supports all of the standard's features. Many of these were added to cater to humans writing [SGML] documents manually, but more and more markup is machine generated. This situation eventually led to the creation of [XML].
-sgmlnorm(1) can be used to check whether [SGML] documents validate against their [DTD]. F.ex
, if a [HTML] file contains a proper document type declaration like
+sgmlnorm(1) can be used to check whether [SGML] documents validate against their [DTD]. For example
, if a [HTML] file contains a proper document type declaration like
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01//EN">
then sgmlnorm(1) can validate it against [W3C]'s __strict.dtd__ and report any violations (such as having text not contained in __<P>__ or __<DIV>__ tags). [Debian] users can install the __sp__ package to get this and other [SGML] parsing tools.
+
+----
+CategoryStandards
