Liang-Jie Zhang | 9 Dec 18:12 2005
Picon

Table of Contents of the International Journal of Web Services Research (JWSR): 3(1), 2006


The contents of the latest issue of:

International Journal of Web Services Research (JWSR)
Official Publication of the Information Resources Management Association
Volume 3, Issue 1, January-March 2006
Published: Quarterly in Print and Electronically
ISSN: 1545-7362
EISSN: 1546-5004

Editor-In-Chief: Liang-Jie Zhang, IBM, USA

EDITORIAL PREFACE:

Jia Zhang, Associate Editor, Northern Illinois University, USA
Liang-Jie Zhang, Editor-In-Chief, IBM T.J. Watson Research Center, USA

This issue of the International Journal of Web Services Research (JWSR) collects five papers on the topics of Web services information confidentiality, transport protocol enhancements, dynamic service composition and configuration, services-oriented data access, and services-based application design and development.

RESEARCH PAPERS

PAPER ONE:

“A Dynamic Label Checking Approach for Information Flow Control in Web Services”

Zahir Tari, RMIT University, Australia
Peter Bertok, RMIT University, Australia
Dusan Simic, RMIT University, Australia

Information Flow Control (IFC) is a method of enforcing confidentiality by using labels, data structures for specifying security classifications. IFC is used in programming languages to monitor procedures in an attempt to detect and prevent information leakage. While it ensures greater security, IFC excessively restricts flow of information. This paper presents a model of information flow control using semi-discretionary label structures. The authors propose a set of rules that not only increases the flexibility of IFC but also defines labels as a practical component of a security system. The authors propose a dynamic approach using a centralized model for dynamic label checking and verify the proposed model using theoretical proofs.

To obtain a copy of the entire article, click on the link below.
http://www.idea-group.com/articles/details.asp?id=5522

PAPER TWO:

“Service-Oriented Solution Framework for Internet Banking”

Tony Chao Shan, Wachovia Corporation, USA
Winnie Wei Hua, CTS Inc., USA

This paper describes a service-oriented solution framework designed for Internet banking in financial services. A pragmatic approach is developed to help migrate conventional n-tier e-commerce systems to a service-oriented computing paradigm, composed of Service-Oriented Architecture (SOA), Integration (SOI), Process (SOP), and Management (SOM). This comprehensive framework comprises Service Patterns, Architecture Process, Hybrid Methodology, Service-Oriented Enterprise Model, and Solution Platform. E-business patterns are applied to categorize diverse online services, which form the baseline for subsequent selection justifications of appropriate technologies, products/tools, and infrastructure. A multi-level architecture process is developed to cope with the architecture complexity in a disciplined way. Furthermore, a hybrid methodology is designed to leverage the benefits of both top-down and bottom-up approaches, in which a converging layer is conceived to incorporate the latest technologies such as portal, process orchestration, Web services, service aggregations, business rule engine, and so forth.

To obtain a copy of the entire article, click on the link below.
http://www.idea-group.com/articles/details.asp?id=5523

PAPER THREE:

“Bandwidth and Latency Considerations for Efficient SOAP Messaging”

Christian Werner, University of Lübeck, Germany
Carsten Buschmann, University of Lübeck, Germany
Tobias Jäcker, University of Braunschweig, Germany
Stefan Fischer, University of Lübeck, Germany

Although Web service technology is being used in more and more distributed systems, its areas of application are inherently limited by high latencies and high amounts of protocol overhead. For messaging in environments with user interaction, like Web platforms for business or multimedia applications, the response time of the whole system needs to be kept in tight boundaries. In other scenarios including mobile communication and battery-powered devices, bandwidth-efficient communication is imperative. In this paper, the authors address both of these issues. First they conduct a detailed latency analysis of different transport mechanisms for SOAP and then thoroughly investigate their protocol overhead. For both aspects the authors present a theoretical analysis as well as experimental measurement results. A new transport binding called PURE is then introduced.

To obtain a copy of the entire article, click on the link below.
http://www.idea-group.com/articles/details.asp?id=5524

PAPER FOUR:

“Facilitating Dynamic Service Compositions by Adaptable Service Connectors”

