• Journal of the Korea Society of Computer and Information
• /
• v.12 no.1 s.45
• /
• pp.9-15
• /
• 2007

As the information of the internet increased, importance of sematic web for collecting and integration of these informations to support decision making of some group or ordinary people are growing as well. Basis structure that composes semantic web is ontology and languages like XML, RDF/RDF schema and OWL are basis means that compose ontology schema. When composes and manages Ontology schema, one of the important consideration point is that schema is changed as times go by. Therefore, change of domain of schema, change of data concept or change of relation between resource etc. are reflected in the ontology system. In this study, we suggest semantic web schema management skill in terms of version management. We categorized version change forms and created version graph for checking of version transition. With created version graph, we define transitivity rule and propose schema tag for detail application which enables extending of applicable version schema.

• English Language & Literature Teaching
• /
• v.10 no.3
• /
• pp.21-40
• /
• 2004

This study Questioned what happens in L2 reading comprehension of the expository text, as measured by recall and inference-making abilities, when a L2 reader was induced to develop a content schema about the topic of a target text, but the structure of that schema departs from the structure of the target text Seventy-four. Korean university students read either the same version text twice (consistent condition) or two different version texts (inconsistent condition) with a three-day interval between the two readings. The results of a verification test indicate that, for those subjects with higher L2 reading proficiency, the inconsistent condition was more beneficial than the consistent condition for the inference-making task. On the other hand, for lower-level L2 readers, the consistent condition was more favorable for the recall task. It was concluded that inducing a structurally inconsistent schema through an L2 pre-reading would be beneficial only when the reader's L2 linguistic ability is proficient enough to produce necessary propositions from the pre-reading.

• International Journal of Advanced Culture Technology
• /
• v.8 no.1
• /
• pp.248-256
• /
• 2020

This study investigated whether the schema modes have validity in Korean adults. We examined the validity and reliability of the Schema Mode Inventory (SMI) in a Korean adult sample (N = 768; Mean age = 22.29 years; range = 19-55 years; 69.3% Males). Psychometric properties, such as factor structure, internal reliability, as well as intercorrelations among subscales were assessed. Confirmatory factor analyses yield satisfying fits for a 61-item Korean Schema Mode Inventory. Thirteen Schema Mode Inventory scales were found to have adequate reliability of the original 14 schema factors. Furthermore, the SMI scales differentiated between depressed and non-depressed participants as theoretically predicted. These findings imply that the SMI is a sound instrument to measure the schema mode model in a Korean setting for assessment prior to schema therapy.

• The Transactions of the Korea Information Processing Society
• /
• v.6 no.3
• /
• pp.553-561
• /
• 1999

The facility of schema evolution is necessary in object-oriented database applications. There exist several versions of schema and instances created under different versions of the schema concurrently in the database. This base proposes a mechanism for supporting accessing instances regardless of versions of the schema in schema evolution environments in object oriented databases. There is trade-off between the flexibility of schema modification operations and the system overhead for supporting such schema modifications. Access handling routines are provided to the undefined attributes in each version of the class. Access handling routines are also defined for each pair of semantics rather than defining backdate/update functions for each pair of versions of a class. Thus, this mechanism supports the change of semantics with reduced user and system overhead.

• The Transactions of the Korea Information Processing Society
• /
• v.7 no.12
• /
• pp.3753-3761
• /
• 2000

There exist several versions of schema and instances created under different versions of the schema concurrently in the database in schema evolution environments. This paper proposes a mechanism for accessing instances regardless of versions in schema evolution environments in object relational databases. Access handling routines are used in accessing to the instances through the undefined attributes in the versions in which they were created. The change of semantic information of attributes is supported. Access handling routines are defined for each pair of semantics rather than defining backdate/update functions for each pair of versions of a class. A query language that accommodates version and semantic information is defined through the extension of the primitive SQL format.

• The Journal of Society for e-Business Studies
• /
• v.10 no.4
• /
• pp.1-18
• /
• 2005

