<?xml version="1.0" encoding="utf-8"?>
<!-- generator="FeedCreator 1.7.2-ppt DokuWiki" -->
<?xml-stylesheet href="http://phoenix.labri.fr/wiki/lib/styles/feed.css" type="text/css"?>
<rdf:RDF
    xmlns="http://purl.org/rss/1.0/"
    xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
    xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
    xmlns:dc="http://purl.org/dc/elements/1.1/">
    <channel rdf:about="http://phoenix.labri.fr/wiki/feed.php">
        <title>phoenix wiki</title>
        <description></description>
        <link>http://phoenix.labri.fr/wiki/</link>
        <image rdf:resource="http://phoenix.labri.fr/wiki/lib/images/favicon.ico" />
       <dc:date>2012-05-16T23:50:55+02:00</dc:date>
        <items>
            <rdf:Seq>
                <rdf:li rdf:resource="http://phoenix.labri.fr/wiki/doku.php?id=a_dsl_for_multimedia_streaming_services&amp;amp;rev=1184083598"/>
                <rdf:li rdf:resource="http://phoenix.labri.fr/wiki/doku.php?id=a_dsl_for_telephony_services&amp;amp;rev=1171390171"/>
                <rdf:li rdf:resource="http://phoenix.labri.fr/wiki/doku.php?id=a_dsl_paradigm_for_protocol-based_service_families&amp;amp;rev=1171389129"/>
                <rdf:li rdf:resource="http://phoenix.labri.fr/wiki/doku.php?id=adaptation_in_systems_software&amp;amp;rev=1171390017"/>
                <rdf:li rdf:resource="http://phoenix.labri.fr/wiki/doku.php?id=adaptation_methodologies&amp;amp;rev=1171389942"/>
                <rdf:li rdf:resource="http://phoenix.labri.fr/wiki/doku.php?id=adaptation_tools_and_techniques&amp;amp;rev=1171390064"/>
                <rdf:li rdf:resource="http://phoenix.labri.fr/wiki/doku.php?id=an_overview_on_dsls&amp;amp;rev=1172584180"/>
                <rdf:li rdf:resource="http://phoenix.labri.fr/wiki/doku.php?id=application_areas&amp;amp;rev=1184083637"/>
                <rdf:li rdf:resource="http://phoenix.labri.fr/wiki/doku.php?id=capability-based_dsls&amp;amp;rev=1171389271"/>
                <rdf:li rdf:resource="http://phoenix.labri.fr/wiki/doku.php?id=domain-specific_language&amp;amp;rev=1177071518"/>
                <rdf:li rdf:resource="http://phoenix.labri.fr/wiki/doku.php?id=dsl&amp;amp;rev=1173709417"/>
                <rdf:li rdf:resource="http://phoenix.labri.fr/wiki/doku.php?id=dsls_for_communication_services&amp;amp;rev=1171389703"/>
                <rdf:li rdf:resource="http://phoenix.labri.fr/wiki/doku.php?id=environment&amp;amp;rev=1173894917"/>
                <rdf:li rdf:resource="http://phoenix.labri.fr/wiki/doku.php?id=framework&amp;amp;rev=1176730014"/>
                <rdf:li rdf:resource="http://phoenix.labri.fr/wiki/doku.php?id=herethefirst_title&amp;amp;rev=1317170553"/>
                <rdf:li rdf:resource="http://phoenix.labri.fr/wiki/doku.php?id=high-performance_servers&amp;amp;rev=1171389548"/>
                <rdf:li rdf:resource="http://phoenix.labri.fr/wiki/doku.php?id=high-performance_systems_components&amp;amp;rev=1171389593"/>
                <rdf:li rdf:resource="http://phoenix.labri.fr/wiki/doku.php?id=ontology&amp;amp;rev=1176972459"/>
                <rdf:li rdf:resource="http://phoenix.labri.fr/wiki/doku.php?id=pantachou&amp;amp;rev=1202825582"/>
                <rdf:li rdf:resource="http://phoenix.labri.fr/wiki/doku.php?id=pervasive_perspective&amp;amp;rev=1171375777"/>
                <rdf:li rdf:resource="http://phoenix.labri.fr/wiki/doku.php?id=programmable_client-server_model&amp;amp;rev=1171389488"/>
                <rdf:li rdf:resource="http://phoenix.labri.fr/wiki/doku.php?id=projects&amp;amp;rev=1202723480"/>
                <rdf:li rdf:resource="http://phoenix.labri.fr/wiki/doku.php?id=research&amp;amp;rev=1174485959"/>
                <rdf:li rdf:resource="http://phoenix.labri.fr/wiki/doku.php?id=resource_management&amp;amp;rev=1171389344"/>
                <rdf:li rdf:resource="http://phoenix.labri.fr/wiki/doku.php?id=service_robustness&amp;amp;rev=1171389210"/>
                <rdf:li rdf:resource="http://phoenix.labri.fr/wiki/doku.php?id=spl_session_processing_language&amp;amp;rev=1202726163"/>
                <rdf:li rdf:resource="http://phoenix.labri.fr/wiki/doku.php?id=sprint&amp;amp;rev=1173290288"/>
                <rdf:li rdf:resource="http://phoenix.labri.fr/wiki/doku.php?id=start&amp;amp;rev=1202835611"/>
                <rdf:li rdf:resource="http://phoenix.labri.fr/wiki/doku.php?id=supporting_infrastructure&amp;amp;rev=1171389448"/>
                <rdf:li rdf:resource="http://phoenix.labri.fr/wiki/doku.php?id=terminology&amp;amp;rev=1176734460"/>
                <rdf:li rdf:resource="http://phoenix.labri.fr/wiki/doku.php?id=web_resources_on_dsls&amp;amp;rev=1276180548"/>
                <rdf:li rdf:resource="http://phoenix.labri.fr/wiki/doku.php?id=writing_services&amp;amp;rev=1255023796"/>
            </rdf:Seq>
        </items>
    </channel>
    <image rdf:about="http://phoenix.labri.fr/wiki/lib/images/favicon.ico">
        <title>phoenix wiki</title>
        <link>http://phoenix.labri.fr/wiki/</link>
        <url>http://phoenix.labri.fr/wiki/lib/images/favicon.ico</url>
    </image>
    <item rdf:about="http://phoenix.labri.fr/wiki/doku.php?id=a_dsl_for_multimedia_streaming_services&amp;amp;rev=1184083598">
        <dc:format>text/html</dc:format>
        <dc:date>2007-07-10T18:06:38+02:00</dc:date>
        <title>a_dsl_for_multimedia_streaming_services</title>
        <link>http://phoenix.labri.fr/wiki/doku.php?id=a_dsl_for_multimedia_streaming_services&amp;amp;rev=1184083598</link>
        <description>Mobility and wireless raise a major challenge to the media delivery: how to mass-deliver media while mass-personalizing it to account for multiple heterogeneous rendering terminals, user requirements, network bandwidth, etc.? Such personalization involves transcoding and transforming multimedia resources along the image chain.</description>
    </item>
    <item rdf:about="http://phoenix.labri.fr/wiki/doku.php?id=a_dsl_for_telephony_services&amp;amp;rev=1171390171">
        <dc:format>text/html</dc:format>
        <dc:date>2007-02-13T19:09:31+02:00</dc:date>
        <title>a_dsl_for_telephony_services</title>
        <link>http://phoenix.labri.fr/wiki/doku.php?id=a_dsl_for_telephony_services&amp;amp;rev=1171390171</link>
        <description>IP telephony materializes the convergence between telecommunications and computer networks. This convergence is dramatically changing the face of the telecommunications domain moving from proprietary closed platforms to distributed systems based on network protocols. In particular, a telephony platform is based on a client-server model and consists of a signalling server that implements a particular signalling protocol (e.g., the Session Initiation Protocol). A signalling server is able to perfo…</description>
    </item>
    <item rdf:about="http://phoenix.labri.fr/wiki/doku.php?id=a_dsl_paradigm_for_protocol-based_service_families&amp;amp;rev=1171389129">
        <dc:format>text/html</dc:format>
        <dc:date>2007-02-13T18:52:09+02:00</dc:date>
        <title>a_dsl_paradigm_for_protocol-based_service_families</title>
        <link>http://phoenix.labri.fr/wiki/doku.php?id=a_dsl_paradigm_for_protocol-based_service_families&amp;amp;rev=1171389129</link>
        <description>Many approaches have been developed to drive the design of a DSL with respect to a specific program family. These approaches aim to discover both commonalities and variations within a program family to fuel the design process of a DSL. A step toward a methodology for DSL development was presented by Consel and Marlet. Recently, this approach has been revisited to structure the development of DSLs on the notion of program family.</description>
    </item>
    <item rdf:about="http://phoenix.labri.fr/wiki/doku.php?id=adaptation_in_systems_software&amp;amp;rev=1171390017">
        <dc:format>text/html</dc:format>
        <dc:date>2007-02-13T19:06:57+02:00</dc:date>
        <title>adaptation_in_systems_software</title>
        <link>http://phoenix.labri.fr/wiki/doku.php?id=adaptation_in_systems_software&amp;amp;rev=1171390017</link>
        <description>Adaptation in Systems Software