Gang Li, Institute of Computing Technology, China
Yanbo Han, Institute of Computing Technology, China
Zhuofeng Zhao, Institute of Computing Technology, China
Jing Wang, Institute of Computing Technology and
Graduate School of the Chinese Academy of Sciences, China
Roland M. Wagner, Fraunhofer Institute for Software and Systems Engineering, Germany

Dynamic changes of services and requirements require service connection relationships adaptable in service compositions. This paper presents an adaptable service connector model and related language and tools. The model presents service connection relationships as an explicit component with which service connections can be reconfigured and changes of services involved in the interaction can be handled; this makes the service connection relationships more adaptive. With the language and tools supporting the model, services can be dynamically chained, which make service-oriented applications adapt to volatile business requirements and dynamic changeable services. The related case study and evaluation are also presented in this paper.

To obtain a copy of the entire article, click on the link below.
http://www.idea-group.com/articles/details.asp?id=5525

PAPER FIVE:

“XML Data Services”

Vinayak Borkar, BEA Systems, Inc., USA
Michael Carey, BEA Systems, Inc., USA
Nitin Mangtani, BEA Systems, Inc., USA
Denny McKinney, BEA Systems, Inc., USA
Rahul Patel, BEA Systems, Inc., USA
Sachin Thatte, BEA Systems, Inc., USA

In this paper, the authors address the question, “In the brave new world of Web services and service-oriented architectures (SOA), how does data fit in?”  They bring data modeling concepts to bear on the world of services, yielding an approach in which enterprise data access is handled by a collection of interrelated data services. It is then shown how the approach can be realized on a foundation of XML standards, namely XML Schema, Web services, and XQuery. The authors show that this approach provides a uniform and declarative framework for integrating enterprise data assets that are drawn from disparate underlying sources, including both queryable and non-queryable data sources as well as data that is encapsulated by Web services. How the approach yields data services that are easily and efficiently reusable is also explained.

To obtain a copy of the entire article, click on the link below.
http://www.idea-group.com/articles/details.asp?id=5526

*****************************************************
For full copies of the above articles, check for this issue of the International Journal of Web Services Research (JWSR) in your Institution's library.  If your library is not currently subscribed to this Journal, please recommend JWSR subscription to your librarian.
*****************************************************

Note: For only $18.00, purchase a JWSR article or any of over 1,000 single journal articles available electronically by visiting www.idea-group.com/articles.

CALL FOR PAPERS

Mission of JWSR:

Web Services are among the most important emerging technologies in the e-business, computer software and communication industries. The Web Services technologies will redefine the way that companies do business and exchange information in the twenty-first century. They will enhance business efficiency by enabling dynamic provisioning of resources from a pool of distributed resources. Due to the importance of the field, there is a significant amount of ongoing research in the areas. In a parallel effort, standardization organizations are actively developing standards for Web Services. The Web Services are creating what will become one of the most significant industries of the new century. The International Journal of Web Services Research is designed to be a valuable resource providing leading technologies, development, ideas, and trends to an international readership of researchers and engineers in the field of Web Services.

Coverage of JWSR:

Web Services architecture
Web Services security
Frameworks for building Web Service applications
Composite Web Service creation and enabling infrastructures
Web Services discovery
Resource management for Web Services
Solution Management for Web Services
Dynamic invocation mechanisms for Web Services
Quality of service for Web Services
Web Services modeling
Web Services performance
UDDI enhancements
SOAP enhancements
Case Studies for Web Services
E-Commerce applications using Web Services
Grid based Web Services applications (e.g. OGSA)
Business process integration and management using Web Services
Multimedia applications using Web Services
Mathematic foundations for service oriented computing
Communication applications using Web Services
Interactive TV applications using Web Services
Semantic services computing
Business Grid

Interested authors should consult the Journal's manuscript
submission guidelines at http://www.idea-group.com/jwsr . All submissions should be sent to the online system (http://www.servicescomputing.org/jwsr).

All inquiries should be sent to:
Editor-In-Chief: Dr. Liang-Jie Zhang at zhanglj <at> us.ibm.com
Grosso, Paul | 9 Dec 21:35 2005

