INTERNATIONAL JOURNAL OF COMPUTER SCIENCE VOLUME 1 NUMBER 4 2006 ISSN 1306-4428

Development of a Semantic Wiki-based Feature
Library for the Extraction of Manufacturing
Feature and Manufacturing Information
Hendry Muljadi, Hideaki Takeda, and Koichi Andoparticular factory may not be the same as in the other factory.
However, in general, feature libraries are not developed in a
way that is easy to modify, especially by people without
information technology background.
On the other hand, in the context of collaboration on the web,
Wiki has proven itself to be a user-friendly interface. For
example, the community of Wikipedia.org, the free content
encyclopedia is becoming larger and larger. There have been
more than 600,000 people who gave their contributions, either
by creating or editing articles in Wikipedia. Wiki is a
discussion medium, a repository of ideas and a tool forcollaboration. It is a simple publishing system that is easy tolearn and quick to use [6]. In Wiki, people can create or edit a
Wiki page using a simple syntax to write content. So, it isnormal to make an assumption that an extended Wiki will be
useful for the development of a feature library which can beeasily modified.
However, for the development of a structured feature library,
semantic extension of Wiki is necessary. In this paper, theimplementation of Semantic Wiki for the development of afeature library is proposed.
The structure of this paper is as follows. Section 2 describes
the semantic extension of MediaWiki. Section 3 describes the
structure of the feature library. The implementation of the
Semantic Wiki for the development of the feature library is
described in section 4. Section 5 presents a case study of how
the feature library may support the extraction of manufacturingfeatures and their proper manufacturing information. Section 6
states the conclusions drawn from the research.

Abstract—A manufacturing feature can be defined simply as ageometric shape and its manufacturing information to create the shape.
In a feature-based process planning system, feature library thatconsists of pre-defined manufacturing features and the manufacturing
information to create the shape of the features, plays an important rolein the extraction of manufacturing features with their proper
manufacturing information. However, to manage the manufacturing
information flexibly, it is important to build a feature library that canbe easily modified. In this paper, the implementation of Semantic Wikifor the development of the feature library is proposed.

Keywords—Manufacturing feature, feature library, feature
ontology, process planning, Wiki, MediaWiki, Semantic Wiki.

C

I. INTRODUCTIONOMPUTER Aided Process Planning (CAPP) as means to
support human effectively to generate process plans has
been a research topic for over 35 years [1]. It offers the ability
to integrate a Computer Aided Design (CAD), which allows
automation of product design, and a Computer Aided
Manufacturing (CAM) system, which allows automation of
manufacturing. In order to allow the CAD system to interface
with the CAPP system, feature technology has emerged as theenabling technology to convert CAD product data to
manufacturing information [2]. Many different approaches
have been developed to extract features from the CAD productdata [3].
For the extraction of manufacturing features for thegeneration of process plans, it is necessary to develop a featurelibrary that consists of pre-defined features and the
manufacturing information to create the shape of the features[4].The manufacturing information consists of the required
machine and tool data, the estimated cost and time data, etc [5].
It is necessary to develop a feature library which is easy tomodify or to customize, since manufacturing technologies areprogressing, and also that manufacturing information used in a

II. MEWKISS – MEDIA WIKI WITH SIMPLE SEMANTICS
A. Extension of MediaWiki
MewKISS is an abbreviation for MediaWiki with Simple
Semantics. The word “KISS” is written with full capital lettersto stress that the proposed Semantic Wiki is developed byfollowing the KISS principle that emphasizes simplicity. The
word “KISS” is originally an abbreviation for “Keep It Simple,
Stupid!” or “Keep It Short and Simple”.
MediaWiki is the Wiki software used for the development of
MewKISS. It is a Wiki software that is written in PHP and uses
MySQL database. It is being used to run the Wikipedia and also
other encyclopedia and dictionary sites. MediaWiki is a very

Manuscript received May 24, 2006.
H.Muljadi is with the Research Organization of Information and Systems,
Tokyo, Japan (phone: 81-3-4212-2664; fax: 81-3-3556-1916; e-mail:hendry@nii.ac.jp).
H.Takeda is with the National Institute of Informatics, Tokyo, Japan (e-mail:takeda@nii.ac.jp).
K.Ando is with the Information Science and Engineering Department,
Shibaura Institute of Technology, Tokyo, Japan (e-mail: andou@
sic.shibaura-it.ac.jp).