DSLs in Operating Systems

Integrating our adaptation methodologies and tools into the development process of real-size software systems was achieved by proposing a new development process. Specifically, we proposed a new approach to designing and structuring operating systems (OSes). This approach was based on DSLs and enables rapid development of robust OSes. Such approach is critically needed in application domain, like appliances, where new products appear at …</description>
    </item>
    <item rdf:about="http://phoenix.labri.fr/wiki/doku.php?id=adaptation_methodologies&amp;amp;rev=1171389942">
        <dc:format>text/html</dc:format>
        <dc:date>2007-02-13T19:05:42+02:00</dc:date>
        <title>adaptation_methodologies</title>
        <link>http://phoenix.labri.fr/wiki/doku.php?id=adaptation_methodologies&amp;amp;rev=1171389942</link>
        <description>Although industry has long recognized the need to develop adaptable programs, methodologies to develop them are still at the research stage. We have presented preliminary results in this area with a detailed study of the applicability of program specialization to various software architectures. Our latest contributions in this area span from a revolutionary approach based on the definition of programming languages, dedicated to a specific problem family, to a direct exploitation of specializatio…</description>
    </item>
    <item rdf:about="http://phoenix.labri.fr/wiki/doku.php?id=adaptation_tools_and_techniques&amp;amp;rev=1171390064">
        <dc:format>text/html</dc:format>
        <dc:date>2007-02-13T19:07:44+02:00</dc:date>
        <title>adaptation_tools_and_techniques</title>
        <link>http://phoenix.labri.fr/wiki/doku.php?id=adaptation_tools_and_techniques&amp;amp;rev=1171390064</link>
        <description>To further the applicability of our approach, we have strengthened and extended adaptation tools and techniques. We have produced a detailed description of the key program analysis for imperative specialization, namely binding-time analysis. This analysis is at the heart of our program specializer for C, named Tempo. We have examined the importance of the accuracy of these analyses to successfully specialize existing programs. This study was conducted in the context of systems software.</description>
    </item>
    <item rdf:about="http://phoenix.labri.fr/wiki/doku.php?id=an_overview_on_dsls&amp;amp;rev=1172584180">
        <dc:format>text/html</dc:format>
        <dc:date>2007-02-27T14:49:40+02:00</dc:date>
        <title>an_overview_on_dsls</title>
        <link>http://phoenix.labri.fr/wiki/doku.php?id=an_overview_on_dsls&amp;amp;rev=1172584180</link>
        <description>DSL - A Programming Language Perspective

 A domain-specific language (DSL) can be viewed as a programming language dedicated to a particular domain or problem. It provides appropriate built-in abstractions and notations; it is usually small, more declarative than imperative, and less expressive than a general-purpose language (GPL).</description>
    </item>
    <item rdf:about="http://phoenix.labri.fr/wiki/doku.php?id=application_areas&amp;amp;rev=1184083637">
        <dc:format>text/html</dc:format>
        <dc:date>2007-07-10T18:07:17+02:00</dc:date>
        <title>application_areas</title>
        <link>http://phoenix.labri.fr/wiki/doku.php?id=application_areas&amp;amp;rev=1184083637</link>
        <description>The previous research directions are validated in the context of realistic application areas, namely Telephony and multimedia streaming. 

	*  SPL: A DSL for Telephony Services
		*  Spidle: A DSL for Multimedia Streaming Services</description>
    </item>
    <item rdf:about="http://phoenix.labri.fr/wiki/doku.php?id=capability-based_dsls&amp;amp;rev=1171389271">
        <dc:format>text/html</dc:format>
        <dc:date>2007-02-13T18:54:31+02:00</dc:date>
        <title>capability-based_dsls</title>
        <link>http://phoenix.labri.fr/wiki/doku.php?id=capability-based_dsls&amp;amp;rev=1171389271</link>
        <description>To answer the fundamental need for innovations in terms of services, existing infrastructures have become increasingly open to external developers. Yet, this openness is done at the expense of the infrastructure robustness.