RE: Deliberate breaking of indent inheritance


Jeremias,

Thank you for your interest in XSL-FO and your
detailed discussion below.

The XSL-FO SG has had many long discussions about
how inheritance works in XSL FO over the years.
We do realize that there are some consequences of
the current inheritance model that makes for some
results that may be unexpected for some users.  This
is somewhat unavoidable in that there are (at least)
two ways inheritance could work, and both ways are
useful in certain circumstances, and the current
spec picked one of those two ways. 

However, the spec is not unclear in the matter of
inheritance (I think you agree on this).  The SG has 
some indication that the various implementations are,
in fact, bringing themselves in line with the spec in
this regard.

The best way to improve the spec would be to add the 
capability of requesting the "other" form of inheritance 
for indents.  However, such an addition to the spec is 
not within the scope of the XSL 1.1 work.  

The SG would urge implementors to implement the spec
as written.  If it is felt it is important to provide
the "other" form of inheritance, it should be done via
a namespaced extension property.  Preferably, implementors
who desire such an extension can agree on its general
syntax, and perhaps a future version of XSL can incorporate
something like that.

paul

for the XSL FO SG

> -----Original Message-----
> From: xsl-editors-request <at> w3.org 
> [mailto:xsl-editors-request <at> w3.org] On Behalf Of Jeremias Maerki
> Sent: Wednesday, 2005 November 30 6:48
> To: xsl-editors <at> w3.org
> Subject: Deliberate breaking of indent inheritance
> 
> 
> Dear Editors,
> 
> a few months ago I documented my interpretation of the XSL-FO 1.0
> specification in terms of start-indent and end-indent inheritance on a
> Wiki page [1]. This is also the way I've implemented the functionality
> in Apache FOP (see 0.90 alpha1, not 0.20.5). I've come to realize that
> Apache FOP is currently the only implementation known to me 
> that doesn't
> deliberately break the property inheritance rules for start-indent and
> end-indent properties over reference-area boundaries.
> 
> The XSL WG's disposition on comment 20, item 4 in [2] clearly states
> that there's merit to stick to the rules. Obviously, I 
> personally agree
> with this decision but the situation produces unexpected results for
> inexperienced FO users. That's certainly the main point why many
> commercial implementors have chosen to break the inheritance rules in
> this case although this creates an interoperability issue.
> 
> Since today XSL-FO is possibly worse concerning interoperability than
> HTML I'd like to ask the XSL WG to reevaluate this topic and 
> to restate
> their updated opinion in this matter. I don't mind if the WG changes
> their opinion.
> 
> Furthermore, in my opinion, it is necessary to find a way to improve
> interoperability between implementations as a whole. It has become a
> major nuisance. If all implementors sticked their heads together to
> create an official test suite, it could help improve the 
> situation a lot
> and it would certainly help clarifying problem spots in the
> specification as well as put a certain pressure on implementors to
> improve interoperability. I'd be willing to invest some 
> effort in this.
> Are there other parties that would be willing to help?
> 
> [1] http://wiki.apache.org/xmlgraphics-fop/IndentInheritance
> [2] http://www.w3.org/2001/08/28-XSL-PR-DOC.html
> 
> Thank you!
> 
> Best regards,
> Jeremias Maerki
> 
> 
> 

Jeremias Maerki | 11 Dec 17:38 2005
Picon

Re: Deliberate breaking of indent inheritance


Thank you, Paul! We are very much in agreement on this topic, it seems.
This week, I've implemented an alternative set of rules that tries to
mimic the behaviour of some of the other implementations out there. The
"feature" is switched on through a configuration option. This is simply
due to user demand.

Anyway, what I'm missing a little is a reference to the topic about a
test suite for XSL-FO. It would make a very strong tool for
communicating the expected behaviour established by the specification.
What does the SG think about this?