In ebXML, a representative framework for electronic commerce, a BPS (Business Process Specification) should be finally defined as an instance of XML-version BPSS for the configuration of B2B (Business to Business) runtime systems . In order to define the instance more complete and consistent, it is required to validate all the semantic constraints on the instance . Due to the limitations of XML Schema constructs, however, current XML-version BPSS fails to specify formal semantic constraints completely. This paper presents how to find, express and reuse BPSS semantic constraints that could not be explicitly defined in the XML-version BPSS. The method facilitates the validation of XML-version BPSS instances easily with some useful guides for fixing violations of semantic constraints. Furthermore, B2B business processes can be standardized and applied more efficiently and effectively.

• Proceedings of the CALSEC Conference
• /
• 2004.02a
• /
• pp.318-326
• /
• 2004

The ebXML (Electronic Business using eXtensible Markup Language) Specification Schema is to provide nominal set of specification elements necessary to specify a collaboration between business partners based on XML. As a part of ebXML Specification Schema, BPSS (Business Process Specification Schema) has been provided to support the direct specification of the set of elements required to configure a runtime system in order to execute a set of ebXML business transactions. The BPSS is available in two stand-alone representations, a UML version and an XML version. Due to the limitations of UML notations and XML syntax, however, current ebXML BPSS specification is insufficient to specify formal semantic constraints of modeling elements completely. In this study, we propose a classification schema for the BPSS semantic constraints and describe how to represent those semantic constraints formally using OCL (Object Constraint Language). As a way to verify a Business Process Specification (BPS) with the formal semantic constraint modeling, we suggest a rule-based approach to represent the formal constraints and to use the rule-based constraints specification to verify BPSs in a CLIPS prototype implementation.

• Journal of Digital Contents Society
• /
• v.13 no.1
• /
• pp.43-52
• /
• 2012

For accurate search on information resources, it is needed to manage gradual changes in ontology efficiently. Recently, because ontology is often written using OWL, techniques that can manage changes in OWL documents are required. To meet these needs, in this paper, we classify changeable elements to detect changes in OWL ontology and propose a storage schema that can manage the changes according to the characteristics of each element. And we suggest the possibility of improving performance of query processing using views that provide information about classes or properties in each ontology version. The proposed storage schema stores changes in metadata associated with each ontology version. In addition, it can manage metadata that must be added or deleted through reasoning when ontology changes. So, the proposed storage schema can support queries about history of changes in ontology and provide accurate and valid metadata that is suitable for user-selected ontology version.

• Journal of KIISE:Databases
• /
• v.31 no.5
• /
• pp.445-456
• /
• 2004

The database schema is assumed to be stable enough to remain valid even as the modeled environment changes. However, in practice. data models are not nearly as stable as commonly assumed by the database designers. Even though a rich set of schema change operations is provided in current database systems, the users suffer from the problem that schema change usually impacts existing application programs that have been written against the schema. In this paper, we are exploring the possible solutions to overcome this problem of impacts on the application programs. We believe that for continued support of the existing programs on the old schema, the old schema should continue to allow updates and queries, as before. Furthermore, its associated data has to be kept up-to-date. We call this the program independency property of schema change tools. For this property. we devise so-called program independency schema evolution (PISE) methodology. For each of the set of schema change operations in the relational schemas, the sketch of the additional algorithms due to the PISE compliance is presented in order to prove the comprehensiveness and soundness of our PISE methodology.

• The Journal of Information Technology and Database
• /
• v.3 no.1
• /
• pp.45-63
• /
• 1996

This paper presents an integrated object-oriented database approach for managing the evolution of products in agile manufacturing environments, Schema evolution modification facilities are provided to support full potential versioning of type definitions. All of the possible versions for a composite product are not explicitly represented to avoid version proliferation. However, valid configurations of any composite products can be provided to comply with customer demands, The attributes of composite products are classified in order to provide well-defined representation scheme for composite products and to be exploited in version control. The attributes are partitioned into composite-related and non composite-related categories. Composite-related attributes consist of subproducts and description ones. Subproducts attributes represent physical constituents of a composite product. Description attributes represent external features, assembling, and correspondence property. Interface attributes are introduced for managing configurability and version propagation. Version derivations due to the changes to the interface attributes are propagated toward the product composition hierarchy, The validity of configurations of composite products is checked by using configurability maps. Instance objects which represent the actual product instances are stored and manipulated in the database in order to support traceability during product life cycle.