<?xml version="1.0" encoding="UTF-8"?><?xml-stylesheet type="text/xsl" href="static/style.xsl"?><OAI-PMH xmlns="http://www.openarchives.org/OAI/2.0/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.openarchives.org/OAI/2.0/ http://www.openarchives.org/OAI/2.0/OAI-PMH.xsd"><responseDate>2026-06-29T15:17:21Z</responseDate><request verb="GetRecord" identifier="oai:docta.ucm.es:20.500.14352/133543" metadataPrefix="oai_dc">https://docta.ucm.es/rest/oai/request</request><GetRecord><record><header><identifier>oai:docta.ucm.es:20.500.14352/133543</identifier><datestamp>2026-02-28T00:47:33Z</datestamp><setSpec>com_20.500.14352_14</setSpec><setSpec>col_20.500.14352_15</setSpec></header><metadata><oai_dc:dc xmlns:oai_dc="http://www.openarchives.org/OAI/2.0/oai_dc/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:doc="http://www.lyncode.com/xoai" xsi:schemaLocation="http://www.openarchives.org/OAI/2.0/oai_dc/ http://www.openarchives.org/OAI/2.0/oai_dc.xsd">
   <dc:title>Explicit domain modelling in video games</dc:title>
   <dc:creator>Llansó, David</dc:creator>
   <dc:creator>Gómez Martín, Marco Antonio</dc:creator>
   <dc:creator>Gómez Martín, Pedro Pablo</dc:creator>
   <dc:creator>González Calero, Pedro Antonio</dc:creator>
   <dc:subject>Inteligencia artificial (Informática)</dc:subject>
   <dc:subject>1203.04 Inteligencia Artificial</dc:subject>
   <dc:description>The state-of-the-art in software engineering for game engines, recommends the use of a component-based software architecture for managing the entities in a game. A component-based architecture facilitates the definition of new types of entities as collections of components that provide basic pieces of functionality, providing a flexible software that can adapt to changes in game design. However, such flexibility comes with a price, both in terms of software understanding and error checking: a game where entity types are just run-time concepts is harder to understand than one with an explicit hierarchy of entity types; and error checking that, in a more traditional inheritance-based architecture, would come from type safety at compile time is now lost. To alleviate these problems, a component-based architecture employs blueprints, external data files that specify the particular combination of components for every entity type.
In this paper we propose an extension to the component-based architecture, substituting blueprints with a full fledged domain model in OWL, including a description of the entities, its attributes and components, along with the messages they exchange. We also describe authoring tools for building such a model and show how the model improves software understanding and error checking.</dc:description>
   <dc:description>Depto. de Ingeniería de Software e Inteligencia Artificial (ISIA)</dc:description>
   <dc:description>Fac. de Informática</dc:description>
   <dc:description>TRUE</dc:description>
   <dc:description>pub</dc:description>
   <dc:date>2026-02-27T16:57:48Z</dc:date>
   <dc:date>2026-02-27T16:57:48Z</dc:date>
   <dc:date>2011-06-29</dc:date>
   <dc:type>conference paper</dc:type>
   <dc:identifier>https://hdl.handle.net/20.500.14352/133543</dc:identifier>
   <dc:identifier>XXXX-XXXX</dc:identifier>
   <dc:identifier>10.1145/2159365.2159379</dc:identifier>
   <dc:language>eng</dc:language>
   <dc:relation>TIN2009-13692-C03-03</dc:relation>
   <dc:rights>open access</dc:rights>
   <dc:format>application/pdf</dc:format>
</oai_dc:dc></metadata></record></GetRecord></OAI-PMH>