Many approaches exist to solve this problem but they all have shortcomings. In the case of Telephony, for instance, a SIP (SIP stands for Session Initiation Protocol) signalling platform allows two ways to program services. The first approach consists of offering a complete …</description>
    </item>
    <item rdf:about="http://phoenix.labri.fr/wiki/doku.php?id=domain-specific_language&amp;amp;rev=1177071518">
        <dc:format>text/html</dc:format>
        <dc:date>2007-04-20T14:18:38+02:00</dc:date>
        <title>domain-specific_language</title>
        <link>http://phoenix.labri.fr/wiki/doku.php?id=domain-specific_language&amp;amp;rev=1177071518</link>
        <description>A domain-specific language (DSL) is a specialized, problem-oriented laguage. Domain specific languages play an important role in generative programming because they are used to “order” concrete members of a system family. Domain-specific language can be textual (e.g., SQL) or graphical (e.g., the graphical specification of a GUI in a GUI builder). They can also have different levels of specialization. You can have more general modeling DSLs, for example, for expressing synchronisation constr…</description>
    </item>
    <item rdf:about="http://phoenix.labri.fr/wiki/doku.php?id=dsl&amp;amp;rev=1173709417">
        <dc:format>text/html</dc:format>
        <dc:date>2007-03-12T15:23:37+02:00</dc:date>
        <title>dsl</title>
        <link>http://phoenix.labri.fr/wiki/doku.php?id=dsl&amp;amp;rev=1173709417</link>
        <description>*  An overview on DSLs
	*  Web resources on DSLs
		*  Some existing DSLs
		*  Some DSL-related projects
		*  Some DSL-related events
		*  Some references


	*  Sprint : a framework for developing DSLs 

	*  Devil: a DSL for specifying device interfaces
	*  GAL : a DSL for programming video device drivers
	*  PLAN-P: a DSL for active networks and application-specific protocols</description>
    </item>
    <item rdf:about="http://phoenix.labri.fr/wiki/doku.php?id=dsls_for_communication_services&amp;amp;rev=1171389703">
        <dc:format>text/html</dc:format>
        <dc:date>2007-02-13T19:01:43+02:00</dc:date>
        <title>dsls_for_communication_services</title>
        <link>http://phoenix.labri.fr/wiki/doku.php?id=dsls_for_communication_services&amp;amp;rev=1171389703</link>
        <description>Domain-specific languages (DSLs) are being successfully designed, implemented and used, both academically and industrially, in a variety of areas including interactive voice menus, Web services, component configuration, and financial products, demonstrating that openness can be reconciled with robustness, without sacrificing performance.</description>
    </item>
    <item rdf:about="http://phoenix.labri.fr/wiki/doku.php?id=environment&amp;amp;rev=1173894917">
        <dc:format>text/html</dc:format>
        <dc:date>2007-03-14T18:55:17+02:00</dc:date>
        <title>environment</title>
        <link>http://phoenix.labri.fr/wiki/doku.php?id=environment&amp;amp;rev=1173894917</link>
        <description>In the ubiquitous computing context, an environment is a place composed of a set of heterogen entities that possibly interact with each other. ... to be continued...

