![](bg6.png)
specified in any way to “loc”, but both must fol-
low the Doclate structure model.
(2) Both “com” and “loc” can only create “elemon”
concepts through RT to CMM vocabularies.
Particularly, the Doclate structure elements have the
following semantics:
AN, IID, CO and RT. They exactly have the same
interpretation as in CMM, but RT refer to CMM.
Document concept display phrase DP. It is a
phase for visual display to represent concept. For
example, a concept of “an appliance, a cabinet, or a
room for storing food or other substances at a low
temperature” could be visually displayed as “refrig-
erator” or “domestic refrigerators” as needed in the
different designs of Doclate template.
Concept occurrence OC. It defines occurrence of
concept in designed Doclate template. The concept
occurrence may happen. For example, “product item”
in a purchasing order may occur many times for
different purchased items.
Value concept VALUE. This is a reification sym-
bol to introduce a reification of a concept to a par-
ticular concept, for example, “colour” → “red”.
Presentation style of reified concept PT. It de-
fines how a reified concept should be displayed. For
example, “1” could be displayed as “1”, “one”, or
“USD1/piece”. It is a logic module and implemented
in a remote namespace.
Data type of reified concept DT. It defines the
data type of the reified concept, for example, “string”
or “decimal”.
Operational function of reified concept FN. It de-
fines how the reified concept value could be com-
puted, for example, automatically generated reified
“date” value, reified computational group concept
“total”, or a result of a logic module.
With the above descriptions, common document
templates could be easily specified locally but accu-
rately maintain semantic consistency between using
parties of different levels of textile e-Marketplace.
Table 6: Textile Common Vocabulary for Garment.
concept[iid=“1.1” fc=“cotton” an=“-” ct=“-” if=“-” co=“-” rt=“-”]
concept[iid=“1.2” fc=“polyester” an=“-” ct=“-” if=“-” co=“-” rt=“-”]
concept[iid=“2” fc=“fabric” an=“-” ct=“n” if=“-” co=“-” rt=“-”]
concept[iid=“2.1” fc=“rib” an=“knit ribbing” ct=“-” if=“-” co=“-” rt=“-”]
concept[iid=“3” fc=“weight” an=“-” ct=“-” if=“-” co=“-” rt=“-”]
concept[iid=“4” fc=“coat” an=“-” ct=“-” if=“-” co=“-” rt=“-”]
concept[iid=“4.1” fc=“zipper” an=“-” ct=“-” if=“-” co=“-” rt=“-”]
concept[iid=“4.2” fc=“pocket” an=“-” ct=“-” if=“-” co=“-” rt=“-”]
concept[iid=“4.3” fc=“hood” an=“-” ct=“-” if=“-” co=“-” rt=“-”]
concept[iid=“4.3.1” fc=“drawcord” an=“-” ct=“-” if=“-” co=“-” rt=“-”]
concept[iid=“4.4” fc=“cuff” an=“-” ct=“-” if=“-” co=“-” rt=“-”]
concept[iid=“4.5” fc=“bottom” an=“-” ct=“garment” if=“-” co=“-” rt=“-”]
concept[iid=“5” fc=“size” an=“-” ct=“-” if=“-” co=“-” rt=“msr:123456”]
concept[iid=“6” fc=“use for” an=“-” ct=“-” if=“-” co=“-” rt=“hba:12345”]
concept[iid=“7” fc=“specification” an=“-” ct=“-” if=“-” co=“-” rt=“spc:1”]
4 COAT EXAMPLE ON TEXVDF
In this section, we demonstrate TexVDF approach
through a garment inquiry specified in Table 5. The
following examples will adopt the written form of
vector concept tree like “1.i...i” to represent the
concept hierarchy of any vocabulary and document
template (Guo 2008).
4.1 CMM for Coat Vocabularies
To implement the garment inquiry example, we first
design the common vocabulary, shown in Table 6,
based on CMM of definition 1.
With the above collaboratively designed garment
vocabulary commonly for all levels of textile e-
Marketplace mediators, individual mediators can
localize their personalized vocabularies applicable to
their own e-Marketplaces. Table 7 shows the local-
ized mapping for one English mediator x1 and a
Chinese mediator x2 for their own e-Marketplaces.
Table 7: Mapping of Local Vocabulary onto Common
Vocabulary.
map[iid=“1.1”, (iid1=“aa” an=“cotton”)x1, (iid2=“111” an=“棉花”)x2]
map[iid=“1.2”, (iid1=“ab” an=“polyester”)x1, (iid2=“112” an=“聚酯”)x2]
map[iid=“2”, (iid1=“b” an=“fabric”)x1, (iid2=“22” an=“面料”)x2]
map[iid=“2.1”, (iid1=“ba” an=“ribbing”)x1, (iid2=“221” an=“针织布”)x2]
map[iid=“3”, (iid1=“c” an=“weight”)x1, (iid2=“33” an=“重量”)x2]
map[iid=“4”, (iid1=“d” an=“coat”)x1, (iid2=“44” an=“上衣”)x2]
map[iid=“4.1”, (iid1=“da” an=“zipper”)x1, (iid2=“441” an=“拉链”)x2]
map[iid=“4.2”, (iid1=“db” an=“pocket”)x1, (iid2=“442” an=“口袋”)x2]
map[iid=“4.3”, (iid1=“dc” an=“hood”)x1, (iid2=“443” an=“帽子”)x2]
map[iid=“4.3.1”, (iid1=“dca” an=“drawcord”)x1, (iid2=“4411” an=“拉绳”)x2]
map[iid=“4.4”, (iid1=“dd” an=“cuff”)x1, (iid2=“444” an=“袖口”)x2]
map[iid=“4.5”, (iid1=“de” an=“bottom”)x1, (iid2=“445” an=“下摆”)x2]
map[iid=“5”, (iid1=“e” an=“size”)x1, (iid2=“55” an=“尺寸”)x2]
map[iid=“6”, (iid1=“f” an=“used by”)x1, (iid2=“66” an=“适用”)x2]
map[iid=“7”, (iid1=“g” an=“cuff”)x1, (iid2=“77” an=“规格”)x2]
Given the above local mapping onto the common
vocabulary shown in Table 6, the users of local
textile e-Marketplace of x1 and x2 can then ex-
change business information without any semantic
conflicts.
4.2 Doclate for Coat Inquiry
In this part, we exemplify the work of Doclate mod-
el in the example of Table 8 and Table 9.
Table 8: Common Document Template for Inquiry.
elemon[iid=“1” an=“” co=“” dp=“coat” oc=“” rt=“4”]
elemon[iid=“1.1” an=“-” co=“” dp=“fabric” oc=“” rt=“2”]
elemon[iid=“1.2” an=“” co=“” dp=“size” oc=“” rt=“5”]
elemon[iid=“1.3” an=“” co=“” dp=“use for” oc=“” rt=“6”]
elemon[iid=“1.4” an=“” co=“” dp=“specification” oc=“” rt=“7”]
ICE-B 2008 - International Conference on e-Business
86