[libxml2.wiki] Update XML Guidelines
- From: Nick Wellnhofer <nwellnhof src gnome org>
- To: commits-list gnome org
- Cc:
- Subject: [libxml2.wiki] Update XML Guidelines
- Date: Sat, 12 Feb 2022 18:02:15 +0000 (UTC)
commit 4a7cef2d1f4550ce59fffb1a85aa8b0a915f59d4
Author: Nick Wellnhofer <wellnhofer aevum de>
Date: Sat Feb 12 18:02:15 2022 +0000
Update XML Guidelines
XML-Guidelines.md | 7 -------
1 file changed, 7 deletions(-)
---
diff --git a/XML-Guidelines.md b/XML-Guidelines.md
index 660fc36..107a453 100644
--- a/XML-Guidelines.md
+++ b/XML-Guidelines.md
@@ -4,13 +4,6 @@ The goal of this document is to provide a set of guidelines and tips helping the
The intended audience is the software developers who started using XML for some of the resources of their
project, as a storage format, for data exchange, checking or transformations. There have been an increasing
number of new XML formats defined, but not all steps have been taken, possibly because of lack of
documentation, to truly gain all the benefits of the use of XML. These guidelines hope to improve the matter
and provide a better overview of the overall XML processing and associated steps needed to deploy it
successfully:
-Table of contents:
-
-1. [Design guidelines](http://xmlsoft.org/guidelines.html#Design)
-2. [Canonical URL](http://xmlsoft.org/guidelines.html#Canonical)
-3. [Catalog setup](http://xmlsoft.org/guidelines.html#Catalog)
-4. [Package integration](http://xmlsoft.org/guidelines.html#Package)
-
## Design guidelines
This part intends to focus on the format itself of XML. It may arrive a bit too late since the structure of
the document may already be cast in existing and deployed code. Still, here are a few rules which might be
helpful when designing a new XML vocabulary or making the revision of an existing format:
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]