<?xml version="1.0" encoding="UTF-8"?>
<mods xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://www.loc.gov/mods/v3" version="3.1" xsi:schemaLocation="http://www.loc.gov/mods/v3 http://www.loc.gov/standards/mods/v3/mods-3-1.xsd">
  <titleInfo>
    <title>Automobile business to business marketplace</title>
  </titleInfo>
  <name type="personal">
    <namePart>Santi Sasithranon</namePart>
    <role>
      <roleTerm authority="marcrelator" type="text">creator</roleTerm>
    </role>
  </name>
  <name type="personal">
    <namePart>Dung, Phan Minh</namePart>
    <role>
      <roleTerm type="text">Examination committee</roleTerm>
    </role>
  </name>
  <name type="personal">
    <namePart>Haddawy, Peter</namePart>
    <role>
      <roleTerm type="text">Chairperson</roleTerm>
    </role>
  </name>
  <name type="personal">
    <namePart>Batanov, Dentcho N.</namePart>
    <role>
      <roleTerm type="text">Examination Committee</roleTerm>
    </role>
  </name>
  <name type="corporate">
    <namePart>Vongchavalitkul University, Thailand</namePart>
    <role>
      <roleTerm type="text">Scholarship donor</roleTerm>
    </role>
  </name>
  <typeOfResource>text</typeOfResource>
  <genre authority="marc">series</genre>
  <genre authority="marc">technical report</genre>
  <originInfo>
    <place>
      <placeTerm type="code" authority="marccountry">th</placeTerm>
    </place>
    <place>
      <placeTerm type="text">Bangkok</placeTerm>
    </place>
    <publisher>Asian Institute of Technology</publisher>
    <dateIssued>2001</dateIssued>
    <issuance>continuing</issuance>
  </originInfo>
  <language>
    <languageTerm authority="iso639-2b" type="code">eng</languageTerm>
  </language>
  <physicalDescription>
    <extent>51 p.</extent>
  </physicalDescription>
  <abstract>What happens if a hundred different companies create their own schemas to describe an invoice? The schemas may contain the same elements, but each schema will use different element names. For example, all invoices will have invoice numbers, but the element names for invoice numbers may be called lnvNum, InvNo, InvoiceNo, or InvoiceNum. A hundred different XML documents will be created. It is difficult to share these documents among companies. If each business partner uses his or her own schema, we need to write a different program to work with each XML document. Clearly, we do not want to do that. We want every partner to use the same structure. The example we just described illustrates that we need for a framework for standard industry schemas. The xCBL document framework provides schemas that all eMarketplace participants can understand, so all businesses can easily exchange business documents across e-marketplaces. This research study concerns automatic xCBL document exchange. A prototype has been developed to show some xCBL documents between buyer and supplier using the automobile B2B Marketplace web site. </abstract>
  <note>A research study submitted in partial fulfillment of the requirements for the degree of Master of Engineering, School of Advanced Technologies</note>
  <note>Research Studies Project Report (M. Eng.) - Asian Institute of Technology, 2001</note>
  <subject authority="lcsh">
    <topic>Automobile industry and trade</topic>
  </subject>
  <subject authority="lcsh">
    <topic>Electronic commerce</topic>
  </subject>
  <relatedItem type="series">
    <titleInfo>
      <title>Research studies project report ; no. IM-01-01</title>
    </titleInfo>
    <name type="corporate">
      <namePart>Asian Institute of Technology.</namePart>
      <namePart/>
    </name>
  </relatedItem>
  <identifier type="uri">http://203.159.5.9/ait-thesis/detail.php?q=B07096</identifier>
  <location>
    <url displayLabel="Full-Text">http://203.159.5.9/ait-thesis/detail.php?q=B07096</url>
  </location>
  <recordInfo>
    <recordCreationDate encoding="marc">020510</recordCreationDate>
    <recordChangeDate encoding="iso8601">20260817170934.0</recordChangeDate>
  </recordInfo>
</mods>
