<?xml version="1.0" encoding="UTF-8" ?>
<rdf:RDF
 xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
 xmlns="http://purl.org/rss/1.0/"
 xmlns:dc="http://purl.org/dc/elements/1.1/"
 xmlns:cc="http://web.resource.org/cc/"
 >
<!--
  This ontology document is licensed under the Creative Commons
  Attribution License. To view a copy of this license, visit
  http://creativecommons.org/licenses/by/2.0/ or send a letter to
  Creative Commons, 559 Nathan Abbott Way, Stanford, California
  94305, USA.
-->
 <channel rdf:about="http://ebiquity.umbc.edu/tag/task computing/">
  <cc:license rdf:resource="http://creativecommons.org/licenses/by/2.0/" />
  <image rdf:resource="http://ebiquity.umbc.edu/img/logo.jpg" />  <title><![CDATA[RSS Tag Search]]></title>
  <link>http://ebiquity.umbc.edu/tag/task computing/</link>
  <description><![CDATA[RSS Tag Search]]></description>
  <items>
   <rdf:Seq>
    <rdf:li resource="http://ebiquity.umbc.edu/project/html/id/38/eBiquitous-task-computing"/>
    <rdf:li resource="http://ebiquity.umbc.edu/paper/html/id/220/Policy-based-Access-Control-for-Task-Computing-Using-Rei-"/>
    <rdf:li resource="http://ebiquity.umbc.edu/event/html/id/87/Development-of-Task-Computing-Applications-and-Devices"/>
   </rdf:Seq>
  </items>
 </channel>
 <image rdf:about="http://ebiquity.umbc.edu/img/logo.jpg">
  <title>UMBC ebiquity research group</title>
  <link>http://ebiquity.umbc.edu</link>
  <url>http://ebiquity.umbc.edu/img/logo.jpg</url>
 </image>
 <item rdf:about="http://ebiquity.umbc.edu/project/html/id/38/eBiquitous-task-computing">
  <title><![CDATA[eBiquitous task computing]]></title>
  <link>http://ebiquity.umbc.edu/project/html/id/38/eBiquitous-task-computing</link>
  <description><![CDATA[Colleagues at Fujitsu's FLACP have implemented a very interesting
envinment that they call "Task Computing Environment" (TCE) that uses
standard Semantic Web (RDF, OWL, DAML-S) and Web Services (SOAP, WSDL)
technology to define, disconver, compose and deliver services.  Their
original vision was to use TCE to provide services in a pervasive
computing environment, but the framework and approach work equally
well for services in a wired environment.  



A good project would be to int...]]></description>
  <dc:date>2003-12-01</dc:date>
 </item>
 <item rdf:about="http://ebiquity.umbc.edu/paper/html/id/220/Policy-based-Access-Control-for-Task-Computing-Using-Rei-">
  <title><![CDATA[Policy-based Access Control for Task Computing Using Rei]]></title>
  <link>http://ebiquity.umbc.edu/paper/html/id/220/Policy-based-Access-Control-for-Task-Computing-Using-Rei-</link>
  <description><![CDATA[In this paper, we describe a policy-based access control
implementation for Task Computing using the Rei policy engine.  Task
Computing lets ordinary end-users accomplish complex tasks on the fly
from an open, dynamic, and distributed "universe of network-accessible
resources" in ubiquitous computing environments as well as those on
the Internet.  The Rei policy specification language is an expressive
and extensible language based on Semantic Web technologies. The Rei
policy engine rea...]]></description>
  <dc:date>2005-05-10</dc:date>
 </item>
 <item rdf:about="http://ebiquity.umbc.edu/event/html/id/87/Development-of-Task-Computing-Applications-and-Devices">
  <title><![CDATA[Development of Task Computing Applications and Devices]]></title>
  <link>http://ebiquity.umbc.edu/event/html/id/87/Development-of-Task-Computing-Applications-and-Devices</link>
  <description><![CDATA[To make Task Computing Environment more attractive and appeal it to 
customers, Fujitsu Laboratories in Japan has developed some applications
and devices based on TCE architecture.  We built demonstrations for an
office scene and a car system(ITS) combining with other technologies,
Spatial Information System(SIS) and ubiquitous IP phone.  These
demonstrations have given many people a very novel impression of
pervasive computing in the future.

Besides these applications, we have devel...]]></description>
  <dc:date>2005-03-10</dc:date>
 </item>
</rdf:RDF>