IJCS VOLUME 1 NUMBER 4 2006 ISSN 1306-4428

265© 2006 WORLD ENFORMATIKA SOCIETYINTERNATIONAL JOURNAL OF COMPUTER SCIENCE VOLUME 1 NUMBER 4 2006 ISSN 1306-4428

useful tool for collaborative content management.
MediaWiki has the category management function thatallows a Wiki page under the namespace (“Category:”) to be
used as a metadata. Metadata is simply defined here as data
about data [7]. This function allows user to createclass-sub-class relation and class-instance relation of Wikipages. However, the metadata cannot be processed nor
manipulated easily by computer applications.
Using the existing category management function as areference, MediaWiki is extended. The extension has enabledMediaWiki to write labeled links. In other words, the extension
has enabled MediaWiki to write Resource Description
Framework (RDF) statement, which consists ofsubject-predicate-object triple. RDF is a language to express
metadata about information resource on the Web proposed by
the WWW Consortium (W3C) [8]. RDF has a simple data
model that is understandable by human and is easy forcomputer applications to process and manipulate.
The Wiki syntax to write the RDF triple is[[Term:target_page|property]].
The
RDF
tripleis<source_page><property><target_page>. Each time the Wikisyntax is used, the Wiki engine will store the RDF triple into atable in the Wiki database.
Fig.1 shows the example of the Wiki syntax writing on a
Wiki page. The Wiki page on which the syntax is written will
become the source page of the RDF triple. Fig.2 illustrates an
RDF triple that is stored in the new table of the Wiki database.
Fig.3(a), (b), (c) show how the labeled link relations are
displayed on the source_page page, target_page page andproperty page respectively. The running system of the extended
MediaWiki is available at http://semanticwiki.jp.

(a) Display of the source_page page->property->target_page(b) Display of the target_page page<-property<-source_page(c) Display of the property pagesource_page->target_page
Fig. 3 Display on the Wiki pages

B. Features of MewKISS
Fig. 4 shows the overall structure of the MewKISS. The
features of the MewKISS can be summarized as follows.
1) A collaborative lightweight metadata management. By
enabling the writing of labeled links with simple syntax,
users can create and manage relations between Wiki pages
easily and flexibly. The writing of labeled links allows users
to write and edit RDF triples even though users have noknowledge about it.
2) Navigation support. Displaying labeled links, as shown in
Fig.3, allows users to navigate the relation between Wikipages easily.
3) Mapping to other Semantic Web application. MewKISS
handles only simple RDF statements. By converting theRDF triples, which are stored in the table of MewKISS, into
XML-encoded RDF data format, the RDF triples can beexported to RDF database such as Sesame(http://openrdf.org). Using Sesame, users can explore theexported RDF triples, make queries etc [9]. Sesame can also
bridge MewKISS to other Semantic Web applications. In
other words, metadata created in MewKISS environment
can be mapped to other Semantic Web applications.
4) An integrated content and metadata management. By
extending MediaWiki, the Semantic Wiki has the benefit of
having all the functions available in MediaWiki as a

Fig. 1 Wiki syntax to write the labeled link:[[Term:target_page|property]]Homer<subject>Child<predicate>Bart<object>

Fig. 2 RDF Triple

IJCS VOLUME 1 NUMBER 4 2006 ISSN 1306-4428

266© 2006 WORLD ENFORMATIKA SOCIETYINTERNATIONAL JOURNAL OF COMPUTER SCIENCE VOLUME 1 NUMBER 4 2006 ISSN 1306-4428

and the functional data of the product design data, theautomatic extraction of manufacturing features with theirproper manufacturing information can be realized [13].

collaborative content management system. Thus, theSemantic Wiki can be used as a collaborative and integrated
content and metadata management system [10].

SESAMEWeb Server(Apache 2)labeledlink
process

RDF
ImportTABLE ICONTENTS OF FUNCTIONAL PROPERTIES
Mechanism utilzed for
Condition and direction ofBasicrealization of the basic
Function
the motionfunction
1: liner,
1: friction-mech.,
2: smooth-liner,
Transmission
2: gear-mech.,
3: very-smooth-liner,of motion
3: link-mech.,
4: round,
4: cam-mech.
5: smooth round,
6: very smooth round
1: liner,
1: rigidity-mech.,
2: weak-radial,
Constraint of
2: ball-bearing-mech.,
3: strong-radial,motion3: sliding-mech.
4: weak-thrust,
5: strong-thrust
1: bolt-and-nut,
2: bolt-only,
3: friction-mech.,Fixation of
1: stationary-object,
4: bearing-fit,
motion2: revolutionary-object
5: key-fit,
6: rivet-fit,
7: shrinkage-fit