An entity is (todo)...</description>
    </item>
    <item rdf:about="http://phoenix.labri.fr/wiki/doku.php?id=framework&amp;amp;rev=1176730014">
        <dc:format>text/html</dc:format>
        <dc:date>2007-04-16T15:26:54+02:00</dc:date>
        <title>framework</title>
        <link>http://phoenix.labri.fr/wiki/doku.php?id=framework&amp;amp;rev=1176730014</link>
        <description>Frameworks are reusable designs of all or part of a software system described by a set of abstract classes and the way instances of those classes collaborate [...] Therefore, frameworks should be developed only when many application are going to be developed within a specific problem domain. -- Evolving Frameworks, D.Roberts, R.Johnson -- PLoP’96</description>
    </item>
    <item rdf:about="http://phoenix.labri.fr/wiki/doku.php?id=herethefirst_title&amp;amp;rev=1317170553">
        <dc:format>text/html</dc:format>
        <dc:date>2011-09-28T02:42:33+02:00</dc:date>
        <title>herethefirst_title</title>
        <link>http://phoenix.labri.fr/wiki/doku.php?id=herethefirst_title&amp;amp;rev=1317170553</link>
        <description>Hi to all on this site its content</description>
    </item>
    <item rdf:about="http://phoenix.labri.fr/wiki/doku.php?id=high-performance_servers&amp;amp;rev=1171389548">
        <dc:format>text/html</dc:format>
        <dc:date>2007-02-13T18:59:08+02:00</dc:date>
        <title>high-performance_servers</title>
        <link>http://phoenix.labri.fr/wiki/doku.php?id=high-performance_servers&amp;amp;rev=1171389548</link>
        <description>All communication services rely on mechanisms implemented in network servers. For services to be efficient, responsive and scalable, not only do these mechanisms need to be efficient, but the way in which they are used by the services needs to be efficient as well. A telephony service implemented on a SIP signalling server that uses inefficient input and output primitives will perform badly and will likely be unable to handle heavy loads. The same telephony service would be just as inefficient, …</description>
    </item>
    <item rdf:about="http://phoenix.labri.fr/wiki/doku.php?id=high-performance_systems_components&amp;amp;rev=1171389593">
        <dc:format>text/html</dc:format>
        <dc:date>2007-02-13T18:59:53+02:00</dc:date>
        <title>high-performance_systems_components</title>
        <link>http://phoenix.labri.fr/wiki/doku.php?id=high-performance_systems_components&amp;amp;rev=1171389593</link>
        <description>The structure and implementation of systems components have a dramatic impact on the performance of the servers that are built on top of them. Implementing efficient support functionality in OSes involves making for efficient data processing in protocol stacks, efficient multiplexing of I/O devices in device drivers, optimal process scheduling, and efficient memory management. Since these functionalities often pose various tradeoffs depending on the needs of applications, they must be configurab…</description>
    </item>
    <item rdf:about="http://phoenix.labri.fr/wiki/doku.php?id=ontology&amp;amp;rev=1176972459">
        <dc:format>text/html</dc:format>
        <dc:date>2007-04-19T10:47:39+02:00</dc:date>
        <title>ontology</title>
        <link>http://phoenix.labri.fr/wiki/doku.php?id=ontology&amp;amp;rev=1176972459</link>
        <description>[Draft] In the software engineering world, the word “ontology” is not as common as in artificial intelligence, semantic web or knowledge representation worlds and sounds like a buzzword. Though valuable definitions for software engineering can be found in these domains, such as:</description>
    </item>
    <item rdf:about="http://phoenix.labri.fr/wiki/doku.php?id=pantachou&amp;amp;rev=1202825582">
        <dc:format>text/html</dc:format>
        <dc:date>2008-02-12T15:13:02+02:00</dc:date>
        <title>pantachou</title>
        <link>http://phoenix.labri.fr/wiki/doku.php?id=pantachou&amp;amp;rev=1202825582</link>
        <description>Status: Alpha

