XML is an Internet standard document created to replace HTML and reinforce the weaknesses of HTML.

Currently, there are HTML and XML standard Internet documents that can be used in web browsers.
XML is a document created to be used on the web like HTML, and is a language and a small repository.
Therefore, it is correct to use XML on the web.

HTML, which has been used the most as a content expression language on the Internet so far, was adequate for its function of expression, but encountered a limit when trying to reuse or search documents. The reason XML is attracting attention as the next-generation Internet language to solve this problem is that XML is a language capable of extensibility, compatibility, and information structure. Now, we are entering an era where we cannot say that we know the Internet without knowing XML. XML is no longer optional. It is a core technology of the Internet.

HTML (Hyper Text Makeup Language), which we are already familiar with, is now easily accessible to anyone on the Internet. This document is a document established as an Internet standard by a world standards organization called W3C (World Wide Web). Without this HTML, it may have been difficult to expect success in the Internet field as it is today. However, HTML, the main character of this Internet success, is produced for display, It has a weakness in that it is difficult to reuse and re-edit documents.

◆Then, what is the difference between HTML/general documents (Office documents, PDF...) and XML?

If unstructured information is stored as a general document, it has the following weaknesses.

◆XSL is required to view XML document in web browser.

XSL (Extensible Stylesheet Language) is a language for defining styles of XML documents.
XSL is largely composed of XSLT (XSL Transformation), a transformation language, and XSL FO (XSL Formating Objects), an output language.

XSL is the language responsible for the XML view. Simply put, it is a language responsible for packaging XML documents. XSL language includes all functions of HTML stylesheet.
XSLT transforms an XML document into another document format. It is converted into documents such as HTML and WML through XSLT and displayed on the web browser.

AutoXML is a web development technology based on Content Model. And AutoXML technology is a technology used based on XML on HTTP.

AutoXML technology is different from general XML technology in production process and output.

The XML document created with AutoXML technology is a perfect W3C standard document and can be used directly on the Internet.

AutoXML technology is a technology that uses and utilizes only the standard document (pureXML) set by the W3C in the web browser. The data is stored in XML, the view has XSL, and the communication protocol is an XML technology that can be written on the web using HTTP.

The difference between pureXML(AutoXML) and mixXML(ODF/OOXML) is as follows.

AutoXML is an XML technology that adheres to the 10 principles set by the W3C and is a document.

The design goals for XML are :

1. XML shall be straightforwardly usable over the Internet.
2. XML shall support a wide variety of applications.
3. XML shall be compatible with SGML.
4. It shall be easy to write programs which process XML documents.
5. The number of optional features in XML is to be kept to the absolute minimum, ideally zero.
6. XML documents should be human-legible and reasonably clear.
7. The XML design should be prepared quickly.
8. The design of XML shall be formal and concise.
9. XML documents shall be easy to create.
10.Terseness in XML markup is of minimal importance.


W3C's XML Development Goals:

1. XML should be readily available on the Internet.
2. XML should support a wide range of applications.
3. XML must be compatible with SGML.
4. Programs that process XML documents should be readily available.
5. XML optional features should be minimized or, if possible, absent.
6. XML documents should be human-readable.
7. You should be able to do XML design quickly.
8. XML design must conform to a specific style and be implicit.
9. XML documents should be easy to generate.
10. Terseness in XML markup is not important.


pureXML was established as the next-generation Internet standard document by the W3C in 1998, and has already been widely distributed as a standard in various industries.

The advantage of pureXML is that all standard technologies set by W3C can be applied.
XSL, XSLT, XPointer, Xpath, XLink, DOM, SAX, XQuery, AJAX, Javascript, CSS, HTML

This can be combined with XML technology and existing web programming technology (HTML, Javascript, CSS, ASP, JSP, .NET, Java) to develop effective applications and solutions. It can be converted and used.

ODF and OOXML, which are currently in progress as standards, not only do not satisfy the basic XML principles and ideas set by the W3C, but also do a significant job of giving up the many advantages of XML (The design goals for XML). .

division	pureXML	Generic XML (mixXML)
XSL	use	not used
program used	web browser	Application
OSMU realization	possible	impossible
Platform relation	Independent	subordination
OS	Independent	subordination
type	AutoXML	OOXML, ODF, FLEX...
Compatibility with existing web technologies	high	low
development method	Content Model	Data Model