Other
Semantic Web
Applications

RDF
ExportWiki Engine(MediaWiki 1.5.x)

MySQL
MewKISS

Table for triples

Fig. 4 Overall structure of MewKISS

Screw Thru-HoleIII. THE STRUCTURE OF THE FEATURE LIBRARY
A. Considering the Designer’s Intention for the Extractionof Manufacturing Features with their Proper Manufacturing
Information
For the extraction of proper manufacturing information tocreate the shape of manufacturing features, it is important tounderstand the designer’s intention. For example, a thru-holefeature may require a cylindrical grinding to create the shape,
while the other thru-hole feature may require threading tocreate the shape, depending on why the designer designed thegeometrical shape. Thus, it is necessary to consider thedesigner’s intention for the extraction of manufacturing feature
with their proper manufacturing information.
In this research, the designer’s intention is represented by thefunctions of the face elements that construct the features. The
face element is defined as a geometrical entity that is bounded
by a set of edges. The functional data of the face elements canbe described as basic function, mechanism utilized forrealization of the basic function, and condition and direction of
the motion. The detail explanation of the functional data
elements is given in other reports [11][12]. Table I shows thecontents of functional properties of face elements that are used
for the creation of the function feature ontology.
Fig. 5 shows an object with a screw thru-hole. Table II shows
the representation of function of the face elements that
construct the screw hole. The basic function is fixation of
motion. The mechanism utilized for realization of the basic
function is bolt-only. The condition and direction of the motion
is stationary-object.
Fig. 6 illustrates that by dealing with the geometrical data

IJCS VOLUME 1 NUMBER 4 2006 ISSN 1306-4428

Fig. 5 An object with a screw thru-hole
TABLE II
THE REPRESENTATION OF FUNCTION OF THE FACE ELEMENTS THATCONSTRUCT THE SCREW HOLE

Basic
Function
Fixation of
motionMechanism utilized
for realization of thebasic function

Condition anddirection of the motion

bolt-only

stationary-object<Design System>
Geometrical Data
Functional Data

Manufacturing Featureswith the Proper
Manufacturing Information
to Generate the Shapes

Fig. 6 Geometrical data and functional data for the automatic
extraction of manufacturing features with their proper manufacturing
information

B. Creation of the Function Feature Ontology, theManufacturing Feature Ontology, and the Relation Between
the Two Ontologies
Fig.6 shows the function feature ontology, themanufacturing feature ontology, and the relation between thetwo ontologies. Two steps for the creation of the function
feature ontology, the manufacturing feature ontology, and therelation between the two ontologies are as follows.

267© 2006 WORLD ENFORMATIKA SOCIETYINTERNATIONAL JOURNAL OF COMPUTER SCIENCE VOLUME 1 NUMBER 4 2006 ISSN 1306-4428

manufacturing feature class. Thus, by developing the featurelibrary based on the proposed structure, the structured featurelibrary is useful to support the automatic extraction of
manufacturing features with their proper manufacturing
information. The automatic extraction of manufacturingfeatures with their proper manufacturing information isimportant for the realization of a manufacturing feature-based
CAPP system.

1) Creating a function feature ontology. A function feature isdefined here as a geometric shape and its functions as
intended by the designer. For the creation of a function
feature ontology, first, features such as thru slot, step etc arelisted up. This research uses the list of features proposed in[14]. Then, sub-classes of these features are created bydescribing the required functions of the face elements that
construct the features.
2) Creating the manufacturing feature ontology. First,
manufacturing features such as step, thru slot etc are listed
up. Sub-classes of these manufacturing features are createdby describing the general manufacturing methods to create
the parent classes. Sub-classes of these sub-classes are
created to have their relation with the function feature
ontology. The relation between the classes in the lowest
level of the manufacturing feature ontology and thefunction feature ontology represents how the manufacturingfeatures should be manufactured to fulfill the required
functions of the face elements that construct the
manufacturing feature.
In Fig.6, an “internal turning and milled blind-hole” featureclass is created to relate the round blind-hole feature class of the
manufacturing feature ontology with the “round blind-holewith 2 faces require: Basic: fixation, Mechanism: bearing fit,
Motion: stationary-object, 1 face requires: Basic:constraint,
Mechanism: ball-bearing, Motion: strong-thrust” class of thefunction feature ontology. This is done since the internal
turning and milling can create the round blind-hole as intended
by the designer. Then, in the development of the feature library,a collection of possible manufacturing information, such asmachine and tool data, etc for the instances of the “internal
turning and milled blind-hole” feature class should be preparedso that when a round blind-hole feature is extracted by a feature
recognition method, and the functional properties of faceelements that construct the round blind-hole feature lead to theextraction of the “internal turning and milled blind-hole”
feature class, a proper manufacturing information can beextracted automatically from the instances of the
Function Feature
Ontology