Keywords: DSL, service coordination, distributed environment

Description:

Coordinating entities in a networked environment has always been a significant challenge for software developers. In recent years, however, it has become even more difficult, because devices have increasingly rich capabilities, combining ever larger range of technologies (networking, multimedia, sensors, etc.).</description>
    </item>
    <item rdf:about="http://phoenix.labri.fr/wiki/doku.php?id=pervasive_perspective&amp;amp;rev=1171375777">
        <dc:format>text/html</dc:format>
        <dc:date>2007-02-13T15:09:37+02:00</dc:date>
        <title>pervasive_perspective</title>
        <link>http://phoenix.labri.fr/wiki/doku.php?id=pervasive_perspective&amp;amp;rev=1171375777</link>
        <description>Nowadays, a lot of buildings contain an amazing number of devices that have various technological functionalities. Some of them can be seen as rendering devices, like TV monitors and speakers; others are data-collecting devices like webcams and sensors; a third category is activation-based devices like lights and doors. Of course, some devices may combine more than one capability. Developing an intelligent building critically relies on the ability to combine the capabilities of the available dev…</description>
    </item>
    <item rdf:about="http://phoenix.labri.fr/wiki/doku.php?id=programmable_client-server_model&amp;amp;rev=1171389488">
        <dc:format>text/html</dc:format>
        <dc:date>2007-02-13T18:58:08+02:00</dc:date>
        <title>programmable_client-server_model</title>
        <link>http://phoenix.labri.fr/wiki/doku.php?id=programmable_client-server_model&amp;amp;rev=1171389488</link>
        <description>Although successful, the client-server model is limited in that it offers little, if any, sensitivity to the client needs. Indeed, in this model, the server consists of a fixed implementation of a set of services which greatly limits its ability to adapt to a client. Let us examine instances of this insensitivity.</description>
    </item>
    <item rdf:about="http://phoenix.labri.fr/wiki/doku.php?id=projects&amp;amp;rev=1202723480">
        <dc:format>text/html</dc:format>
        <dc:date>2008-02-11T10:51:20+02:00</dc:date>
        <title>projects</title>
        <link>http://phoenix.labri.fr/wiki/doku.php?id=projects&amp;amp;rev=1202723480</link>
        <description>SPL (Session Processing Language)

