Alejandro Cánovas | 2 Nov 10:13 2010
Picon

Call for Associate Editors and reviewers: Advances in Network and Communications


******** Call for Associate Editors and reviewers ********

Advances in Network and Communications

ISSN: 2093-4734

http://www.humanpub.org/anc/index.html

Advances in Network and Communications is an online international journal, published by Human and
Sciences Publication (HumanPub). All papers published in this journal will be permanently available
online without charge. 

Advances in Network and Communications is published two times in a year. The goal of the ANC is to publish
peer reviewed original research result-oriented, practical, theoretical, survey, review, tutorial
papers in the various fields of Network and Communications. 

High quality submissions that advance the research and that contribute something new to the literature on
Computing & Information Technology and Telecommunications are encouraged. The special focus of the ANC
forum is to publish path-breaking applications and applied research results in the network and
communication areas.

Topics such as Security and cryptographic algorithms communication, QoS, Ad-Hoc and Sensor networks,
P2P, CDNs, Wireless Networks, Mobile and Dynamic Networks, Mesh networks, VoIP, IPTV, Cognitive Radio
Networks, Optical networks, Green Computing networks, Power Efficient and Energy Saving Networks,
Distributed/Decentralized Networks are covered (but not limited to) in this journal.

You are welcome to send this call for Associate Editors and reviewers to the mailing lists you belong to and
any people working in Network and Communications that may be interested in working on the dissemination
of the research papers in this area.
(Continue reading)

Bob Stayton | 2 Nov 17:57 2010
Picon

Re: Localization

Hi Klaus,
Regarding the lang attribute name, if you want valid DocBook documents you would use the attribute named lang for DocBook version 4 documents, and xml:lang for DocBook version 5 documents. 
 
Regarding the value of "de" versus "DE_DE", you may also see examples using "de-de", "de_DE", and other variants.  I'm not clear that there is a single standard that everyone is to adhere to, which has led to the "too much flexibility" problem you mention.
 
So the XSL stylesheets are written to handle all the variants.  The stylesheets take the value of either the lang or xml:lang attribute, convert it to lowercase, change any dash to underscore, and looks for a best match in the collection of languages supported by DocBook XSL.  The final match comes down to a locale name in the "common" directory of the XSL stylesheet distribution.  There you will find a file named 'de.xml' with a language="de" attribute.  Since DocBook XSL does not have support for country variants of German, there is a single German locale file.  So the minimum match for lang would be "de".  If you are using Chinese, you would need to use either "zh_cn" or "zh_tw".
 
