KR100445587B1 - Computer readable medium storing XML based data platform for representing product information using in electronic commerce system - Google Patents

Abstract

The present invention relates to a computer-readable recording medium on which a data platform capable of expressing an electronic catalog of all goods used in an electronic commerce system in XML is recorded. A header portion representing information; A body part representing detailed information of each of the one or more products, wherein the body part includes classification / identification information and product information on one or more products, and the classification / identification information indicates classification information to which the product belongs. A classification information element, an identification information element representing an identification key for identifying a product, and a type information element representing additional type information of the product, wherein the product information is a basic information element representing an essential value of the product, a product seller A sales information element representing sales information of a and a value added information element representing value added information provided by an outsider including a customer, wherein the classification information element includes one or zero sub-classification information elements to classify the product's classification information. Hierarchical Records an XML-based data platform that integrates product information used in an e-commerce system.

According to the present invention, various product information used in an e-commerce system can be integratedly expressed, product information can be classified and expressed according to a function, information redundancy can be reduced, and recursion of elements can be classified by use. Information and product information can be expressed hierarchically, and additional information can be easily expressed.

Description

Computer readable medium storing XML based data platform for representing product information using in electronic commerce system}

The present invention relates to a data platform capable of expressing product information used in an e-commerce system in an integrated manner. Specifically, a computer on which a data platform capable of expressing an electronic catalog of all goods used in an e-commerce system in XML is recorded. The present invention relates to a recording medium which can be read by.

Recently, research on electronic commerce based on the Internet and XML has been actively conducted, thanks to the extensive use of the Internet and Extensible Markup Language (XML) technology that can describe structured web documents. For smooth e-commerce, e-commerce infrastructure such as e-commerce procedures, transaction forms, and system environment should be established, and interoperability should be guaranteed through standardization of catalogs for trading items, especially for trading goods. To this end, many companies and organizations are developing their own standards and developing an e-commerce standards framework to support them. Frameworks currently under development include CommerceNet's eCo, RosettaNet, Microsoft's BizTalk, UN / CEFACT and OASIS 'ebXML. The frameworks all describe standard documents for all transactions between companies based on XML.

On the other hand, XML developed for the purpose of exchanging data on the Web, unlike HTML, provides functions such as providing a user-defined tag, structural document description, document structure verification, etc., and is actively used in data processing fields such as electronic commerce. However, despite these advantages of XML, it is impossible to correctly convey meaning between different organizations and users unless a standard for tag semantics is defined. Therefore, it is necessary to standardize commonly used tags or terms. Currently, this standardization work is being carried out in xNet, hosted by CommerceNet, RosettaNet, and OBI (Oper Buying on the Internet).

However, although standardization for e-commerce between companies is established to some extent in xCBL, RosettaNet, etc., in the standardization of the product catalog, the product information is not classified and represented, and it is not specific, so that all the information of the product is systematically described. The difficulty is pointed out. That is, in the case of data platforms for expressing product information according to the related art, it is insufficient to express detailed information of the product itself by expressing only information commonly present in all products for the integrated expression of the product.

The present invention was created to solve the above problems, and enhances versatility by separating and expressing unique and common elements for all commodity information used in an e-commerce system, and hierarchical representation of commodity classification and hierarchical information of commodity information. Its purpose is to provide a computer-readable recording medium on which an XML-based data platform capable of commercial expression and integrated expression of various product attributes is recorded.

Figure 1 illustrates the structure of ProductCatalog in the XML-based data platform according to the present invention.

2 illustrates the structure of ProductHeader, which is an element of ProductCatalog.

3 illustrates a structure of ListOfPartner that is an element of ProductHeader.

4 illustrates a structure of ProductData, which is an element of ProductCatalog.

5 illustrates a structure of ClassIdent that is an element of Product.

6 shows the structure of ProductInfo that is an element of Product.

7 illustrates a structure of BasicInfo, which is an element of ProductInfo.

8 illustrates a structure of ProductCharacteric that is an element of BasicInfo.

9 shows the structure of ProductComponents that are elements of BasicInfo.

10 shows the structure of SellingInfo, an element of ProductInfo.

11 illustrates the structure of ValueAddedInfo that is an element of ProductInfo.