IV. THE SEMANTIC WIKI-BASED FEATURE LIBRARY
A. Modification of MewKISS
For the development of the Semantic Wiki-based featurelibrary, further extension of MewKISS is done. New
namespaces are created. Namespace (“FF:”) is created to deal
with the function feature ontology, and namespace (“MF:”) forthe manufacturing feature ontology. New tables are also
created in the MewKISS database to deal with the newnamespaces.
B. Function Feature Ontology
For the creation of the function feature ontology, the Wikisyntax [[FF:feature_subclass|subclass]] is used (see Fig. 7).
When the Wiki syntax is written on the parent class page, theWiki engine will store the RDF triple into a table which deals
with the namespace (“FF:”) in the Semantic Wiki database. By
directly querying the table, the labeled link relation will be
displayed as follows.
1) On the parent class page: -> subclass -> feature_subclass(see Fig. 8)2) On the feature_subclass page: <- subclass <- parent class(see Fig. 9)3) On the subclass page: parent class -> feature_subclass (seeFig. 10)The “FF:subclass” page can be used to see all theclass-sub-class relations of the function feature ontology. Fig.
11 illustrates the page relations of the function feature
ontology.
Manufacturing
Feature Ontology

Function
Features

Step

Slot

Manufacturing
Features
Step

Round
Blind-Hole

Slotinternal turning andmilled blind-holeround blind-hole with 2 faces require: Basic:
fixation, Mechanism: bearing fit, Motion:
stationary-object, 1 face requires: Basic:constraint,
Mechanism: ball-bearing, Motion: strong-thrust

Round
Blind-HoleDrilledBlind-Hole

Fig. 6 Function Feature Ontology, Manufacturing Feature Ontology, and the relation between the two ontologies

IJCS VOLUME 1 NUMBER 4 2006 ISSN 1306-4428

268© 2006 WORLD ENFORMATIKA SOCIETYINTERNATIONAL JOURNAL OF COMPUTER SCIENCE VOLUME 1 NUMBER 4 2006 ISSN 1306-4428

FF:Feature
Edit Box[[FF: Slot|subclass]][[FF:Step|subclass]]

FF:subclass
Feature -> Slot
Feature -> Step-> subclass -> Slot-> subclass -> Step
has_Subclass

FF:Slot

Fig. 7 Writing the Wiki syntax [[FF:feature_subclass|subclass]]<- subclass <- Feature

has_Subclass

FF:Step<- subclass <- Feature

Fig. 11 Page relations in the function feature ontology

C. Manufacturing Feature Ontology
For the creation of the manufacturing feature ontology, theWiki syntax [[MF:feature_subclass|subclass]] is used. When
the Wiki syntax is written on the parent class page, the Wiki
engine will display the labeled link relations in the same way asin the function feature ontology. The “MF:subclass” page canbe used to see all the class-sub-class relations of the
manufacturing feature ontology.
For the class-instance relation of the manufacturing feature
ontology, Wiki syntax [[Term:instance_page|instance]] is used(see Fig. 12). When the Wiki syntax is written on the
manufacturing_feature_class page, the Wiki engine will
display the labeled link relation as follows.
1) On the manufacturing_feature_class page: -> instance ->instance_page2) On the instance_page page: <- instance <- manufacturing_
feature_class3) On the “instance” page: manufacturing_feature_class ->instance_page
On the instance_page page, relation with manufacturing
information can be written using the Wiki syntax[[Term:manufacturing_information|property]] (see Fig.13).
Metadata of the manufacturing information can also be createdeasily using the similar Wiki syntax.
Fig. 14 illustrates the page relations of the manufacturingfeature ontology, as well as the page relations between
manufacturing feature and manufacturing information.