On 09.12.2005 21:35:43 Grosso, Paul wrote:
> 
> Jeremias,
> 
> Thank you for your interest in XSL-FO and your
> detailed discussion below.
> 
> The XSL-FO SG has had many long discussions about
> how inheritance works in XSL FO over the years.
> We do realize that there are some consequences of
> the current inheritance model that makes for some
> results that may be unexpected for some users.  This
> is somewhat unavoidable in that there are (at least)
> two ways inheritance could work, and both ways are
> useful in certain circumstances, and the current
> spec picked one of those two ways. 
> 
> However, the spec is not unclear in the matter of
> inheritance (I think you agree on this).  The SG has 
> some indication that the various implementations are,
> in fact, bringing themselves in line with the spec in
> this regard.
> 
> The best way to improve the spec would be to add the 
> capability of requesting the "other" form of inheritance 
> for indents.  However, such an addition to the spec is 
> not within the scope of the XSL 1.1 work.  
> 
> The SG would urge implementors to implement the spec
> as written.  If it is felt it is important to provide
> the "other" form of inheritance, it should be done via
> a namespaced extension property.  Preferably, implementors
> who desire such an extension can agree on its general
> syntax, and perhaps a future version of XSL can incorporate
> something like that.
> 
> paul
> 
> for the XSL FO SG
> 
> > -----Original Message-----
> > From: xsl-editors-request <at> w3.org 
> > [mailto:xsl-editors-request <at> w3.org] On Behalf Of Jeremias Maerki
> > Sent: Wednesday, 2005 November 30 6:48
> > To: xsl-editors <at> w3.org
> > Subject: Deliberate breaking of indent inheritance
> > 
> > 
> > Dear Editors,
> > 
> > a few months ago I documented my interpretation of the XSL-FO 1.0
> > specification in terms of start-indent and end-indent inheritance on a
> > Wiki page [1]. This is also the way I've implemented the functionality
> > in Apache FOP (see 0.90 alpha1, not 0.20.5). I've come to realize that
> > Apache FOP is currently the only implementation known to me 
> > that doesn't
> > deliberately break the property inheritance rules for start-indent and
> > end-indent properties over reference-area boundaries.
> > 
> > The XSL WG's disposition on comment 20, item 4 in [2] clearly states
> > that there's merit to stick to the rules. Obviously, I 
> > personally agree
> > with this decision but the situation produces unexpected results for
> > inexperienced FO users. That's certainly the main point why many
> > commercial implementors have chosen to break the inheritance rules in
> > this case although this creates an interoperability issue.
> > 
> > Since today XSL-FO is possibly worse concerning interoperability than
> > HTML I'd like to ask the XSL WG to reevaluate this topic and 
> > to restate
> > their updated opinion in this matter. I don't mind if the WG changes
> > their opinion.
> > 
> > Furthermore, in my opinion, it is necessary to find a way to improve
> > interoperability between implementations as a whole. It has become a
> > major nuisance. If all implementors sticked their heads together to
> > create an official test suite, it could help improve the 
> > situation a lot
> > and it would certainly help clarifying problem spots in the
> > specification as well as put a certain pressure on implementors to
> > improve interoperability. I'd be willing to invest some 
> > effort in this.
> > Are there other parties that would be willing to help?
> > 
> > [1] http://wiki.apache.org/xmlgraphics-fop/IndentInheritance
> > [2] http://www.w3.org/2001/08/28-XSL-PR-DOC.html
> > 
> > Thank you!
> > 
> > Best regards,
> > Jeremias Maerki
> > 
> > 
> > 

Jeremias Maerki

Grosso, Paul | 11 Dec 18:07 2005

RE: Deliberate breaking of indent inheritance


> -----Original Message-----
> From: xsl-editors-request <at> w3.org 
> [mailto:xsl-editors-request <at> w3.org] On Behalf Of Jeremias Maerki
> Sent: Sunday, 2005 December 11 10:39
> To: xsl-editors <at> w3.org
> Subject: Re: Deliberate breaking of indent inheritance

> Anyway, what I'm missing a little is a reference to the topic about a
> test suite for XSL-FO. It would make a very strong tool for
> communicating the expected behaviour established by the specification.
> What does the SG think about this?

See http://www.w3.org/Style/XSL/TestSuite/ for a reference
to the XSL 1.0 test suite.  

paul

Jeremias Maerki | 11 Dec 18:46 2005
Picon