In order to achieve the above object, a computer-readable recording medium on which an XML-based data platform expressing information of one or more commodities used in an e-commerce system is recorded, indicating common information of the one or more commodities. A header portion; A body part representing detailed information of each of the one or more products, wherein the body part includes classification / identification information and product information on one or more products, and the classification / identification information is a classification to which the product belongs. A classification information element representing information, an identification information element representing an identification key for identifying a product, and a type information element representing additional type information of the product, wherein the product information is basic information representing an essential value of the product. An element, a sales information element representing sales information of a product seller, and a value added information element representing value added information provided by an outsider including a customer, wherein the classification information element includes one or zero sub-classification information elements. Classification classification of the product Records an XML-based data platform that collectively expresses product information used in an e-commerce system characterized by representing hierarchically.

The main focus when designing the data platform according to the present invention is that the information on all products that can be used in electronic commerce is integrated and described in one model. To do this, we first type the attributes of all products so that various products can be represented by a general model. The criteria of typification considered in designing data platform according to the present invention are as follows. First, they should be mutually exclusive and complete between types. Second, increase the generality of the model considering both common and unique attributes of product information. Third, product attributes are limited to belonging to the product itself. In other words, the data platform according to the present invention does not consider attributes related to the seller such as delivery and payment.

Based on the product attribute classification criteria as described above, the data platform according to the present invention categorizes the product attributes into classification / identification, product essence, and information source. The classification / identification attribute enables semantic classification between heterogeneous product groups and the same product group, and includes attribute information for identifying a specific product in the same product group. These attributes are subdivided into classification information, identification information, and type information. The classification information includes attributes for classification of goods, the identification information includes attributes that can be distinguished between different goods, and the type information includes additional type information. The commodity essence attribute is an attribute that provides the essential value of all commodities. These attributes can be subdivided into content information, function / performance information, and form information according to the intrinsic value of the product. An information source attribute is an entity that provides goods, that is, an attribute provided as a source of information, and according to who provides the information, the production information provided by the producer (supplier), the sales information provided by the seller, and the customer This is classified as value-added information provided.

Hereinafter, an embodiment of the present invention will be described in detail with reference to the accompanying drawings.

First, the data platform according to the present invention is designed on the premise that it is described in XML, and the elements described on each box shown in the accompanying drawings correspond to one element of XML. In addition, symbols used in the accompanying drawings and the following description are defined as shown in Table 1.

Symbol Explanation * Indicates that the indicated node may be zero or more + Indicates that the indicated node can be 1 or more ? Indicates that the indicated node can come zero or one time | Represents OR (attr) Indicates that the indicated node is an attribute (class) Indicates that it is a class node with subnodes, so nodes without a class mark are the last node ━━━ Represents membership relationship between nodes ――― → Means recursive calls between nodes

Referring to FIG. 1, a ProductCatalog representing a catalog of a product in a data platform according to the present invention is divided into two parts, a product part of a header and a product head of a body. Data affecting the entire catalog is represented in the ProductHeader section, and data affecting each product itself is represented in the ProductData section.

Referring to FIG. 2, ProductHeader is a class that stores elements common to the entire product catalog and elements that are likely to overlap in the ProductData part. Namely, DefaultLanguage represents the basic language used for catalog descriptions, and DefaultCurrency represents the default currency for commodity prices. Of course, other languages and currencies may be used when describing product information in the ProductData part. In addition, ProductHeader is a list of zero or more Partners, and includes a ListOfPartner.

Referring to FIG. 3, ListOfPartner is a class representing Partners related to products represented in a product catalog as a list. Partners can come from any associated specific party or person, such as the manufacturer or supplier, purchaser or information provider. You can represent multiple companies or people by expressing the partner multiple times as sub-elements.

Party has an OR relationship with the Person element and contains information about the company associated with the product. Person has an OR relationship with the Party element and is a class that contains information about people related to the product. PartnerID Unique identifier given to the vendor. RelationShip represents a relationship between a company or a person and a product, and may have one of Seller, Manufacturer, and Intermediary as its attributes. Seller specifies that the company or person is the seller of the product, Manufacturer specifies that the manufacturer is a manufacturer, and Intermediary represents the middleman. These attributes are typically attributes of the company. Role specifies the role of the company or person in the product. Attributes for roles are attributes that people generally have, such as Author, Singer, and Evaluator.