Fig. 8 Display on the parent class pageFig. 9 Display on the feature_subclass pageFig. 12 Writing the Wiki syntax: [[Term:instance_page|instance]]

Fig. 10 Display on the subclass page

IJCS VOLUME 1 NUMBER 4 2006 ISSN 1306-4428

269© 2006 WORLD ENFORMATIKA SOCIETYINTERNATIONAL JOURNAL OF COMPUTER SCIENCE VOLUME 1 NUMBER 4 2006 ISSN 1306-4428

D. Relation between Function Feature Ontology and
Manufacturing Feature Ontology
To make the relation between the lowest sub-class of thefunction feature ontology and the lowest sub-class of the
manufacturing feature ontology, the Wiki syntax[[MF:manufacturing_feature_class|related]] is used. Fig. 15
shows the Wiki syntax writing on the function_feature_class
page. When the Wiki syntax is written on the function_feature_class page, the Wiki engine will display the labeled link relation
as follows.
1) On the function_feature_class page: -> related ->manufacturing_feature_class (see Fig. 16)
2) On the manufacturing_feature_class page: <- related <function_feature_class (see Fig. 17)3) On the “related” page: function_feature_class ->manufacturing_feature_class (see Fig. 18)
The “MF:related” page can be used to see all the relations
between the lowest sub-class of the function feature ontology
and the lowest sub-class of the manufacturing feature ontology.

Fig. 13 Writing the Wiki syntax:[[Term:manufacturing_information|property]]

sub-classsub-classsub-classsub-classinstancemachinesub-classFig. 15 Page relations in the function feature ontology

instancemachineFig. 16 Display on the lowest sub-class of the function feature
ontology

Fig. 14 Illustration of the manufacturing feature ontology and therelation with manufacturing information

IJCS VOLUME 1 NUMBER 4 2006 ISSN 1306-4428

270© 2006 WORLD ENFORMATIKA SOCIETYINTERNATIONAL JOURNAL OF COMPUTER SCIENCE VOLUME 1 NUMBER 4 2006 ISSN 1306-4428

feature recognition method which uses the graph-based
approach [15]. The detail explanation of the Extended SRG
Method is given in other report [16].
Using the Extended SRG Method, three manufacturingfeatures are extracted : a thru hole feature ( f4 , f5 ) (Fig. 21(a)), a
blind hole feature ( f1 , f2 , f3 ) (Fig. 21(b)), and a stepped-thru
hole ( f1 , f2 , f3 , f4 , f5 ) (Fig. 21(c)).
Then, using the functional data shown in Table III, theextracted features find the matched manufacturing featureclasses from the feature library. Thru hole feature ( f4 , f5 )matches the “rough internal turning thru hole” feature class,since the faces of the thru hole have no basic function, but areneeded by other functional faces. Blind hole feature ( f1 , f2 , f3 )matches the “internal turning and milled blind hole” featureclass, where internal turning process is used to machine face f1
and face f2 , and milling process to machine face f3 .
Stepped-hole feature ( f1 , f2 , f3 , f4 , f5 ) matches the “roughinternal turning and internal step turning stepped-hole” featureclass, where rough internal turning and internal step turning
process are required to manufacture the shape.

Fig. 17 Display on the lowest sub-class of the manufacturing feature
ontology

Fig. 18 Display on the “MF:Related” page

E. Discussion
As shown above, the modified MewKISS provides anenvironment for the feature library to construct the function
feature ontology, the manufacturing feature ontology, therelation between the two ontologies, and the relation between
manufacturing feature and manufacturing information. The
modified MewKISS also provides a collaborative environment
where many people can work together to manage the Semantic
Wiki-based feature library.
And since users can write page relations in RDF triple
representation, even though they have no knowledge about it,
the page relation can be processed and manipulated by othercomputer applications. In other words, by storing the metadata
in RDF triples, the metadata can also be mapped easily to otherapplications.

Fig. 19 A sketch of a Flywheel

f2

f5