Should I throw away all the resources of the existing system when developing with AutoXML technology? not.
XML technology is a killer It is not an application technology, it is an enabled technology . In other words, XML is a technology that reinforces the existing system while maintaining it as it is.

XML is excellent because it is a language with excellent extensibility, portability, compatibility, interoperability, and readability, and it can act as a small storage (DB) and can be applied well on any platform.
In case of developing web application/solution, it can be mixed with existing RDBMS and web programming technology. In particular, since the functions and properties of HTML are all contained in XML (XSL), existing web development technology can be used as it is.

When developing web applications/solutions, XML technology is used as a very important element technology for integration and interworking between systems. XML has excellent portability, extensibility, and interoperability, so it is very easy to interoperate with existing legacy systems.

The following explanation is a model that analyzes how XML technology is applied to the web application/solution development field.

division	Large XML Model	Medium XML Model	Small XML Model
AutoXML	80-90%	50%	10-20%
Legacy Technology	10-20%	50%	80-90%
field of application	Systems that use day-day content a lot (EDMS, KMS, CMS) A system for exchanging data and documents (B2B) Electronic payment	A system for exchanging and integrating data and documents (BPM, SCM, CRM, Collaborative ERP...)	A system that a lot of business logic applies (ERP...)

◆There is no difference between web development using webform and AutoXML method!

In general, database-based data model development uses a web form to create information and store it in the DB.

The AutoXML development method also uses a web form to create an XML document and store it in the DB.

There is no problem at all in using it in conjunction with existing technologies because XML documents are created from webforms and stored in the DB in the conventional way.

In the AutoXML development method, since XML acts as a small database, transactions applied to the DB are handled in a distributed manner, resulting in less load on the DB. In addition, there is no problem in effectively processing XML documents using the existing RDB because XML is composed of text documents even in large-capacity processing of XML documents. View file, XSL, can express millions of documents with a very small capacity because even if 100 XML documents are created, only one XSL document is required.

When comparing storage space, access speed, and analysis process as a whole, storing data in XML on the web is more effective than processing with RDBMS alone.
XML Repository includes all the functions of the existing RDBMS and can play the role.
Currently, XML-only databases have excellent transaction processing, and the execution speed is significantly faster than RDBMS.
Because XML is text-based, compatibility with existing RDBMS is very good.

AutoXML development method stores structured/unstructured information as XML documents, extracts structured data required by logic and stores it in an RDB format table.

In the AutoXML development method, structured/unstructured information is stored as XML documents, and the structured data required by logic is extracted and stored in an RDB type table.

In general, the data that requires logic to be stored in the RDB type table occupies about 10-20% of the total information.

The fundamental purpose of this question is to answer accurately by calculating the development time, man-hours, and input personnel. To compare the two development systems, many parts need to be comparatively analyzed, but if you simply compare specific things, it can be summarized as follows.

If 100 documents are to be implemented in HTML/DB method in the electronic payment system, in theory, 100 tables should be designed and programmed.

●Time taken to implement one document (DB design/programming): 20 hours

●Time required for DB/programming modification due to document change: 5 hours

●Time taken to implement 100 documents (DB design/programming): 20 hours * 100=2,000 hours + modification time

In order to implement 100 documents in the AutoXML method in the electronic approval system, in theory, design XML/XSL/Webform documents.


●Designing 1 document as XML/XSL/Webform document: 5 hours

●Time to modify XML/XSL/Webform document by document change: 1 hour

●Time taken to implement 100 documents (DB design/programming): 5 hours * 100=500 hours + modification time

It is possible with the AutoXML method to implement the approval document in the approval document system at the level of a general user who does not actually know web programming. The reason that the above method is possible in the AutoXML method is because the DB design/web programming process is omitted.

Since many parts of the AutoXML-based development process are solved by automated tools and engines, the development period and man-hours can be greatly reduced. If the integration process is additionally developed in the existing method, the coding by the programmer should be reinforced for data exchange, but in the AutoXML method, it can be simply implemented as a tool and document exchange can be implemented at the same time.

And -.NET+Biztalk and C# platforms are implemented only on Windows-based, so development on other Linux, UNIX, and mainframes is not supported, so development must be done separately. However, development on AutoXML-based platforms supports all platforms. It is possible to reduce the man-hours of development and duplicate development.