In other words, the Party describes information about the manufacture, sale, and supplier of the product, and the information about the content creator about the content-oriented product, such as a book or record, is described on the Person. Since manufacturing, sales, and suppliers generally deal with multiple products, this information can be described in the ProductHeader section rather than for each product, so that information about the same company can be described only once. This effect is also shown when a person provides content for various products. For example, if a person writes several books, information about the author of the book can be described only once. Therefore, by putting Partner in ProductHeader, data duplication can be avoided when creating XML document.

Referring to FIG. 4, information related to an actual product is represented in ProductData, which may have one or more Product elements, and may represent various types of products. Each Product element represents ClassIdent class representing product classification information, product identification information, type information to classify product, and ProductInfo class representing basic and price information of product and additional information. Has

Referring to FIG. 5, ClassIdent has three elements, ClassInfo, IdentInfo, and TypeInfo.

ClassInfo expresses the classification system of goods. ClassCode represents a classification code, and ClassScheme represents a classification system. ClassValue has a child element, ClassName, which describes the class name as a child element, and a ClassSynonym of the * attribute, which describes class names similar to the class name. ClassSynonym is equipped to support search even if the user does not know the exact classification of the product.

ClassInfo has its own element as a sub-element, so that classifying information of goods can be represented hierarchically. The classification information of the novel product is described as an example.

Arts & Humanities> Humanities> Literature> Fiction

To express such information, the following structure is used.

(Classification information (classification contents, classification information?))

The classification information of novel goods exemplified in this structure is expressed hierarchically as follows.

(Category information ("art and humanities",

(Category information ("humanities",

(Category information ("literature",

(Category ("Novel")))))))))

IdentInfo is a class for representing an identification key for identifying a product by a code system provided by each agency, and has an Identifier class as a lower element.

TypeInfo is a class that contains product type information. It has CountyOfOrgin and AddedType as child elements. CountryOfOrigin represents the origin of the commodity. AddedType is a class describing additional types that support consumer-convenient search for desired products within a specific representative product. The additional type is divided into additional information related to product characteristics and additional information related to product promotion. This is a classification for smooth management of tangible information. The additional information related to characteristics includes classification by content, classification by use, classification by form, classification by user, classification by use time, and usage place. Additional information related to the promotion and additional information related to promotion include the presence of new products, the presence of recommended products, the presence of popular products, the presence of award products.

The following is additional information about the book.

<This month's novel is a book for modern women. Currently winning best awards in each category>

To express this, we use the following structure:

(Additional type (type classification, type name, other type name ?, type value))

(Type Classification ("Product Characteristics" | "Product Promotion" | Other Classification))