V. CASE STUDY
Fig. 20 shows a part of a flywheel shown in Fig. 19 that isused for the case study here. As shown in Fig.20, a bearing will
be fixed in the hole and a shaft will rotate inside the holesmoothly. Table 3 shows the functional data properties of eachface elements.
For the extraction of manufacturing features from theproduct design information, a feature extraction method called
the Extended Super Relation Graph (SRG) Method is used. The
Extended SRG Method is an extension of SRG Method, a

IJCS VOLUME 1 NUMBER 4 2006 ISSN 1306-4428

f4

Fixingface
Constrainingface
No function
f3

f1<Flywheel><Bearing><Shaft>Fig. 20 The area of the Flywheel used for the case study and its
connection with other parts

271© 2006 WORLD ENFORMATIKA SOCIETYINTERNATIONAL JOURNAL OF COMPUTER SCIENCE VOLUME 1 NUMBER 4 2006 ISSN 1306-4428

Face
Elements
f1
f2
f3
f4
f5

TABLE IIIFUNCTIONAL DATA OF FACE ELEMENTS

Basic Function
Fixation
Fixation
Constraint
No function
No function

Mechanism utilized forrealization of the basic function
Bearing Fit
Bearing Fit
Ball-Bearing-

Fig. 22 and Fig. 23 illustrate two different kind of processplans that can be generated to manufacture the area of the
flywheel shown in Fig. 20 based on the extracted
manufacturing features and their manufacturing information.
In the first process plan, this stepped-hole will be
manufactured by three different manufacturing processes:
internal turning, milling and rough internal turning. In thesecond process plan, the stepped-hole will be manufactured by
two different manufacturing processes: rough internal turningand internal step turning. Thus, the feature library can be usefulfor the extraction of manufacturing features and their
manufacturing information that can lead to the generation ofprocess plans of a part.

Condition and direction of the
motionStationary-Object
Stationary-Object
Strong-thrust-(a) Internal Turning(b) Millingf5f4(c) Rough Internal Turning(a) Thru HoleFig. 22 Processes in Process Plan 1

f2
f3
f1
(b) Blind Holef5(a) Rough Internal Turning

f3 f2

f4
f1
(c)Stepped-Hole(b) Internal Step Turning

Fig. 21 Features extracted by the Extended SRG Method

IJCS VOLUME 1 NUMBER 4 2006 ISSN 1306-4428

Fig. 23 Processes in Process Plan 2272© 2006 WORLD ENFORMATIKA SOCIETYINTERNATIONAL JOURNAL OF COMPUTER SCIENCE VOLUME 1 NUMBER 4 2006 ISSN 1306-4428

VI. CONCLUSION[9]J.Broekstra and A.Kampman,”RDF(S) manipulation, storage andquerying using Sesame,” In Demo Proc. of the 3rd Intl. Semantic Web.
Conf., Hiroshima, 2004[10] H.Muljadi and H.Takeda,”Semantic Wiki as an integrated content andmetadata management system,” in Poster & Demonstration Proc. of the
4th Intl. Semantic Web Conf., Galway, 2005, PID-44.
[11] H.Yoshikawa and K.Ando,”Intelligent CAD in manufacturing,” Annals of
CIRP, vol.36, no.1, pp. 77-80, 1987
[12] K.Ando and H.Yoshikawa,”Generation of manufacturing information inIntelligent CAD, Annals of CIRP, vol.38, no.1, pp.133-136, 1989
[13] H.Muljadi, K.Ando and H.Takeda,”Considering designer’s intention for
the extraction of manufacturing feature,” in Proc. of the 18th Int’l Conf.
on Production Research, Salerno, 2004, in CD-ROM.
[14] W.R. Butterfield, M.K.Green, D.C.Scott and W.J.Stoker,”Part Features
for Process Planning,” Computer Aided Manufacturing International(CAM-I), Document R-86-PPP-01, 1988
[15] C.Y.Kao, S.R.T. Kumara and R.Kasturi,”Extraction of 3D object featuresfrom CAD Boundary Representation using the Super Relation Graph
Method,” IEEE Transaction on Pattern Analysis and Machine Intelligence,
vol.17, no.12, pp.1228-1233, 1995.
[16] H. Muljadi and K. Ando,”Feature Recognition Method Aiming At theGeneration of Alternative Process Plans,” in DAAAM International
Scientific Book 2005, B.Katalinic, Ed. Vienna: Danube Adria Association
for Automation & Manufacturing (DAAAM) International, 2005,
pp.449-464.

