Looking back at the use of XML

Some time ago, Beijing came to several technical consultants to help analyze the conversion scheme of a company's project, and accidentally talked about the XML topic. The analysis by the two experts is good. XML is a good thing, but if it is abused, the system will definitely be abolished. ProgramMembers also agreed that, because a previous query, converted to XML, had more than one GB of data, so we should not mention the efficiency. In addition, the amount of XML parsing will affect the efficiency. If XML is used everywhere, the effect can be imagined.
I remember that I had a project with two parts: CS and BS. One of the declaration forms needs to be done by winform and webform. Considering the uncertainty of the declaration forms, the government departments are all like this, so the content of the form is described in XML. This idea was very good at first, but later I changed the end of CS to a programmer, and I felt that this XML had changed. Because in the past, XML also follows a certain format and can be used to determine whether it complies with the standard. Later, this XML simply became a tool used to describe what is in winform, the check box list is also changed to <checkbox .... /> <label ...... /> this combination, of course, does not mean that BS cannot be parsed, but deviates from the original design intention. The elements of the declaration form are directly described by controls without being encapsulated, it is difficult to parse, because it also needs to filter out many controls not supported by BS.
In short, the analysis failure point is the XML description, which should be in units of the elements of the Declaration Form. Each form element is encapsulated based on the winform control set, instead of the form description in the unit of the winform control.
Based on the former, the XML size will be small, which is determined, and it will be easy for any other program to take it and parse it without filtering it one by one.