(Type name ("Content Category" | "Tool Type" | "Type Type" | "User Type" | "User Name")

| "Use Location" | "New Product" | "Recommended Product" | "Popular Product" | "Award Product

Nothing "| other name))

If it is determined that the classification does not fall into two categories, "product characteristics" and "product promotions," it may be stated by selecting "different classification". In addition, when selecting "other name" from the type name to expand the type name, the extensibility is enhanced by allowing the user to add an arbitrary type name to the "other type name" item of the additional type. With this structure, the above information can be expressed as follows.

(Additional Type (Type Classification ("Product Characteristics")), (Type Name ("Content Category")), "Novel")

(Additional type (type classification ("product characteristics")), (type name ("user category")), "female")

(Additional type (type classification ("product promotion")), (type name ("new or not")), "Yes")

(Additional Type (Type Classification ("Product Characteristics")), (Type Name ("Popularity")), "Best Seller")

(Additional Type (Type Classification ("Product Characteristics")), (Type Name ("Availability")), "Yes")

Referring to FIG. 6, ProductInfo has BasicInfo describing basic information of a product, SellingInfo describing sales information of a product, and ValueAddedInfo describing added value information of a product.

Referring to FIG. 7, BasicInfo providing basic information about a product has the following elements. ProductID represents the unique identification code of the product, ProductName represents the name of the product, Description contains a descriptive description of the product, and ProductPrice represents the price of the product. In other words, ProductPrice of BasicInfo expresses price set by manufacturer providing product. A manufacturer is a company that manufactures a product. It refers to a partner in the ProductHeader. ManufactedDate represents the date and time when the product was manufactured. If it is a content product such as a book or CD, it is the publication date. EffectiveDate represents the expiration date of the product, and includes child, From, Until, and Period. You can express the period using From, Until, and the date as the Period. For example, From and Until are used to represent the period 2001.3.1 to 2001.4.1, and Period is used to represent the validity period as a 30-day date. Participant represents the participant involved in the manufacture of the product, referring to the Partner listed in the ProductHeader. PhysicalDimension represents the standard specification of the product and includes length, height, weight and weight as elements. ProductComponent is a class that describes the characteristics of the parts that make up a product, ProductCharacteristic is a class that represents the characteristics of the product itself, and ProductAttachment is a class that represents an element added to express the product. To have. Attachment provides a picture of a product or a data file of the product through a URL.

Referring to FIG. 8, ProductCharacteristic describing an attribute of a product essence has the following elements. Product nature attributes are described in several specifications. TypeCode indicates the type of specification. As mentioned earlier, these types can be divided into three types: content, function / performance, and form. Types of shapes can be subdivided into specifications, weights, materials, ingredients, colors, shapes, packaging, and the like. Other types may be represented on TypeCodeOther. However, it is assumed that most products belong to the above three attribute types. Therefore, the integrated expression of the product becomes possible. In SpecificationName, the name of a product characteristic belonging to a specific type is described, and the characteristic value is expressed on Value. For example, in describing the characteristics of a computer product, CPU, RAM, auxiliary storage, etc. may be described on SpecificationName as a type of performance. In the case of RAM, the capacity is described in Value, and the unit of measure is described in UOM. When specifying the characteristics of a product, more than one type may be used. However, ambiguity will accompany SpecificationName for each product in a number of products. Therefore, it is necessary to code the SpecificationName for each product, and such a task is a task to be performed by the corresponding industry for each product.

Referring to FIG. 9, sub-elements of ProductComponents used to display the structure of a product based on a further description or a relationship between parts of a product are as follows. ProductRef refers to the identifier (ID) of the product if the part itself is represented as a product and information about the product is represented. RelationShipCode shows the relationship with the parent component. Codes can be Aggregation, Composite, Others. Aggregation is a relationship that cannot be a product by the component itself, and Composite is a relationship that can be a product by the component alone. Others are represented by Others. ComponentType represents the classification of the component, ComponentName represents the name of the component, and Manufacturer represents the manufacturer of the component. SubComponent is a class that has ProductComponents recursively as subelements.

A part can be made up of one or more other parts. Therefore, the structure by the relationship between components can be shown. In the following, such a structure will be described in more detail using the information of the computer goods as illustrated below.

<CPI 800MHz, Memory 256RAM, Monitor 17Inch LCD>

To express such information, the following structure is used.

Product Information (Product Name, Product Characteristics *, Product Information *))

(Product Characteristics (Character Name, Value))

With this structure, the above information is expressed hierarchically as follows.

(Product information ("Computer",

(Product Information ("CPI", (Product Characteristics ("CPI Clock", "800MHz"))))

(Product Information ("Memory", (Product Characteristics ("Memory Size", "256RAM"))))

(Product Information ("Monitor", (Product Characteristics ("Monitor Size", "17Inch"), (Product Information ("Brown Tube), (Product Information (" Brown Tube Type "," LCD))))))))

As a result of the above, in order to express the monitor CRT of the computer product, it can be seen that the product expression of the computer / monitor / monitor CRT is hierarchically formed.

ComponentCharacteristic is a class that has Specification as * attribute as a lower element and expresses detailed information of parts with Specification. atLeast represents the minimum number of components needed, and atMost represents the maximum number of components. Description is a class that contains a descriptive description of the part. ComponentAttachment attaches a file that is added to describe the part. It has a Attachement as a child element as the * attribute.

Referring to FIG. 10, SellingInfo representing other information on the sale of a merchandise seller has the following sub-elements.