Since AutoXML development method supports OSMD (One Source Multi Device), it can be developed independently of OS and Hardware Device, saving time, cost and man-hours!

When implementing an existing RDBMS-based web application, materials commonly used are HTML, COM, DB, and attached files (DOC, XLS, PDF...). In this case, the database and attached files are responsible for data, and it is common to implement presentation in HTML and COM through web programming such as .NET or Java. What material we use is important here. one system now In the case of development, it is not operated as a single system, so work integration between systems and data/document integration are becoming important. In particular, there are frequent cases where data generated in one system (eg, production plan of ERP) is used in another system (SCM).

AutoXML technology eliminates money-eating hippos!

AutoXML solves security problems in the following way when developing systems on the Internet web.

●Step 1: Security based on PKI authentication/OTP (One Time Password)
●Step 2: Application-based password security
●Step 3: Grant user authority by authentication server
●Step 4: Perform limited service per user by ACL (Access Control List)
●Step 5: XML document-based security (View sample code)

XML-based content security problem is difficult to implement in RDBMS-based system and can be solved with AutoXML-based integrated security system.
XML security includes technologies such as XML server, XML authentication, XML encryption key management specification (XKMS), and XML content security.
As such, content security can implement the difficult part in RDBMS-based system, so it can be utilized in the system to handle important data.

Security is the most important part of web application development.
AutoXML technology can be used very well to secure data sent and received over the Internet.

When building system integration, the following five standardizations should be considered.

Data standardization

Document standardization

Business process standardization

Standardize messaging

Interface standardization

The most important part to review is the standardization of data and documents. Without standards (standards) for data and documents, it takes a lot of time, money, and man-hours to develop an integrated system.

The most important thing here is data standardization by XML.

If someone asks “Why standardize with XML?”, the answer is simple.
XML is an international standard document established by W3C in 1998. There are good reasons why it has become a standard.

Several W3C working groups, IT companies, research institutes, and professional organizations have already summarized the great advantages of XML. Why XML is a language with many advantages that cannot be solved by legacy documents or DBs, and it is already known as to why XML is a document. There is a good reason why the world's leading IT companies (IBM, SUN, MS, BEA, Oracle...) invest enormous amounts of time and money in XML technology. HTML currently used on the Internet Web programming technology has limitations in document exchange, extensibility, integration and collaboration in addition to the function of expression. XML and Web services are pointed out as alternative means to solve these problems.

The important thing to note here is that all platforms, applications, and tools support XML and must support it. This is not only because XML is a standard, but also because (experts) expect that all systems, applications, and DBs that do not support XML will disappear.
XML is emerging as a very important core technology because there is no alternative means other than XML for integration and collaboration between systems and for exchanging information and documents.

● Integration procedure is simpler than other integration methods.
● Integration development time is less than other integration methods.
● Needs fewer adapters (per process) than other integration methods.
● Document exchange is simpler than other integration methods.
● Extensibility/interoperability is superior to other integration methods.

Answer-● Integration process is better than other integration methods Simple.

Usually, to implement Integration in the Adapter method, the following steps are carried out.

First of all, the method of giving data from System A to System B in the legacy system integration method is to first create stream data as coding or TOOL, then transfer it to FTP, and the person in charge creates data in the DB of System B with coding or EAI TOOL. proceeds in a way

Here, we need to check the implementation time, man-hours, manpower, scalability, and maintenance of the integrated method. A particularly important thing to consider is that SAM File and XML File, which are basic materials for integration, are different. Because the XML file is structured, the development time is greatly simplified when implementing integration. Because DOM/SAX technology dealing with XML structure is It supports 3Ksoft's BaseXML platform's TOOL and can be easily integrated with simple operation.

And the most important factor is automation.
In order to implement integration by making
SAM File and sending it to FTP, a person has to process it manually, but when XML is processed in HTTP (web browser), it has a great advantage that Integration can be implemented automatically in real time. This is a huge benefit in processes where data must be processed in real time.

Answer-● Integration development time is different It costs less than the integrated method.

The answer to this is simple. The XML-based integration implementation has adopted the standard in many ways. For those who want to implement system integration, the advantages (there are standards and standards) from multiple standardizations (data, documentation, interfaces, messaging) make it easy to implement.
BaseXML-based integration can be easily implemented as TOOL and BaseXML Mapper even if you are not a professional developer.
Development time can be effectively reduced accordingly.