The complete list of supported locales in a DocBook distribution is in common/l10n.xml (that's .xml, not .xsl), which looks like this:
 
<!ENTITY af SYSTEM "af.xml">
<!ENTITY am SYSTEM "am.xml">
<!ENTITY ar SYSTEM "ar.xml">
<!ENTITY az SYSTEM "az.xml">
<!ENTITY bg SYSTEM "bg.xml">
Strictly speaking, the stylesheet actually looks for a match on the value of the "language" attribute in those locale files, but the locale filenames match that attribute value in all cases, so you can use the list of filenames in that file as a reference.
 
Hope this helps.
 
Bob Stayton
Sagehill Enterprises
bobs <at> sagehill.net
 
 
----- Original Message -----
Sent: Sunday, October 31, 2010 12:37 PM
Subject: Re: [docbook] Localization

Bob Stayton wrote:
Hi Klaus,
I think you have misunderstood that example.  That was a snippet from a DocBook XSL localization file, not something to insert in your file.  If you want to declare a document to be German, you would add a lang="DE_DE" attribute to the root element of your document (or xml:lang if using DocBook 5).  Then the stylesheet will process it with German generated text.  If I have misunderstood your intentions, let me know.

Bob Stayton
Sagehill Enterprises
bobs <at> sagehill.net


----- Original Message ----- From: "Klaus Jantzen" <k.d.jantzen <at> t-online.de>
To: "docBook" <docbook <at> lists.oasis-open.org>
Sent: Friday, October 29, 2010 12:20 AM
Subject: [docbook] Localization


Hi,

according to the example on page 334 of "DocBook XSL" I insert the following lines in my file

<l:l10n xmlns:l="http://docbook.sourceforge.net/xmlns/l10n/1.0"
       language="de"
       english-language-name="German">

Processing the file with xsltproc under Debian lenny I get the following message

xxx.dbk:154: parser error : Premature end of data in tag l10n line 17

What is missing ?
Where can I find the documentation for this tag?

Thanks.
-- 
KDJ.

---------------------------------------------------------------------
To unsubscribe, e-mail: docbook-unsubscribe <at> lists.oasis-open.org
For additional commands, e-mail: docbook-help <at> lists.oasis-open.org





Hi Bob,

thank you very much for your help.
I did what you suggested and it works.

And with that my problems start.
You suggested >lang="DE_DE"<, in one of the books[1][2] it says >lang="de"< and somewhere it
says >xml:lang="de"< .
Now I have three notations and each works. So what is the "correct" notation?
Flexibility is nice but too much flexibility confuses.

At the moment I am somewhat confused as to where I have to look for information: [1] or [2] in case I
am stuck.

A ray of hope: in the mean time I am able to successfully use a catalog: mainly due to the complete example in [2].

Thanks again.

[1] DocBook 5 The Definitive Guide
[2] DocBook XSL 4th Edition
--
.telrow { FONT-SIZE: 80%; FONT-FAMILY: Helvetica, Arial, sans-serif } KDJ.
--------------------------------------------------------------------- To unsubscribe, e-mail: docbook-unsubscribe <at> lists.oasis-open.org For additional commands, e-mail: docbook-help <at> lists.oasis-open.org
Jaime Lloret Mauri | 9 Nov 03:20 2010
Picon

[NPA] CFP: Network Protocols and Algorithms


********************* Call for Papers ********************* 

Network Protocols and Algorithms 

ISSN 1943-3581

http://www.macrothink.org/journal/index.php/npa/

Network Protocols and Algorithms is a free-access online international journal, peer-reviewed and
published by Macrothink Institute. It publishes papers focused on the design, development, manage,
optimize or monitoring any type of network protocol, communication system, algorithm for
communication and any protocol and algorithm to communicate network devices.

The scope of the journal include, but are not limited to, the following topic areas:

- Synchronization Protocols and Algorithms
- Security Protocols and Algorithms
- QoS Protocols and Algorithms
- Ad-Hoc and Sensor Network Protocols and Algorithms
- Content Delivery Networks Protocols and Algorithms
- P2P Protocols and Algorithms
- Cluster-Based Protocols and Algorithms
- Real-Time Protocols and Algorithms
- Wireless Protocols and Algorithms
- MAC Protocols and Algorithms for Wired Networks
- Mobile wireless internet protocols and algorithms
- Delay Tolerant protocols and algorithms
- Mesh network protocols and algorithms
- Protocols and algorithms for Voice over IP delivery
- Cognitive Radio Network Protocols and Algorithms
- Monitoring and management protocols and algorithms
- optical networking protocols and algorithms
- Scalable Network Protocols and Algorithms
- Protocols and algorithms for Green Computing and Resource Allocation
- Routing Protocols and Algorithms
- Tree-based Protocols and Algorithms
- Distributed/Decentralized Algorithms for Networks
- Fault tolerant Protocols and Algorithms
- Protocols and algorithms for Mobile and Dynamic Networks
- Cross-Layer Collaborative Protocols and Algorithms
- Formal methods and cryptographic algorithms for communication
- Power Efficient and Energy Saving Network Protocols and Algorithms
- Multimedia Network Protocols and Algorithms
- Network Protocols and Algorithms for Context-Aware and Semantic Networks
- Localized Network Protocols and Algorithms
- Transport Layer Protocols
- Smart Grids protocols and algorithms

Network Protocols and Algorithms has linked its papers to references by DOI (Digital Object Identifier) numbers.

Network Protocols and Algorithms appears in the next search engines: Google Scholar, Bing, Yahoo and Ask.

Network Protocols and Algorithms is added and indexed in Index Copernicus, ProQuest, EBSCO,
Ulrichsweb.com, Directory of Open Access Journals (DOAJ), Open J-Gate, Gale, Socolar, io-port
Database, NewJour - Electronic Journals and Newsletters, Public Knowledge Project metadata
harvester, Ovid LinkSolver, Genamics JournalSeek and PublicationsList.org. It is also requested to be
included in other major Indexing Databases.

You are welcome to submit a paper or forward this call for papers to any people working in Network Protocols
and Algorithms that may be interested in submitting a paper.

The topics suggested by the journal can be discussed in term of concepts, state of the art, standards,
implementations, running experiments and applications. Proposals and deployments are also welcome.

Submission Information:
Only original and unpublished research papers will be considered in this journal. Manuscripts must be
writen in English. All submissions will be reviewed based on technical merit and relevance.
Instructions for authors and submissions can be found in http://www.macrothink.org/journal/index.php/npa/about/submissions

Jaime Lloret Mauri
Editor in Chief of the International Journal of Network Protocols and Algorithms
Associate Professor
Department of Communications
Polytechnic University of Valencia
rob.cavicchio | 9 Nov 19:24 2010

RE: Localization

Bob Stayton [bobs <at> sagehill.net] wrote:

 

>
Regarding the value of "de" versus "DE_DE", you may also see examples using "de-de", "de_DE", and other variants.  I'm not clear that there is a single standard that everyone is to adhere to, which has led to the "too much flexibility" problem you mention.

<

 

 

The most current standard I know of is RFC 5646 (http://www.rfc-editor.org/rfc/rfc5646.txt), which uses the hyphen but mandates neither a specific capitalization rule nor the use of the country code. I've never actually seen a published standard that used the underscore, but I have seen it in practical use.

 

 

*************************
Rob Cavicchio
Principal Technical Writer & Information Architect
EMC Captiva

Information Intelligence Group
EMC Corporation
3721 Valley Centre Drive, Ste 200

San Diego, CA 92130

P: (858) 320-1208
F: (858) 320-1010
E: rob.cavicchio <at> emc.com

The opinions expressed here are my personal opinions. Content published here is not read or approved in advance by EMC and does not necessarily reflect the views and opinions of EMC.

 

 

 

Bob Stayton | 16 Nov 00:07 2010
Picon

DocBook Technical Committee Meeting Agenda: 17 November 2010

DocBook Technical Committee Meeting Agenda: 17 November 2010
=============================================================

The DocBook Technical Committee will meet on Wednesday, 17 November 2010 at
01:00p EST (10:00a PST, 17:00GMT, 18:00BST, 19:00CEST, 02:00JST+,
022:30p India+) for 90 minutes.

Attendance at teleconferences is restricted to members
(and prospective members) of the committee.

This is the phone number for Wednesday's DocBook TC call:

Phone: +1-719-387-5556
 Code: 902213

The DocBook TC uses the #docbook IRC channel on
irc.freenode.org.  The IRC channel is used for exchanging
URIs, providing out-of-band comments, and other aspects
of the teleconference, so please join us there if at
all possible.

Agenda

1. Roll call
2. Accepting the minutes [1] of the previous meeting.
3. Next meeting: 17 November 2010
4. Review of the agenda.
5. Review of open action items

  a.  Norm to develop a proposal for maintaining the DocBook websites.

  b.  Bob to write up a short policy statement about the use
      of the DocBook namespace.

  c.  Bob to respond to RFE 3035565.

  d.  Norm to publish an online version of DocBook 5.0 doc.

  e.  Jirka to post the transclusion spec to docbook.org.

6.  Publishing Subcommittee report.

8.  Reltables in modular DocBook.

9.  Transclusion in DocBook.

Please see Jirka's updated proposal and discussion thread. [2]

10.  Discussion of Larry's help example in assembly and  <at> type proposal. [3]

11.  Review of Requests for Enhancement

    To browse a specific RFE, enter the URL (on one line):

      http://sourceforge.net/tracker/index.php?func=detail&;
      group_id=21935&atid=384107&aid=XXXX

    RFEs to revisit for 6.0
      1907003  biblioid content model too broad  

    RFEs to be considered 
      1679665  Add better support for modular documentation  
      2820190  add a topic element  
      2820947  Ability to transclude text 
      3035565  Allow sections at any level  
      3107140  aconym expansion inline 

-----

[1] http://lists.oasis-open.org/archives/docbook-tc/201010/msg00011.html
[2] http://lists.oasis-open.org/archives/docbook-tc/201010/msg00001.html
[3] http://lists.oasis-open.org/archives/docbook-tc/201009/msg00007.html

Bob Stayton
Sagehill Enterprises
bobs <at> sagehill.net
Bob Stayton | 18 Nov 21:22 2010
Picon

DocBook Technical Committee Meeting Minutes: 17 November 2010

DocBook Technical Committee Meeting Minutes: 17 November 2010
=============================================================

The DocBook Technical Committee met on Wednesday, 17 November 2010 at
01:00p EST (10:00a PST, 17:00GMT, 18:00BST, 19:00CEST, 02:00JST+,
022:30p India+) for 70 minutes.

1. Roll call

Present:
Paul Grosso, Dick Hamilton, Nancy Harrison, Scott Hudson,
Jirka Kosek, Larry Rowland, Bob Stayton, Norm Walsh

Regrets: Gershon Joseph

2. Accepted the minutes [1] of the previous meeting.

3. Next meeting: 15 December 2010

4. Review of the agenda.

Add discussion of the namespace usage policy statement.

5. Review of open action items

  a.  Norm to develop a proposal for maintaining the DocBook websites.
  CONTINUE

  b.  Bob to write up a short policy statement about the use
      of the DocBook namespace.
  COMPLETED

  c.  Bob to respond to RFE 3035565.
  COMPLETED

  d.  Norm to publish an online version of DocBook 5.0 doc.
  CONTINUE

  e.  Jirka to post the transclusion spec to docbook.org.
  CONTINUE

6.  Namespace usage policy

The committee agreed that the TC cannot police efforts by
users to add elements to the DocBook namespace in their
local applications.  They just should not call it DocBook
if they do.

The committee is proposing the following text submitted by
Norm to be included in the DocBook documentation:

"DocBook is used throughout the world. As one would expect in such a
broad context, DocBook is often customized to satisfy the requirements
of specific organizations or projects. The DocBook TC encourages such
customization and works hard to make sure that the schemas are as
amenable to customization as possible.

When customizers add new elements to DocBook, they often place those
elements in the DocBook namespace (http://docbook.org/ns/docbook).
There is historical precedent for this approach as DocBook's history
pre-dates namespaces and even XML. Even without precedent, users would
almost certainly encourage customizers to use the same namespace. In
many cases it simplifies authoring and almost always simplifies the
training of new authors.

However, a new element introduced into the DocBook namespace by a
local customization is not officially part of DocBook. Only the
DocBook TC can introduce new elements into DocBook officially by
publishing a new version of the standard with those elements.

That means that the practice of adding new elements comes with a cost:
the potential for confusion among authors familiar with different
customizations and the costs associated with resolving any conflicts
between interchange partners.

The DocBook TC encourages customizers to think carefully about these
costs and weight the potential tradoffs between unofficially adding
elements to DocBook and using elements in their own namespace with
care."

ACTION: Norm to incorporate this into the official docs with
appropriate links to the "If you change DocBook, it's not
DocBook any more.

7.  Publishing Subcommittee report.

Scott said the publishing schema is now a published
Committee Specification and no further work will
be done on this version.   The specs and schemas
are available on the OASIS site. [4]
There are no plans to make this an OASIS spec.

8.  Reltables in modular DocBook.

Much discussion of Larry's reltable examples,
and reltables in general. Norm asked for explanations,
and Larry and Nancy provided them.
Norm finds reltables difficult to understand.
Larry says they have implicit relationships.
Bob mentioned that DITA has strongly typed topics
for the columns, but DocBook topics do not.
Nancy stated the goal: creating linking within
an assembly.  Larry found that doing the
samples showed some features that would be
useful, like directionality of links.

ACTION: Larry to use his experience from the
samples to create a fresh proposal for linking
within assembly.

9.  Transclusion in DocBook.

Please see Jirka's updated proposal and discussion thread. [2]

Continued to next meeting.

10.  Discussion of Larry's help example in assembly and  <at> type proposal. [3]

Larry provided answers to questions.
Members could see the need to add a type attribute
to the assembly structure element.  

11.  Review of Requests for Enhancement

    To browse a specific RFE, enter the URL (on one line):

      http://sourceforge.net/tracker/index.php?func=detail&;
      group_id=21935&atid=384107&aid=XXXX

    RFEs to revisit for 6.0
      1907003  biblioid content model too broad  

    RFEs to be considered 
      1679665  Add better support for modular documentation  
      2820190  add a topic element  
      2820947  Ability to transclude text 
      3035565  Allow sections at any level  
      3107140  aconym expansion inline 

Meeting adjourned without discussion of RFEs.

-----

[1] http://lists.oasis-open.org/archives/docbook-tc/201010/msg00011.html
[2] http://lists.oasis-open.org/archives/docbook-tc/201010/msg00001.html
[3] http://lists.oasis-open.org/archives/docbook-tc/201009/msg00007.html
[4] http://www.oasis-open.org/committees/tc_home.php?wg_abbrev=docbook-publishers

Bob Stayton
Sagehill Enterprises
bobs <at> sagehill.net
Lwam Berhane | 19 Nov 09:42 2010
Picon

profiling

Hi!

Since im using Docbook im trying to profile my files. There is the 
docbook.xsl which should be replaced by the profile-docbook.xsl. I want 
to render pdf with FOP and im working with the latest Docbook Version, V5.

Which attributes and values do I need in my xml files for profiling?

Can somebody give some example code

Best regards, Lwam

punkt.de GmbH               TYPO3-Internet-Dienstleistungen-Beratung
Kaiserallee 13a             Tel.: 0721 9109-0  Fax: -100
76133 Karlsruhe             info <at> punkt.de    http://punkt.de/
AG Mannheim 108285          Gf: Jürgen Egeling
Lwam Berhane | 19 Nov 10:09 2010
Picon

calculating with xslt

Hi!

I have not such a big idea of xslt but im learning it. I'm working with 
Docbook v5, mainly print documents.

My aim: getting a table with 2 columns and several rows in a xml file.
One column for the occupation and one column for the cost.
In the last row I want to get the total amount of all occupations.

My try:

<!-- The version has nothing to do with the version of the section. I 
used it for the cost. 300 means 300 €-->
<article>
<section>
     <title id="001" version="300">Optionale Module</title>

     <para>.....</para>
     </section>
     <section>
       <title id="002" version="300">Newsletter</title>

       <para>Dauer: 3 Tag(e)</para>

       <para>..../para>
     </section>
</article>

and so on...with the following stylesheet
========================================================

     <xsl:template match="article">
     <table>
     <title>An example of complex table</title>

     <tgroup cols="2">
       <tbody>
        <row>
         <entry>
             <xsl:for-each select="section/title">
                 <para>
                     <xsl:value-of select="."/>
                 </para>
             </xsl:for-each>
         </entry>
       <entry>
         <para>
        <xsl:variable name="tmpTotal">
             <xsl:for-each select="section/title">
                       <xsl:value-of select=" <at> version"/>
                 </xsl:for-each>
              </xsl:variable>
             <xsl:variable name="myTotal" 
select="xalan:nodeset($tmpTotal)"/>
             <xsl:value-of select="sum($myTotal/entry/para)" />
         </para>
         </entry>
     </row>
    </tbody>
   </tgroup>
  </table>
  </xsl:template>
</xsl:stylesheet>

--

-- 
Gruß Lwam Berhane

punkt.de GmbH               TYPO3-Internet-Dienstleistungen-Beratung
Kaiserallee 13a             Tel.: 0721 9109-0  Fax: -100
76133 Karlsruhe             info <at> punkt.de    http://punkt.de/
AG Mannheim 108285          Gf: Jürgen Egeling
Thomas Schraitle | 19 Nov 11:08 2010
Picon

Re: [docbook] profiling

Hi,

>Since im using Docbook im trying to profile my files. There is the 
>docbook.xsl which should be replaced by the profile-docbook.xsl. I want 
>to render pdf with FOP and im working with the latest Docbook Version, V5.
>
>Which attributes and values do I need in my xml files for profiling?

Usually it's arch, os, audience, and some others. Find the complete list in
Table 26.1. Profiling attributes of [1]

>Can somebody give some example code

Well, first you need to know, which variants you need. For example,
if you write documentation for, let's say, Linux and Windows, your text
will contain two variants. As these are operating systems, the perfect match
would be the os attribute. To distinguish between these two variants you
define the values "linux" and "win".

An installation section could look like this:

 <section>
   <title>Installation</title>
   <para os="linux">To install Foo on Linux, use ...</para>
   <para os="win">To install Foo on Windows, use ...</para>
 </section>

This first step is just to mark the texts for the respective variants. You
can define complete chapters, sections or smaller pieces like paragraphs
(as in the example above) or filenames, or ...  It depends on your needs
and how you structured your text. There are almost no limitations.

The second step is the profiling or filtering step. This step "extracts"
only those pieces what you are interested in. For example, if you
are interested in Linux documentation, elements marked as "win" will
be discarded. Everything else is not affected.

As this is all perfectly explained in Bob's book, I'll refer to [1] for further
details. :)

Tom

[1] http://www.sagehill.net/docbookxsl/Profiling.html#ProfilingAttribs
Sandra Sendra | 19 Nov 15:31 2010
Picon

Deadline extension: ICDT 2011 | The Sixth International Conference on Digital Telecommunications


INVITATION:

=================
Please consider to contribute to and/or forward to the appropriate groups the following opportunity to
submit and publish original scientific results.
=================

============== ICDT 2011 | Call for Papers ===============

CALL FOR PAPERS, TUTORIALS, PANELS

ICDT 2011: The Sixth International Conference on Digital Telecommunications

April 17-22, 2011 - Budapest, Hungary

General page: http://www.iaria.org/conferences2011/ICDT11.html

Call for Papers: http://www.iaria.org/conferences2011/CfPICDT11.html

Submission deadline: December 10, 2010

Technical co-sponsors:
    Cisco Systems, Inc.
    Alcatel-Lucent
    Nokia Siemens Networks 
    Fraunhofer IGD
    ICTmc
    University Politehnica of Bucharest
    University of Erlangen-Nuremberg

Sponsored by IARIA, www.iaria.org
Extended versions of selected papers will be published in IARIA Journals: http://www.iariajournals.org
Please note the Poster Forum and Work in Progress options.

The topics suggested by the conference can be discussed in term of concepts, state of the art, research,
standards, implementations, running experiments, applications, and industrial case studies.
Authors are invited to submit complete unpublished papers, which are not under review in any other
conference or journal in the following, but not limited to, topic areas. 

All tracks are open to both research and industry contributions, in terms of Regular papers, Posters, Work
in progress, Technical/marketing/business presentations, Demos, Tutorials, and Panels.

Before submission, please check and conform with the Editorial rules: http://www.iaria.org/editorialrules.html

ICDT 2011 Topics (topics and submission details: see CfP on the site)

SIGNAL: Signal processing in telecommunications
Signal processing theory and practice; Image and multidimensional signal processing; Signal filter
design and structures; Multirate filtering, filter banks, and adaptive filters; Fast signal
processing algorithms; Nonlinear signals and systems; Nonuniform transformation; 2D nonuniform DFT;
Fast algorithm of NDFT; Advanced image/video coding; Advanced prediction techniques; Signal
detection and reconstruction; Spectral estimation and time-frequency analysis; Higher order
spectrum analysis; Parameter estimation; Array signal processing; Statistical signal analysis;
Signal and system modeling; Cyclostationary signal analysis; Active noise control, active noise
reduction and echo cancellation; Psychoacoustics and room acoustics; Signal processing for music;
Binaural systems and multidimensiona
 l signal systems; Geophysical and seismic signal processing; Nonlinear interpolation/resampling;
Extensions to wavelet based coding (x-lets); Low complexity image/video compression; Multipl!
 e resolution signal processing; New 
approach to digital signal processing; Compression of random data; Recompression of compressed data; 2D
projection of 3D data; Stereo data matching; Emerging applications requiring new compression tools;
Unified compression and recognition; H.264 and latest video coding standards; Latest audio coding
standards 

DATA: Data processing
Data transmission and reception mechanisms and techniques; Enhanced tools for video data integrity;
Data mining, filtering, and reporting; Secure data transmission; Transmission media and data
encoding; Text reading devices (super-pen, pen-elite, reading-pen); Scanned and generated lossy
(progressive) multi-page text; (Visually) lossless mechanisms; Pricing data transmission;
Differential data transmission systems; Data transmission equipments and transmission rates;
Delay-constrained data transmission; Undersea and satellite data transmission techniques;
Performance evaluation of data transmission; Multicast data transmission; High speed data
transmission; Data transmission control; Integrity and privacy in data transmission; Data
transmission standards 

AUDIO: Audio transmission and reception systems
Audio transmission and reception systems and devices; Digital audio transmission signal processing;
Audio transmission over Internet; Audio Multiplexing Transmission Systems; Stereo audio
transmission signal; Digital infrared audio transmission; Multi-stream and multi-path audio
transmission; Wireless-compressed digital audio transmission; Perceptual coding for audio
transmission and storage; Laser audio transmission; Synchronizing video and audio transmission;
Wide-band audio transmission; Index-frame audio transmission; Digital audio transmission rights;
Noise in wireless audio transmission; Audio tools and products; Standards 

VOICE: Voice over packet networks
Planning and implementing voice networks and systems; Voice transmission systems; Voice transmission
performance; Quality real-time voice transmission; Metrics for quality of voice transmission;
Stereophonic voice transmission systems; Header Compression for VoIP over WLAN; Voice over IP solution
for mobile radio interoperability; VoIP over cable TV networks; VoIP over Wi-Max

VIDEO: Video, conferencing, telephony
Digital video; Video coding formats (ITU-T, SMPTE 421M, AVS-China); Video coders and decoders;
Profiles, latency, intermediate formats; Video surveillance and privacy; Video feature
requirements; Network video recorders; Graceful degradation of archive video; Video data integrity
(error detection, tamper resistance); Alarm events for voice content (motion detection, object
tracking, face recognitions); Coding efficiency and distributed video coding; Compression and
scrambling; Enhanced tools for video data integrity; Multiple reference pictures; Intra-layer and
inter-layer prediction; Fading prediction and loop filter; Video with compression errors; Viewing
distance and perceptual quality; Video quality models; Omnidirectional video; 3D video; Video
standardization encoding; Texture synthe
 sizer 

IMAGE: Image producing, sending, and mining
Model-based progressive image transmission; Wireless image transmission; Computer generated images;
Image security, scrambling, and regions of interest; Timing requirements for image transmission;
Transmission of still and moving images; Protocols for low bit rate; Error-prone image transmission;
Energy efficient image transmission; Multi-technology image formation; Devices for image capturing
and processing (cams, web-cams, etc.); Scanning and sampling, quantization and halftoning, color
reproduction; Image representation and rendering, display and printing systems; Image quality
assessment; Image search and sorting, video indexing and editing; Integration of images and video with
other media; Image authentication and watermarking; Image storage, retrieval and multimedia; Image
and video 
 databases; Generic coding of moving pictures; Media stream packetization; Modes for archival playback;
Image-based applications; Standard for image processing; Image analysis and segmentati!
 on; Image filtering, restoration an
d enhancement; Image representation and modeling; Pattern recognition 

SPEECH: Speech producing and processing
Tooling, Architectures, Components and Standards; Voice modulation, frequencies; Linguistics,
Phonology and Phonetics; Discourse and Dialogue; Speech analysis, synthesis, coding, and
recognition; Speech enhancement and noise reduction; Speech features, production, and perception;
Speech Coding and Transmission; Speech Signal Processing; Spoken Language Generation and Synthesis;
Speech QoS Enhancement; Speaker Characterization and Recognition; Spoken Language; Resources and
Annotation; Spoken/Multi-modal Dialogue Technology and Systems; Spoken Language Information
Extraction/Retrieval; Speech Transmission Technology for the Aged and Disabled; Audio-Visual Speech
Processing; Biomedical Applications of Speech Analysis; Spoken document retrieval; Speech
Processing in a Packet; Network Environm
 ent; Automatic Speech Recognition in the Context of Mobile Communications; Human Factors in Speech and
Communication Systems; Automatic speech recognition and understanding technology; Spee!
 ch to text systems; Spoken dialog s
ystems; Multilingual language processing; New Applications of Spoken Language Technology and Systems 

IPTV: IP/Mobile TV
IPTV applications and middleware; On-demand television; Interactive TV; Broadcast TV data; Broadcast
content formats; Stereo and 3D TV; TVoDSL; Television archiving; IPTV broadcasting; IPTV-aware
devices; IPTV regulatory issues and copyrights; IPTV network infrastructure; IPTV monitoring and
management; I[P]TV usage fees; IPTV Personalization and QoS Implications 

MULTI: Multicast/Broadcast Triple-Quadruple-play
Scalable video/audio coding; Multiplexing video/audio/data; Multimedia terminals; Multimedia
systems and protocols; PSTN modems and interfaces; Facsimile terminals; Direct broadcast satellite;
Terrestrial broadcast television; Cable modems; Universal media access; Format compatibility; Media
support platforms; VoIP Quality for Triple Play; Testing triple-play services; Triple-play data
encryption; Triple-play services 

CONTENT: Production, distribution
Content injection, cashing, storage, and distribution; Producing and transmitting streaming content;
Content localization services; Content and customers profiles; Documenting and content authoring;
Authorizing topic-based content; Content customization and metadata; On-demand content; Content
retrieval from archives (alarm-based, time stamp-based); Content management solutions and systems;
Unstructured content environment; Multi-channel content delivery/publishing strategies; Content
reuse 

HXSIP: H-series towards SIP
SIP and H-xxx architectures and logical components; Instant messages and presence; Management of QoS in
SIP and H-xxx environments; Basic SIP building blocks; Security and firewalls with SIP and H-xxx series;
Service creation and telephony services with SIP and H-xxx; Multimedia conferencing with SIP and H-xxx;
SIP application scenarios; SIP (auto)configuration; SIP and H-xxx beyond VoIP; Leveraging SIP for
Global Enterprise Roaming; SIP, H-xxx and 3GPP; Emergency Calling in SIP and H-xxx; Advanced SIP and
H-xxx applications and services; SIP and H-xxx on Cable Networks; SIP and H-xxx devices; SIP and h-xxx
deployment experience; End-to-end SIP and H-xxx communications; SIP/H.323 Interworking Function for
real time communications 

MULTE: Multimedia Telecommunications
Frameworks, architectures, systems for delivering voices, audio, and data; Methodologies,
technologies, procedures and mechanisms; IMT-2000 concepts; IMS concepts (IP Multimedia Systems);
Bluetooth and WLAN coexistence on handsets; Packet-based multimedia communication systems;
Converging technology for voice and data networks; Accessibility features for unpaired users;
Confidentiality for audiovisual services; Multimedia transmission performance; Multiplexing and
synchronization; Directory services for multimedia; Computation complexity and costs (multiple
simultaneous decoders); Coding efficiency (embedded, bit-plane, arithmetic); Compatibility
between Analog/DVD and networks; IP4/IP6 transition and NAT; QoS/SLA, perceptual QoS, and formal
visual tests; Temporal and spatial scalability; 
 Pre-processing and predictive coding; Coding with regions-of-interest; Secure transcoding;
Computation power and resolution; Transform and quantization; Entropy coding; Lossless and lossy c!
 ompression; Transmission in noisy e
nvironments; Voice/video/data in 4G; Specialized medical applications; Medical imaging and
communications networks; MPEG for endoscopy, microscopy, radiology, surgery; Medical archiving
systems; Digital devices for image capturing (microscope, stethoscope); Digital equipments and
digital cinema; Digital signature protection 

MOBILE: Mobile technologies
3G+: UMTS, HSPA, HSUPA, HSDPA, HSOPA, WiMAX, UWB. LTE, All-IP LTE 4G and beyond; Seamless handover
engineering; Cognitive radio; Mobile video surveillance; Pervasive/ubiquitous/mobile systems;
Security and privacy issues for mobile and wireless systems; Mobile ad hoc networks 

MEDMAN: Control and management of multimedia telecommunication
Video codec-aware of packets; Monitoring via guard on patrol, central station, forensic analysis;
Managing single domestic licensing and granted patent pool for compressions; End-to-end quality
monitoring/management; Perceived/offered quality: video-only, audio-only, audio-video;
In-service monitoring of voice/video/data services; Real-time distributed imagery management
systems; Performance in voice/video/data systems; Distributed multimedia service management;
Mobile multimedia network management; Multi-point, multicast services management; Deployment of
multimedia services; Network management models and architectures; Billing and security for
multimedia services; Network measurement/monitoring for multimedia services

SARP: Software architecture research and practice 
Distributed software architecture; Architectural styles and patterns; Architecture refinement and
transformation; Software architecture and pervasive systems; Software architecture analysis &
testing; Architectural description languages (ADLs); Component-based software architecture;
Dynamic software architecture; Self-repairing software architecture; Adaptive software
architecture; Aspect-oriented software architecture; Service-oriented architecture [SOA]; Domain
specific software architecture [DSSA]; Tools/Environments for software architects; Product-line
software architecture; Industrial case studies and reports

STREAM: Data stream processing 
Fundamentals on data stream processing; Data stream processing and event stream processing; Continuous
query languages; Time management in data stream systems; Aggregated queries support; Query processing
with multiple, continuous, rapid, time-varying data streams; Processing frequent itemset discovery
queries; Real-time stream data processing; Network-aware operator placement for stream-processing
systems; Integrating database queries and Web searches; Scalable Distributed Stream Processing;
Optimization of data stream processing; Performance and overhead in data stream processing; QoS
adaptation in data stream systems; Adaptive query processing in data stream; Interactive distributed
data stream processing and mining; Data stream management systems; Control theory on stream
processing; P
 rocessing high-speed data streams; Stream processing in production-to-business software; Multi-site
cooperative data stream analysis; Grid-based data stream processing; Hyperdatabases for P!
 2P data stream processing; Sensor d
ata stream processing in health monitoring; Processing and sharing data streams in Grid-based P2P infrastructures

TRACK: Tracking computing technologies 
Airport security communications technologies; Hazards detection- automatic real-time
material/object recognition; Intelligent IP-based sensor networking for homeland security;
Real-time intelligence data validation and verification mechanisms; Efficient data integration and
mining techniques for NATO countries; Secure distributed storage and data pinning; SATCOM for HLS;
Critical aerospace communications systems; HLS for air, land and sea operational environments;
Airborne real-time spatial tracking techniques; Bio-authentication sensors and tools; Cyber and
physical security of key infrastructure and operations; Protection of Real-time resilient
communications network infrastructures; International standards for data schema and data sharing
between USA and other countries; Emergency respo
 nse tools; Prediction of Intent; Standards for Passenger Data Integration; Sharing Addressing and
Service Discovery in Auto-configuring MANETs; Exploiting localization and network informati!
 on (GPS, INS, GIS, terrain features
, ToA, AoA, SNR, QoS) for improved ad-hoc networking in complex terrain; Advanced indoor and outdoor
location-based applications: real-time tracking, multimedia, bidirectional, proactive
applications; Location based services based on integrated cellular, ad hoc, RFID, and sensor networks;
New positioning techniques in support of location based servcies (indoor, cellular, satellite,
hybrid); Geographic Information Systems for supporting location based services; Quality of location
data Integration of Hierarchical Location-Based Routing (HLBR) with Delay- and Disruption-Tolerant
Neworks (DTNs); Narrow-band control channels for HLBR; Location-aware (GPS-aware) Internet Browsers
for Location-based services

----------------------------
ICDT Steering Committee 
Reda Reda, ICTmc, Austria 
Constantin Paleologu, University Politehnica of Bucharest, Romania 
Tomohiko Taniguchi, Fujitsu Laboratories Limited, Japan 
Abdulrahman Yarali, Murray State University, USA 

ICDT Advisory Chairs 
Michael Grottke, University of Erlangen-Nuremberg, Germany
Weilian Su, Naval Postgraduate School - Monterey, USA
Javier Del Ser Lorente, TECNALIA RESEARCH & INNOVATION - Zamudio, Spain 

ICDT Industry Liaison Chairs 
Bilal Al Momani, Cisco Systems, Inc., Ireland
Saied Abedi, Fujitsu Laboratories of Europe Ltd. (FLE), UK
Gerard Damm, Alcatel-Lucent, France
Dan Romascanu, Avaya, Israel 

ICDT Research/Industry Chairs 
Jyrki Penttinen, Nokia Siemens Networks, Spain / Helsinki University of Technology, Finland
Klaus Drechsler, Fraunhofer Institute for Computer Graphics Research IGD - Darmstadt, Germany 

ICDT Publicity Chair 
Sandra Sendra Compte, Polytechnic University of Valencia, Spain 

Committee: http://www.iaria.org/conferences2011/ComICDT11.html
====================

Gmane