ProductVendorData is a class representing a company that sells a product. Since the sales information may differ according to a company, the productVendorData may represent sales information for multiple vendors as a + attribute. PartnerRef refers to the Partner of ProductHeader with information about the seller. LeadTime represents the delivery lead-time of an order, and SellingPrice describes the price of the product and its details. Inventory represents the inventory of the product to be purchased, and WarrantyDescription contains descriptive information about the warranty of the product. ListOfProfferItem is a class that describes the list of products provided when purchasing a product. It has an OptionalItemSpec as a child element. The ListOfOptionalItem class represents a list of items available for optional purchase. It has an OptionalItemSpec as a child element. The Refunds class represents the difference between the refunds that occur when the product is returned after purchase, and has RefundRate and EffectiveDate as its child elements. RefundRate represents the multiplication factor, and EffectiveDate represents the period within which it can be returned.

Referring to FIG. 11, ValueAddedInfo representing additional product information has RelatedProduct and Evaluation as child elements.

RelatedProduct represents a product related to the current product. Types of related types, identifiers of related products, links to related products, etc. are represented. Attribute values include TargetType, LinkInfo, and ProductRefs. TargetType specifies the relationship with the product, which may be Component, Substitute, Alternate, Accessory, Associate, Others. LinkInfo specifies the URL that introduces the relevant product. You can refer to the product's identifier (ID) using ProductRefs. Evaluation is a class representing the evaluation of the current product, and additionally displays the evaluator, the evaluation type, the evaluation, and the evaluation date and time. For data on evaluators, refer to Partner of ProductHeader.

The data platform according to the present invention configured as described above is written in XML Extensible Markup Language document type definition (DTD). In this case, in order to increase the reusability of each element, it is preferable to configure the DTD as one file for each element with high usage rate. Hereinafter, a DTD file for ClassIdent shown in FIG. 5 and a DTD file for BasicInfo shown in FIG. 7 are illustrated among the DTD files thus created.

ClassIdent.DTD

<? xml version = "1.0" encoding = "UTF-8"?>

<! ELEMENT ClassInfo ((ClassValue), (ClassInfo)?)>

<! ATTLIST ClassInfo

ClassCode CDATA #IMPLIED

ClassScheme CDATA #IMPLIED

>

<! ELEMENT ClassValue ((ClassName), (ClassSynonym) *)>