Answer -● Needs fewer adapters (per process) than other integration methods.

Since the existing integration method is implemented as a point-to-point method, the following number of adapters should be created theoretically when implementing integration between systems.

▶ System Data Interlocking-Use an adapter to solve compatibility
▶ Processing speed: slow
▶ System load : It takes a lot of load.
▶ When linking with other groups or organizations, it is extremely complex and difficult to link
▶ Maintenance: Develop a large number of adapters, high maintenance cost

▶ Using XML to solve system data interworking-compatibility
▶ Processing speed: Very fast.
▶ System load: almost none.
▶ Easily link with other groups or organizations
▶ Maintenance: Remarkably reducing maintenance costs

Here, the integrated implementation by XML only needs to create a MAP file with MAPPING information and store it in the MAP Repository. Then, BaseXML Mapper analyzes this information and maps the contents of the XML file to the table of the desired DB. (See Figure 5 BaseXML Integration Method above)

Existing EAI companies are adopting adapter-type integration in the integration method.
This requires a lot of time, investment, and resources, and the processing speed is also slow.

Number of adapters required for integration of adapter method = N*(N-1)/2
Number of adapters required for integration by XML = N (system number)

Answer -● Document exchange is simpler than other integration methods.

The AutoXML integration method is built on the basis of EDI (Electronic Document Interchange) that integrates information between systems. While the existing integration implementation considered how to integrate only data, the AutoXML integration method is a system that simultaneously implements data integration and document exchange. And with this system, XML-based EDI can be implemented more easily, and all users (users of other systems) who use the AutoXML integration method can When printing the XML document, the form is already expressed in XSL, so it can be printed and used as an offline document without additional development of a reporting tool. (Total time and man-hour savings)

Answer -● Extensibility/interoperability is superior to other integration methods.

Because XML is a highly scalable, portable, and interoperable language and technology, it is used by all RDBMSs and all platforms (NT, UNIX, Linux, mainframe).
In particular, since XML has already been established as a standard in each industry, it is easy to implement integrated implementation with XML in any system or platform.

The AutoXML development method is much more efficient in terms of development time, cost, and man-hours than the existing development method.

In the existing development method, development is based on database and programming, so the entire work section from modeling/planning to test/QA is inefficient in terms of time, cost, and man-hours.

If the requirements from Test and QA are corrected, review from the beginning, and if the database is changed, the program and UI are modified, increasing the development period, cost, and man-hours.

In the AutoXML development method, since the test occurs before development in the content modeling stage, it can be checked before development, so trial and error or errors can be significantly reduced.

There is a great advantage of being able to check the UI, function, and design before development. This greatly shortens the overall project.

◆ Comparison of productivity, cost, and speed of AutoXML development and existing development methods

tyoe	general method	AutoXML	AutoXML + Model
productivity	100	200	400
cost	100%	75%	50%
speed	100	200 or more	200

The Internet standard languages/documents currently available on the Internet are Hyper Text Markup Language (HTML) and eXtensible Markup Language (XML).

◆ Features of AutoXML

Internet standards document

Structured documentation

Excellent readability/compatibility/interoperability

Reduce software cost by using a web browser for creation/exchange

Automate the process → Automate possible

Excellent security

Transmission speed is fast

Search is fast and accurate

XML is a standard document/language/message/interface/small DB.

◆ Difference between AutoXML/HTML output

Fields	HTML	AutoXML
W3C standard	In 1992	In 1998
birth background	Display	exchange of documents
DB Used	◎	▲
programming	◎	▲
structured data	◎(DB)	◎ (XML+DB)
unstructured data	Ｘ File (DOC,PDF…)	◎
Data extract	Ｘ	◎
data exchange (B2B)	Ｘ	◎
Search	Ｘ	◎
Security	Ｘ	◎
integrated	Ｘ	◎
process direction	one-way	bidirectional
Semantic Web	Ｘ	◎

Some users say "We think design is very important, Is it not possible to use design in XML like existing HTML?" is a question.

XML is a W3C standard document that includes HTML.

It is the same as using image, video, sound file... in HTML. HTML5, which is new these days, is also implemented in XML.

This means that design issues should not be distinguished from XML, HTML, and HTML5.

This means that design is a matter of design and has nothing to do with XML.

Description of W3C Technology Stack Illustration
As shown in the table above, HTML, XHTML, and HTML5 are already included in XML.