Re: Deliberate breaking of indent inheritance


Thanks, Paul, I know that one. Not that it is up-to-date (Proposed Rec
status) or extremely useful (not containing test cases for today's
problem points), unfortunately. I know that the NIST test suite was
updated a little but never officially published again. It would really
be worthwhile to start a community effort to build an official, living,
up-to-date test suite. Otherwise, we'll never have a satisfactory
interoperability level.

In the meantime, for those interested, Apache FOP now contains a
constantly growing test suite which is publicly accessible. Comments and
contributions from other implementors and adopters are more than welcome.
The individual test cases contain FOP-specific checks and only reflect
FOP's implementation status but given sufficient interest, I'm sure the
test suite could be reorganized to better accommodate other users.

On 11.12.2005 18:07:46 Grosso, Paul wrote:
> 
> 
> > -----Original Message-----
> > From: xsl-editors-request <at> w3.org 
> > [mailto:xsl-editors-request <at> w3.org] On Behalf Of Jeremias Maerki
> > Sent: Sunday, 2005 December 11 10:39
> > To: xsl-editors <at> w3.org
> > Subject: Re: Deliberate breaking of indent inheritance
> 
> > Anyway, what I'm missing a little is a reference to the topic about a
> > test suite for XSL-FO. It would make a very strong tool for
> > communicating the expected behaviour established by the specification.
> > What does the SG think about this?
> 
> See http://www.w3.org/Style/XSL/TestSuite/ for a reference
> to the XSL 1.0 test suite.  
> 
> paul

Jeremias Maerki

Grosso, Paul | 13 Dec 22:40 2005

RE: nested inlines and baseline scaling


After much discussion, the XSL FO SG agrees that the
wording in the area should be improved, but it will
take some time to have a detailed resolution.

Since this wording comes from XSL 1.0, we plan to
process it as an erratum to 1.0 and fold it into
1.1 when it is ready.  Given that this is a 1.0
erratum and not a new 1.1 issue, We do not plan 
to hold up the XSL 1.1 CR for this issue.  We do
expect to be able to fold in the resolution of this
erratum before 1.1 becomes a Rec.

paul

Paul Grosso for the XSL FO SG

> -----Original Message-----
> From: xsl-editors-request <at> w3.org 
> [mailto:xsl-editors-request <at> w3.org] On Behalf Of Manuel Mall
> Sent: Tuesday, 2005 September 27 10:03
> To: xsl-editors <at> w3.org
> Subject: nested inlines and baseline scaling
> 
> 
> My apologies for this relatively long post. I am struggling to
> come to terms with some of the fundamentals of line building.
> 
> The spec in 4.6.1 defines what a 'properly stacked' inline-area
> is. Items 1. and 2. deal with stacking in IPD and item 3 repeated here
> deals with stacking in the BPD:
> 
> "3. For any inline-area descendant I of P, the distance in the shift-
> direction from the dominant baseline of P to the alignment-point of I
> equals the offset between the dominant baseline of P and the 
> baseline of
> P corresponding to the alignment-baseline trait of I, plus the sum of
> the baseline-shifts for I and all of its ancestors which are 
> descendants
> of P.
> 
> The first summand is computed to compensate for mixed writing systems
> with different baseline types, and the other summands involve 
> deliberate
> baseline shifts for things like superscripts and subscripts."
> 
> In 7.13 there are examples given and they all work with the above
> definition.
> 
> Now lets take this example:
> 
> <fo:block>Some text
>   <fo:inline font-size=".5em"
>         dominant-baseline="reset-size"
>         alignment-baseline="text-before-edge">top
>   </fo:inline>
> </fo:block>
> 
> The inline gets a new baseline table scaled to its font-size 
> because of
> the dominant-baseline="reset-size" setting. Note that the
> dominant-baseline-indentifier has not changed. Its still "alphabetic"
> although that baseline does not align any more between the two areas
> because of the rescaling of the baseline table. Now lets give the text
> "top" a small suffix.
> 
> <fo:block>Some text
>   <fo:inline font-size=".5em"
>         dominant-baseline="reset-size"
>         alignment-baseline="text-before-edge">top
>     <fo:inline font-size=".5em" alignment-baseline="central">
>     tiny</fo:inline>
>   </fo:inline>
> </fo:block>
> 
> So "tiny" becomes some small text aligned on the central baseline as
> established after rescaling. The problem is that the positioning of
> "tiny" violates the rule 3. above on proper stacking with 
> respect to the
> line-area created by the fo:block. It is OK with respect to its direct
> ancestor but it fails when applied recursively. This is 
> because rule 3.
> doesn't cater at all for rescaling of the baseline table, it 
> only deals
> with changing the alignment point (In my example its first moved to
> "text-before-edge" and then to "central") and baseline-shifts. But I
> couldn't find anywhere in the spec a notion that baseline rescaling
> involves a baseline shift. The problem of course is that when 
> a baseline
> table is rescaled there is no uniform shift and the shift amount per
> baseline also depends on the alignment.
> 
> May be rule 3 is not meant to be applied recursively but than it its 
> formulated inconsistently with the rest of the spec.
> 
> Still seriously confused
> 
> Regards
> 
> Manuel Mall
> 
> 