<! ELEMENT ClassName (#PCDATA)>

<! ELEMENT ClassSynonym (#PCDATA)>

<! ELEMENT IdentInfo ((% Identifier-Class;) +)>

<! ELEMENT TypeInfo ((CountryOfOrgin) *, (AddedType) *)>

<! ELEMENT CountryOfOrgin ((CountryCode ?, CountryName))>

<! ELEMENT CountryCode (#PCDATA)>

<! ATTLIST CountryCode

CountryCodeScheme CDATA #IMPLIED

>

<! ELEMENT CountryName (#PCDATA)>

<! ATTLIST CountryName

lang CDATA #IMPLIED

>

<! ELEMENT AddedType ((Value) ?, (% Description-Class;)?)>

<! ATTLIST AddedType

TypeClass (Property | Marketing | Others) #IMPLIED

TypeNameCode (Content | Usage | Form | User | Time | Place | New | Recommended | Popular | Prize | Others) #IMPLIED

TypeNameCodeOther CDATA #IMPLIED

>

<! ELEMENT Value (#PCDATA)>

<! ENTITY% ClassIdent-Content "((ClassInfo) +, (IdentInfo)?, (TypeInfo)?)">

<! ELEMENT ClassIdent (% ClassIdent-Content;)>

BasicInfo.DTD

<? xml version = "1.0" encoding = "UTF-8"?>

<! ELEMENT ProductName (#PCDATA)>

<! ELEMENT ManufacturedDate (% Date-Class;)>

<! ELEMENT Manufacturer (#PCDATA)>

<! ATTLIST Manufacturer

PartnerRef IDREF #IMPLIED

>

<! ELEMENT Participants (#PCDATA)>

<! ATTLIST Participants

PartnerRef IDREF #IMPLIED

>

<! ELEMENT PhysicalDimension ((Length) ?, (Height) ?, (Width) ?, (Weight)?)>

<! ENTITY% PysicalDimension-attr "UOM CDATA #IMPLIED">

<! ELEMENT Length (#PCDATA)>

<! ATTLIST Length

% PysicalDimension-attr;

>

<! ELEMENT Height (#PCDATA)>

<! ATTLIST Height

% PysicalDimension-attr;

>

<! ELEMENT Width (#PCDATA)>

<! ATTLIST Width

% PysicalDimension-attr;

>

<! ELEMENT Weight (#PCDATA)>

<! ATTLIST Weight

% PysicalDimension-attr;

>

<! ELEMENT ProductCharacteristic ((% Specification-Class;) *)>

<! ELEMENT ProductAttachment ((% Attachment-Class;) *)>

<! ENTITY% BasicInfo-Content "((ProductName), (% Description-Class;)?, (% ProductPrice-Class;) *, (Manufacturer) *, (ManufacturedDate)?, (% EffectiveDate-Class;) ?, (Participants) *, (PhysicalDimension)?, (ProductCharacteristic)?, (% ProductComponents-Class;) *, (ProductAttachment) *) ">

<! ELEMENT BasicInfo (% BasicInfo-Content;)>

<! ENTITY% BasicInfo-Attr "

ProductID ID #REQUIRED

">

<! ATTLIST BasicInfo

% BasicInfo-Attr;

>

The database can be configured by creating a database schema according to the DTD as illustrated above. Therefore, the data platform according to the present invention can be recorded on a recording medium executable on a computer. The recording medium may be a magnetic storage medium (e.g., a ROM, a floppy disk, a hard disk, etc.), an optical reading medium (e.g., a CD-ROM, a DVD, etc.) and a carrier wave (e.g., transmission over the Internet). It includes a storage medium.

The following illustrates an XML document representing a "computer" product according to the data platform according to the present invention.

computer

<? xml version = "1.0" encoding = "EUC-KR"?>

<! DOCTYPE ProductCatalog SYSTEM "../ dtd / NewUPDM.dtd">

<ProductCatalog>

<ProductHeader>

<DefaultLanguage> KOR </ DefaultLanguage>

<DefaultCurrency> Won </ DefaultCurrency>

<ListOfPartners>

<Partner PartnerID = "SAMBO-1" RelationShip = "Manufacturer">

<Party>

<PartyName>

<Name1> Sambo Computer </ Name1>

</ PartyName>

</ Party>

</ Partner>

<Partner PartnerID = "SEJI" RelationShip = "Manufacturer">

<Party>

<PartyName>

<Name1> Seji Electronics </ Name1>

</ PartyName>

</ Party>

</ Partner>

<Partner PartnerID = "sambo-2" RelationShip = "Seller">

<Party>

<PartyName>

<Name1> Sambo Corporation </ Name1>

</ PartyName>

</ Party>

</ Partner>

</ ListOfPartners>

</ ProductHeader>

<ProductData>

<Product>

<ClassIdent>

<ClassInfo>

<ClassValue>

<ClassName> Computer amp; Internet </ ClassName>

</ ClassValue>

<ClassInfo>

<ClassValue>

<ClassName> Computer </ ClassName>

</ ClassValue>

<ClassInfo>

<ClassValue>

<ClassName> Desktop </ ClassName>

</ ClassValue>

</ ClassInfo>

</ ClassInfo>

</ ClassInfo>

</ ClassIdent>

<ProductInfo>

<BasicInfo ProductID = "BS409-VM3">

<ProductName> Sambo Dreamsys EX BS409-VM3 </ ProductName>

<Description>

<LongDescription> From the strongest to the future, DREAMSYS EX, the next generation multimedia PC, is strong in graphics, the next generation computer equipped with home DNA! , Future cyber design, luxury and easy-to-understand LED display, cyber metal color contribute to advanced intainer.

</ LongDescription>

</ Description>

<ProductPrice>

<Amount> 1,190,000 </ Amount>

</ ProductPrice>

<Manufacturer PartnerRef = "SAMBO-1"> Sambo Computer </ Manufacturer>

<ProductCharacteristic>

<Specification TypeCode = "Content" SpecificationName = "Configuration">

<Value> 866Mhz / 64MB / 30GB / 48X / AT 128 Pro </ Value>

</ Specification>

<Specification TypeCode = "Content" SpecificationName = "Characteristic">

<Value> Multimedia PC, futuristic cyber design, next generation multimedia PC, strong in graphics. Next-generation computer with home DNA, IEEE394, maximizes utilization of digital home appliances, convenient access to high capacity, high speed PC peripherals

</ Value>

</ Specification>

<Specification TypeCode = "Performance" SpecificationName = "CPU">

<Value> Intel PentiumIII 866Mhz </ Value>

</ Specification>

<Specification TypeCode = "Performance" SpecificationName = "RAM">

<Value> 64 MB SDRAM </ Value>

</ Specification>

<Specification TypeCode = "Performance" SpecificationName = "HDD">

<Value> 30 GB HDD </ Value>

</ Specification>

<Specification TypeCode = "Performance" SpecificationName = "GraphicCard">

<Value> ATI 128 Pro GL 32MB </ Value>

</ Specification>

<Specification TypeCode = "Performance" SpecificationName = "CDROM">

<Value> LG 48X CDROM </ Value>

</ Specification>

<Specification TypeCode = "Performance" SpecificationName = "SoundCard">

<Value> PCI 32 bit SoundCard </ Value>

</ Specification>

</ ProductCharacteristic>

<ProductAttachment>

<Attachment>

<AttachmentURL> http://Sambo.com/info/bs409-vm3.jpg </ AttachmentURL>

<AttachmentPurpose> Picture of computer appearance </ AttachmentPurpose>

<AttachmentMimeType> JPEG </ AttachmentMimeType>

</ Attachment>

</ ProductAttachment>

</ BasicInfo>

<SellingInfo>

<ProductVendorData PartnerRef = "sambo-2">

<SellingPrice>

<ProductPrice>

<Amount> 1.071.000 </ Amount>

</ ProductPrice>

<DiscountRate> 10 </ DiscountRate>

</ SellingPrice>

</ ProductVendorData>

</ SellingInfo>

</ ProductInfo>

</ Product>

</ ProductData>

</ ProductCatalog>

After the XML document as illustrated above is parsed by an XML parser (for example, IBM Parser, Oracle Parser, etc.), each element is in a state capable of processing. After the parsed element is identified and compared with the database schema, the element values are stored in the database.

Through this process, the stored information is retrieved through the search module, and the retrieved data is converted into XML format and used in other information systems.

So far I looked at the center of the preferred embodiment for the present invention. Those skilled in the art will appreciate that the present invention can be implemented in a modified form without departing from the essential features of the present invention. Therefore, the disclosed embodiments should be considered in descriptive sense only and not for purposes of limitation. The scope of the present invention is shown not in the above description but in the claims, and all differences within the equivalent scope should be interpreted as being included in the present invention.

According to the present invention, various product information used in an e-commerce system can be integratedly expressed, product information can be classified and expressed according to a function, information redundancy can be reduced, and recursion of elements can be classified by use. Information and product information can be expressed hierarchically, and additional information can be easily expressed.

Therefore, it can be the basis for standardizing the product catalog which is one of the infrastructures of electronic commerce.

Claims (4)

Claims [1] A computer-readable recording medium in which an XML-based data platform expressing information of one or more commodities used in an e-commerce system is recorded. A header portion representing common information of the one or more products; A body part representing detailed information of each of the one or more products; The body portion includes classification / identification information and product information for one or more products, respectively. The classification / identification information includes a classification information element indicating classification information to which the product belongs, an identification information element indicating an identification key for identifying the product, and a type information element indicating additional type information of the product, The commodity information includes a basic information element representing an essential value of a commodity, a sales information element representing sales information of a commodity seller, and a value added information element representing value added information provided by an outsider including a customer, The classification information element includes one or zero sub-classification information elements to record an XML-based data platform that collectively expresses product information used in an electronic commerce system. Computer-readable recording media. The method of claim 1, wherein the header portion One or zero base language elements representing the base language used in the product catalog description, one or zero base currency elements representing the base currency for the commodity price, and one representing information about the manufacture, sale, suppliers of the commodity, or A computer-readable recording medium on which an XML-based data platform, which collectively represents product information used in an e-commerce system, includes 0 company list elements. The method of claim 1, wherein the basic information element is XML-based integrated product information used in the e-commerce system characterized by including a product attribute element representing the product attribute information divided into one of three types of content, function / performance and form A computer-readable recording medium on which the data platform of the computer has been recorded. The method of claim 1, wherein the basic information element is Integrate the product information used in the e-commerce system, characterized in that it represents the attribute information of the parts constituting the product, and includes a component element hierarchically representing the classification information of the product including one or zero sub-component elements. A computer-readable recording medium on which an XML-based data platform is expressed.