DiaGen

Pantachou</description>
    </item>
    <item rdf:about="http://phoenix.labri.fr/wiki/doku.php?id=research&amp;amp;rev=1174485959">
        <dc:format>text/html</dc:format>
        <dc:date>2007-03-21T15:05:59+02:00</dc:date>
        <title>research</title>
        <link>http://phoenix.labri.fr/wiki/doku.php?id=research&amp;amp;rev=1174485959</link>
        <description>Our proposed project builds upon results that have been obtained by the Compose research group whose aim was to study new approaches to developing adaptable software components in the domain of systems and networking, namely 

	*  Programming language technology: language design and implementation, domain-specific languages, program analysis and program transformation.
		*  Operating Systems and Networking: design, implementation and optimization.
		*  Software engineering: software architecture…</description>
    </item>
    <item rdf:about="http://phoenix.labri.fr/wiki/doku.php?id=resource_management&amp;amp;rev=1171389344">
        <dc:format>text/html</dc:format>
        <dc:date>2007-02-13T18:55:44+02:00</dc:date>
        <title>resource_management</title>
        <link>http://phoenix.labri.fr/wiki/doku.php?id=resource_management&amp;amp;rev=1171389344</link>
        <description>As explained earlier, making a platform programmable without compromising its robustness requires services to be checked and their resource usage to be strictly put in relation to the capabilities of the service user. However, one issue has not been addressed yet: how much resource is being used by a service? This issue is important because, although a service may have successfully checked and may only be using authorized resources, its execution can still degrade, or even crash, the platform. I…</description>
    </item>
    <item rdf:about="http://phoenix.labri.fr/wiki/doku.php?id=service_robustness&amp;amp;rev=1171389210">
        <dc:format>text/html</dc:format>
        <dc:date>2007-02-13T18:53:30+02:00</dc:date>
        <title>service_robustness</title>
        <link>http://phoenix.labri.fr/wiki/doku.php?id=service_robustness&amp;amp;rev=1171389210</link>
        <description>Communication platforms are increasingly opened through their programming interfaces and the standardized protocols they support. As a consequence, they are destined to be shared and fueled by as many service providers as possible. As in the context of software providers, service providers can either be companies, or individuals devoted to some community, as illustrated by the development effort of Linux. Like software, new services can only spread without restrictions if some level of robustnes…</description>
    </item>
    <item rdf:about="http://phoenix.labri.fr/wiki/doku.php?id=spl_session_processing_language&amp;amp;rev=1202726163">
        <dc:format>text/html</dc:format>
        <dc:date>2008-02-11T11:36:03+02:00</dc:date>
        <title>spl_session_processing_language</title>
        <link>http://phoenix.labri.fr/wiki/doku.php?id=spl_session_processing_language&amp;amp;rev=1202726163</link>
        <description>Status: Beta (inactive)

Keywords: IP telephony, Domain-Specific Language, SIP

Description:

The goal  of this project is to ease development of  IP telephony thanks to a domain-specific language, SPL. SPL stands for Session Processing Language. It offers abstraction to program simple and concise telephony services. The SPL compiler is able to guarantee several service properties. Hence, deployed services may not crash the telephony platform.</description>
    </item>
    <item rdf:about="http://phoenix.labri.fr/wiki/doku.php?id=sprint&amp;amp;rev=1173290288">
        <dc:format>text/html</dc:format>
        <dc:date>2007-03-07T18:58:08+02:00</dc:date>
        <title>sprint</title>
        <link>http://phoenix.labri.fr/wiki/doku.php?id=sprint&amp;amp;rev=1173290288</link>
        <description>Sprint - A Framework for Developing DSLs 

	*  Introduction
		*  Overview of the Framework
		*  Prototypes
		*  References

 

Adaptive software can be constructed from generic software components. Generic software components are parameterized to select from a family of similar behaviors. These components can then be instantiated through these parameters to adapt to different requirements on their behavior. Research in program families and domain analysis studies techniques for building families…</description>
    </item>
    <item rdf:about="http://phoenix.labri.fr/wiki/doku.php?id=start&amp;amp;rev=1202835611">
        <dc:format>text/html</dc:format>
        <dc:date>2008-02-12T18:00:11+02:00</dc:date>
        <title>start</title>
        <link>http://phoenix.labri.fr/wiki/doku.php?id=start&amp;amp;rev=1202835611</link>
        <description>Welcome to the Phoenix wiki.

You will find here some information structured in three parts: 

	*  Research : the area of applications on which Phoenix is working
	*  DSL : any information related to Domain-Specific Languages (DSL)
	*  Terminology : vocabulary and definitions used in the group</description>
    </item>
    <item rdf:about="http://phoenix.labri.fr/wiki/doku.php?id=supporting_infrastructure&amp;amp;rev=1171389448">
        <dc:format>text/html</dc:format>
        <dc:date>2007-02-13T18:57:28+02:00</dc:date>
        <title>supporting_infrastructure</title>
        <link>http://phoenix.labri.fr/wiki/doku.php?id=supporting_infrastructure&amp;amp;rev=1171389448</link>
        <description>We propose to study the layers underlying communication services. First, we are extending the client-server model to make it programmable with DSLs. Second, we concentrate on improving the performance of servers and systems components, on both the server and client sides.</description>
    </item>
    <item rdf:about="http://phoenix.labri.fr/wiki/doku.php?id=terminology&amp;amp;rev=1176734460">
        <dc:format>text/html</dc:format>
        <dc:date>2007-04-16T16:41:00+02:00</dc:date>
        <title>terminology</title>
        <link>http://phoenix.labri.fr/wiki/doku.php?id=terminology&amp;amp;rev=1176734460</link>
        <description>This page is intended to contain a set of concise definitions of the vocabulary used inside the team. If you have a login, feel free to comment, propose discussions, and modify definitions (however these definitions should remain concise if possible).</description>
    </item>
    <item rdf:about="http://phoenix.labri.fr/wiki/doku.php?id=web_resources_on_dsls&amp;amp;rev=1276180548">
        <dc:format>text/html</dc:format>
        <dc:date>2010-06-10T16:35:48+02:00</dc:date>
        <title>web_resources_on_dsls</title>
        <link>http://phoenix.labri.fr/wiki/doku.php?id=web_resources_on_dsls&amp;amp;rev=1276180548</link>
        <description>ADL A specification language (Assertion Definition Language) for programming interfaces. It can be used to describe the programmer’s interface to any C-callable function, library or system call.

ALI A language for constructing image processing applications in the domain of digital radiography [Lud94].</description>
    </item>
    <item rdf:about="http://phoenix.labri.fr/wiki/doku.php?id=writing_services&amp;amp;rev=1255023796">
        <dc:format>text/html</dc:format>
        <dc:date>2009-10-08T19:43:16+02:00</dc:date>
        <title>writing_services</title>
        <link>http://phoenix.labri.fr/wiki/doku.php?id=writing_services&amp;amp;rev=1255023796</link>
        <description>Do you find that minor subjects have been giving you more trouble than your major subjects? While you do need to accomplish the course, professors are sometimes just too demanding. You are studying engineering, yet your history professor keep bugging you that history is just as important. Well, it is important to know history and all that brouhaha but professors should not pressure students so much on minor subjects. In this case, you are studying to become an engineer, not a historian or a hist…</description>
    </item>
</rdf:RDF>