This research can be summarized as follows.
1) The feature library consists of the function feature ontology,
the manufacturing feature ontology and the manufacturing
information. The relation between the classes in the lowest
level of the manufacturing feature ontology and the function
feature ontology represents how the manufacturing features
should be manufactured to fulfill the required functions of
the face elements that construct the manufacturing feature.
2) MewKISS is modified for the development of the featurelibrary. The Semantic Wiki-based feature library is able toconstruct the function feature ontology, the manufacturingfeature ontology, the relation between the two ontologies,
and the relation between manufacturing feature andmanufacturing information.
3) As shown in the case study, the feature library is useful tosupport the automatic extraction of manufacturing features
and their proper manufacturing information for thegeneration of process plans of a part.
4) The Semantic Wiki-based feature library is a very simple
system, and people can collaborate to manage the featurelibrary. And since users can write page relations in RDF
triple representation, even though they have no knowledge
about it, the metadata can be processed and manipulated byother applications.

Dr. Hendry MULJADI is currently a project researcher at Transdisciplinary
Research Integration Center of Research Organization of Information and
Systems, Japan. He received his Doctor of Engineering degree from the
Shibaura Institute of Technology, Japan in 2004. His research interests are
CAD/CAM, production/ manufacturing system, management of technology,
and semantic web. He is a member of the Japan Society for Precision
Engineering (JSPE), the Japan Society of Mechanical Engineers (JSME), andthe Japanese Society for Artificial Intelligence (JSAI).

REFERENCES
[1]
[2]
[3]
[4]

[5]
[6]
[7]
[8]

Prof. Dr. Hideaki TAKEDA is a professor at National Institute of Informatics(NII) and The Graduate University for Advanced Studies, Japan. He is also avisiting professor at University of Tokyo. He received His Doctor ofEngineering degree from the University of Tokyo, Japan in 1991. His researchinterests are knowledge sharing system such as ontologies and community
support systems, semantic web, robotics such as intelligent artifacts, and design
theory. He is a member of The Institute of Electronics, Information andCommunication Engineers (IEICE), Information Processing Society of Japan(IPSJ), The Robotics Society of Japan, The Japan Society for Precision
Engineering, American Association for Artificial Intelligence (AAAI), and atrustee of The Japanese Society for Artificial Intelligence (JSAI).

K. Luttervelt, Report on the CIRP Working Group CAPP 2000-2003,
2003
J.H.Han and D.Rosen,”Special panel session for feature recognition at the1997 ASME Computers in Engineering Conference,” Computer-Aided
Design, vol.30, no.13, pp. 979-982, Nov. 1998.
S.R.Subrahmanyam,”A method for generation of machining and fixturingfeatures from design features,” Computer in Industry, vol.47, no.3, pp.
269-287, Mar. 2002.
M.Kanamaru, K.Ando, H.Muljadi and M.Ogawa,”Manufacturing featurelibrary for the machining process planning,” in Proc. The Japan Soc.
Precision Eng. Autumn Conf., Shimane, 2004, CD-ROM C-74 (inJapanese).
P.Scallan, Process Planning: The Design/Manufacture Interface,
Oxford:Butterworth-Heinemann, 2004, pp.41.
B.Leuf and W.Cunningham, The Wiki Way: Quick Collaboration on theWeb, Boston: Addison-Wesley, 2001, pp.14-15.
H. Takeda,” Semantic Web: A Road to the Knowledge Infrastructure on
the Internet,” New Generation Computing, vol.22, no.4, pp. 395–413,
2004.
E. Miller, R.Swick, D.Brickley (2004), Resource Description Framework(RDF). Available: http://www.w3.org/RDF/

IJCS VOLUME 1 NUMBER 4 2006 ISSN 1306-4428

Prof. Dr. Koichi ANDO is a professor at Shibaura Institute of Technology,
Japan. He received his Doctor of Engineering degree from the University ofTokyo, Japan in 1992. His research interests are Industrial Engineering,
CAD/CAM, production/manufacturing system, production management andmanagement of technology. He is a member of the Japan Society for Precision
Engineering (JSPE), the Japan Society of Mechanical Engineers (JSME), theJapan Industrial Management Association (JIMA), the Operations ResearchSociety of Japan, the Japan Ergonomics Society (JES), and the Society of Plant
Engineers Japan (SOPEJ).

273© 2006 WORLD ENFORMATIKA SOCIETY