Grosso, Paul | 13 Dec 22:44 2005

RE: alignment-baseline and aligment-adjust properties


It turns out it might not be as simple as some missing
or extra values.  At least some SG members believe it
is more complicated than just an editorial oversight.

Since this wording comes from XSL 1.0, we plan to
process it as an erratum to 1.0 and fold it into
1.1 when it is ready.  Given that this is a 1.0
erratum and not a new 1.1 issue, We do not plan 
to hold up the XSL 1.1 CR for this issue.  We do
expect to be able to fold in the resolution of this
erratum before 1.1 becomes a Rec.

paul

Paul Grosso for the XSL FO SG 

> -----Original Message-----
> From: xsl-editors-request <at> w3.org 
> [mailto:xsl-editors-request <at> w3.org] On Behalf Of Manuel Mall
> Sent: Wednesday, 2005 September 28 5:24
> To: xsl-editors <at> w3.org
> Subject: alignment-baseline and aligment-adjust properties
> 
> 
> This comment applies to the current spec as well as the current draft.
> 
> Both, the alignment-baseline and aligment-adjust properties 
> refer in their
> descriptions to the values "top", "bottom", "text-top", and 
> "text-bottom".
> However, in their actual definitions these values are not 
> included. I assume
> this is an editorial oversight or am I missing something?
> 
> Regards
> 
> Manuel
> 

Werner Donné | 16 Dec 14:33 2005
Picon

Possible inconsistency between XSL-FO and CSS regarding fixed positioning


Dear Editors,

If I understand it correctly, a fixed box is not repeated
on every page, because it is a child of the page-viewport-area
and each page has its own page-viewport-area.

The "absolute-position" property is, however, derived from the
CSS property "position" and it uses the definitions of the latter.
The specification of the value "fixed" [1] doesn't say literally
that the box should be repeated on every page, but the example at
the end of the paragraph suggests it. Moreover, section 9.6.1 of
the CSS2 specification [2] says it explicitly. The CSS2.1 revision
has made the spefication of "fixed" explict with respect to the
repetition [3].

Shouldn't XSL-FO comply to that? The phrase "every page" is perhaps
not precise enough. Every page of a page-sequence would be more
natural. In CSS this should be refined as well I think [4].

Best regards,

Werner.

[1] http://www.w3.org/TR/xsl11/#absolute-position
[2] http://www.w3.org/TR/1998/REC-CSS2-19980512/visuren.html#fixed-positioning
[3] http://www.w3.org/TR/CSS21/visuren.html#propdef-position
[4] http://lists.w3.org/Archives/Public/www-style/2005Dec/0078.html
--

-- 
Werner Donné  --  Re BVBA
Engelbeekstraat 8
B-3300 Tienen
tel: (+32) 486 425803	e-mail: werner.donne <at> re.be

srinivasarao vegunta | 17 Dec 08:05 2005
Picon

RE: Synchronizing text

Thanks the document is very helpful in finding the missed files
 
sri

__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com


Gmane