Nabble - w3.org - www-di

www-di list closing, public-uwa opening

2007-04-12T09:30:06Z

Dear subscribers of www-di,

First of all i want to thank all of you who participated in the
discussions on this list the last 6 years or so.

W3C has recently closed the Device Independence Activity, which was
supporting this list.
To replace it, a new activity has now been approved, the Ubiquitous Web
Application Activity (http://www.w3.org/2007/uwa ), which is
encompassing most of DI work and extends its scope. Most of DI work
items, have been transferred to UWA. We are encouraging people to read
the charter(http://www.w3.org/2006/10/uwa-charter.html) and the activity
description (http://www.w3.org/2007/uwa/Activity ).
For that reason, this list, the public list to discuss DI work, will now
close but the archive will stay.
For those interested to follow the work of the new activity, please
subscribe to public-uwa@... (instructions at
http://www.w3.org/Mail/Request) and just follow the archives at
http://lists.w3.org/Archives/Public/public-uwa/

Best Regrads and thanks a gain for your past participation in DI and
future in UWA !

Stephane
--
Stephane Boyera stephane@...
W3C +33 (0) 4 92 38 78 34
BP 93 fax: +33 (0) 4 92 38 78 22
F-06902 Sophia Antipolis Cedex,
France

RE: Javascript mapping / implementation of DCI

2007-03-23T03:39:21Z

I know there are implementations from a DI member organisation, though the implementation was based on an earlier version of the API. Once the interface is updated to an Element based approach, and has been tested, it is my understanding that the member organisation intends to donate the implementation to the Open Source community.

---Rotan.

-----Original Message-----
From: www-di-request@... [mailto:www-di-request@...] On Behalf Of José Manuel Cantera Fonseca
Sent: 22 March 2007 10:14
To: www-di@...
Subject: Javascript mapping / implementation of DCI

Dear all,

Is there any public open source implementation of DCI in Javascript?

Where could I find the mapping to Javascript from the DCI IDL? It would
be very useful to obtain the skeleton interface in Javascript.

Thanks and best regards

RE: Javascript mapping / implementation of DCI

2007-03-22T14:01:52Z

Hi Jose,

There are implementations by some members of the DI group, but I don't
think they are in the public domain.

There is a normative ECMAScript binding defined in the DCI specification
(section 8)[1].

You should be aware that, based on feedback from the DOM interest group,
we are in the process of changing the DCI so that interfaces inherit from
DOMElement rather than DOMNode.

We will issue a new working draft when the current editor (me, actually)
finishes the remaining updates to the document.

Best wishes
Rhys

[1] http://www.w3.org/TR/DPF/#sec-ecmascriptbindings

-----Original Message-----
From: www-di-request@... [mailto:www-di-request@...] On Behalf Of
José Manuel Cantera Fonseca
Sent: 22 March 2007 10:14
To: www-di@...
Subject: Javascript mapping / implementation of DCI

Dear all,

Is there any public open source implementation of DCI in Javascript?

Where could I find the mapping to Javascript from the DCI IDL? It would be
very useful to obtain the skeleton interface in Javascript.

Thanks and best regards

Javascript mapping / implementation of DCI

2007-03-22T04:14:19Z

Dear all,

Is there any public open source implementation of DCI in Javascript?

Where could I find the mapping to Javascript from the DCI IDL? It would
be very useful to obtain the skeleton interface in Javascript.

Thanks and best regards

RE: GRDDL Going to Last Call: Relevant to DIWG

2007-02-11T23:09:16Z

Hello Harry,

Thanks for the clarification. It just helps me know whether I need to find a reviewer or not.

Thanks also for pointing out the potential advantages of GRDDL over other approaches to semantic enrichment. You have definitely helped us with our semantic enrichment work item.

Thanks again and good luck with the last call.

Very best wishes
Rhys

-----Original Message-----
From: www-di-request@... [mailto:www-di-request@...] On Behalf Of Harry Halpin
Sent: 09 February 2007 17:57
To: Rhys.Lewis@...
Cc: www-di@...; w3c-di-wg@...
Subject: Re: GRDDL Going to Last Call: Relevant to DIWG

(trying to cc w3c-di-wg@...).

I do not believe a formal review is needed as there is no dependency we believe between DIWG and GRDDL. However, we do believe that GRDDL might be of use to DIWG and we do believe that GRDDL as it stands fulfills our charter, which mentions DIWG [1].

"The Device Independence Working Group
<http://www.w3.org/2001/di/Group/> has a Semantic Enrichment for Device Independence work item <http://www.w3.org/2004/05/di-charter-2004-06.html#author-semantic-enrichment>
etc; the two groups should investigate whether implementations of GRDDL on mobile devices may contribute to these work item"

I think GRDDL is actually both more lightweight, requiring minimal or, and if the namespace document contains the transfomraiton, no change XHTML documents in order to retrieve semantics in the form of RDF from them.

However, HTML layout information is lost in translation to RDF ofcourse.
However, Ben Adida is working on a hGRDDL transform that transforms microformats -> RDFa+XHTML that keeps the HTML in place [2]. Hopefully there will be more progress on that front!

thanks,
harry

[1]http://www.w3.org/2006/07/grddl-charter.html
[2]http://www.w3.org/2006/07/SWD/wiki/hGRDDL_Example

Rhys Lewis wrote:

> Hello Harry,
>
> Thanks very much for your note about GRDDL going to last call soon.
>
> First impressions do confirm your assertion that GRDDL makes a major
> contribution to the item we had labelled 'semantic enrichment' in our
> current charter. Actually, we had concluded that the 'role' attribute
> and some likely extensions in XHTML Version 2 would probably meet our
> needs in this area. GRDDL looks to go beyond those capabilities.
>
> I've taken the liberty of copying your note to our internal working
> group list (w3c-di-wg@... <mailto:w3c-di-wg@...>). That's where
> we normally carry out group discussions.
>
> Perhaps you could indicate, on that list, whether the GRDDL working
> group is likely to request DIWG as one of the formal reviewers for the
> GRDDL documents?
>
> Best wishes
> Rhys Lewis, chair DIWG
>
>

--
-harry

Harry Halpin, University of Edinburgh
http://www.ibiblio.org/hhalpin 6B522426

Re: GRDDL Going to Last Call: Relevant to DIWG

2007-02-09T09:57:12Z

(trying to cc w3c-di-wg@...).

I do not believe a formal review is needed as there is no dependency we
believe between DIWG and GRDDL. However, we do believe that GRDDL might
be of use to DIWG and we do believe that GRDDL as it stands fulfills our
charter, which mentions DIWG [1].

"The Device Independence Working Group
<http://www.w3.org/2001/di/Group/> has a Semantic Enrichment for Device
Independence work item
<http://www.w3.org/2004/05/di-charter-2004-06.html#author-semantic-enrichment>
etc; the two groups should investigate whether implementations of GRDDL
on mobile devices may contribute to these work item"

I think GRDDL is actually both more lightweight, requiring minimal or,
and if the namespace document contains the transfomraiton, no change
XHTML documents in order to retrieve semantics in the form of RDF from them.

However, HTML layout information is lost in translation to RDF ofcourse.
However, Ben Adida is working on a hGRDDL transform that transforms
microformats -> RDFa+XHTML that keeps the HTML in place [2]. Hopefully
there will be more progress on that front!

thanks,
harry

[1]http://www.w3.org/2006/07/grddl-charter.html
[2]http://www.w3.org/2006/07/SWD/wiki/hGRDDL_Example

Rhys Lewis wrote:

--
-harry

Harry Halpin, University of Edinburgh
http://www.ibiblio.org/hhalpin 6B522426

Re: GRDDL Going to Last Call: Relevant to DIWG

2007-02-08T06:44:11Z

Hello Harry,

Thanks very much for your note about GRDDL going to last call soon.

First impressions do confirm your assertion that GRDDL makes a major contribution to the item we had labelled 'semantic enrichment' in our current charter. Actually, we had concluded that the 'role' attribute and some likely extensions in XHTML Version 2 would probably meet our needs in this area. GRDDL looks to go beyond those capabilities.

I've taken the liberty of copying your note to our internal working group list (w3c-di-wg@...). That's where we normally carry out group discussions.

Perhaps you could indicate, on that list, whether the GRDDL working group is likely to request DIWG as one of the formal reviewers for the GRDDL documents?

Best wishes

Rhys Lewis, chair DIWG

GRDDL Going to Last Call: Relevant to DIWG

2007-02-06T18:21:59Z

I'm Harry Halpin, the Chair of the GRDDL WG [1] which links XML and
XHTML (including "microformats") to the Semantic Web in order to
facilitate the deployment of the Semantic Web.

In order to prevent a "surprise" Last Call, I'd like for your WG to
know that we are going to go, barring any final comments or problems,
to request move to Last Call on or shortly after Feb 15th for the
following three documents:

1) GRDDL Specification [2]
2) GRDDL Primer [3]
3) GRDDL Use Cases [4]

We believe this technology is related to the DIWG WG as a GRDDL can be
considered a possible solution for a Semantic Enrichment for Device
Independence work item, which states that:

"Discussion with various groups, including WAI PF and MMI, has indicated
that there is a likely need for representations that allow authors to
express additional semantics associated with particular
components of a user experience" [5]

In a nutshell, GRDDL allows the use of "link" element in a XHTML header
to express a transformation of the HTML to RDF, which could then in turn
provide needed semantic enrichment. This requires only a minor addition
to the link element or namespace document of the XML vocabulary/XHTML
profile URI and the authoring of a transformation, which can often be
done generically for many XHTML pages.

We believe this is compatible with:

"
it is possible that one outcome might include a small number of markup
extensions that represent usage patterns so common that they should be
supported directly. Another and possibly alternative outcome might be
ways to annotate such usage patterns to indicate additional semantics.
As with other work items, DIWG will focus on using existing W3C
techniques wherever appropriate and will propose extensions only where
necessary. Any extensions proposed will use the modularity of the
underlying W3C technology." [5]

We are interested in whether or not implementations of GRDDL on mobile
devices may contribute to these work item, and I hope it does.

thanks!

[1] http://www.w3.org/2001/sw/grddl-wg/
[2] http://www.w3.org/2004/01/rdxh/spec
[3] http://www.w3.org/2001/sw/grddl-wg/doc29/primer.html
[4] http://www.w3.org/2001/sw/grddl-wg/doc43/scenario-gallery
[5]
http://www.w3.org/2004/05/di-charter-2004-06.html#author-semantic-enrichment

--
-harry

Harry Halpin, University of Edinburgh
http://www.ibiblio.org/hhalpin 6B522426

MyMobileWeb receives the Eureka-CELTIC label

2006-11-17T03:55:31Z

Dear all,

I'm glad to announce that our open source project MyMobileWeb (http://www.morfeo-project.org/mymobileweb) has received the Eureka-CELTIC label. The project is leaded by Telefonica. Andrea Trasatti, our colleague in the DD and BP group, will participate in the project as an independent expert and consultant in the area of Device Description.

With respect to the W3C standardization effort we have to say that:

+ One of the tasks of the project, leaded by Andrea Trasatti, will be the implementation of the upconming DDR APIs, so MyMobileWeb will support the connection to any standard DDR.

+ Other of the tasks will be the implementation, targeted to mobile ui and mobile applications, of the upcoming standard for a DFAUI (Declarative Format for Application and User Interfaces) that the WAF WG could define.

------

The CELTIC Office, in a meeting that took place on November 9th, assigned the label "Eureka-CELTIC" to the MyMobileWeb project. Besides, due to its good rating and excellent comments received from experts, MyMobileWeb has been identified as a "CELTIC Flagship Project". This is a new success and assures the continuity of the project until at least 2010.

This label is a very important step towards the evolution of the project in an international basis, with four countries involved (Spain, France, Italy, and Germany). The commencement of the international project is scheduled on July 2007. In the meantime, MyMobileWeb is a "Tractor Project" which is being funded by the Spanish Ministry of Industry. The project consortium is the same that will participate in the CELTIC project representing Spain.

Best Regards

Mobile Web Best Practices - Free W3C Webinar, November 20 2006

2006-11-10T08:05:26Z

W3C presents: Mobile Web Best Practices

Need help with the challenges of mobile Web design? Join us for a
free W3C webinar where you will learn from an expert in mobile Web
design what to think about when mobilizing your Web content, what are
your options, and how you can benefit from the expertise collected
through the documents and tools provided by the W3C Mobile Web Best
Practices Working Group.

* What?

W3C Webinar on the Mobile Web Best Practices
* When?

Monday, November 20 2006
11am Paris - 10am UTC - 5am Boston
* Duration: 1h

If you are

* experienced with XHTML/CSS
* familiar with good markup techniques
* unsure about this "mobile Web thing"

this Webinar is for you!

Abstract

This presentation will briefly introduce the W3C Mobile Web
Initiative, before diving into the documents produced by the Mobile Web
Best Practices Working Group, with a specific focus on the Best
Practices themselves, the accompanying techniques, and the plans for the
future mobileOK mark. This will be illustrated with examples and
demonstrations of the Mobile Web Best Practices checker.

Invited Speaker: Dominique Hazael-Massieux

Dominique Hazael-Massieux has been working for the past 6 years at
W3C, where he gained a large expertise of the various technologies that
serve as a foundation of the Web as we know it, as well as the basis for
the Web as we don't know it yet. Since 2005, he is involved in the
Mobile Web Initiative, serving as the Team Contact for the Mobile Web
Best Practices, putting this knowledge in application in the context of
mobility. In addition to that, he's developing the Mobile Web Best
Practices checker, the first tool made available to help content
providers follow the Mobile Web Best Practices.

Attending the Webinar

If you are interested in attending, please fill in the application
form at http://www.w3.org/2006/10/Webcast

--
Stephane Boyera stephane@...
W3C +33 (0) 4 92 38 78 34
BP 93 fax: +33 (0) 4 92 38 78 22
F-06902 Sophia Antipolis Cedex,
France

Re:

2006-10-30T05:22:05Z

Rhys Lewis wrote:

> In a number of cases, we did not hear back from you after we responded
> to your comments. Given the time that has elapsed since our responses
> were sent, we have assumed that a lack of reply means that you have
> accepted our response.

Given the time that has elapsed, I'm afraid I'm no longer sure what I
said. However, looking at the latest drafts I think my original concerns
still stand. Perhaps the primer will clear this up, but this seems to be
an effort to create an embedded stylesheet language. It mixes content
with presentation in direct contravention to the goals of the Web, HTML,
and XML going back to their earliest days.

--
Elliotte Rusty Harold elharo@...
Java I/O 2nd Edition Just Published!
http://www.cafeaulait.org/books/javaio2/
http://www.amazon.com/exec/obidos/ISBN=0596527500/ref=nosim/cafeaulaitA/

Delivery Context: Interfaces (DCI) Accessing Static and Dynamic Properties Is a Candidate Recommendation

2006-10-20T07:00:56Z

Dear www-di,

I am pleased to announce that Delivery Context: Interfaces (DCI) Accessing
Static and Dynamic Properties is a W3C Candidate Recommendation. Available
at:

http://www.w3.org/TR/2006/CR-DPF-20061019/

Abstract

This document defines platform and language neutral programing
interfaces that provide Web applications access to a hierarchy
of dynamic properties representing device capabilities,
configurations, user preferences and environmental conditions.

Comments are welcome on this list.

Max Froumentin,
For the Device Independence Working Group.

RE: DISelect and the media attribute

2006-10-20T02:49:09Z

Hi Jose,

The reasoning was that XSLT already defined {} as the syntax wrapper for AVT and we simply adopted it.

This is one of the things that we might revisit in a new revision of DISelect that used different expression languages. For the current spec, it's completely consistent, but I agree that for different expression languages, the tradeoffs are different.

Best wishes
Rhys

-----Original Message-----
From: jmcf@... [mailto:jmcf@...]
Sent: 20 October 2006 09:06
To: Rhys.Lewis@...
Cc: www-di@...
Subject: Re: DISelect and the media attribute

Thanks Rhys, for your quick response.

Taking into account that different expression languages can be together
in authoring unit, wouldn't it be better to define a more specific
syntax for the expressions?

For example JSP 2.0 E.L. expressions are ${a.b > 5}.

DISelect expressions could be

diselect{<expression>}

Or, as DISelect are XPATH expressions, wouldn't it be better that the
expressions were as

xpath{<DISelectExpression>}

Defining the expressions with a prefix will make the specification more
extensible and could even incoporate in a future other E.L.s

What do you think?

Rhys Lewis escribió:

> Hi Jose,
>
> It is specifically allowed in the full profile of DISelect. Section 7 covers the use of AVTs to set host language attributes. So if your example were, for example, from DIAL, it would be fine. However, you do need the curly brackets to satisfy the AVT syntax, so I think you example would actually need to be:
>
> <style type="text/css" src="mystyle.css" media="{DISelect expression 1}" />
> <style type="text/css" src="mystyle2.css" media="{DISelect expression 2}" />
> <style type="text/css" src="mystyle4.css" media="{DISelect expression 4}" />
>
> You could of course also code it as
>
> <style type="text/css" src="mystyle.css" expr="DISelect expression 1" />
> <style type="text/css" src="mystyle2.css" expr="DISelect expression 2" />
> <style type="text/css" src="mystyle4.css" expr="DISelect expression 4" />
>
> where the expressions evaluate to true or false rather than to some value of media. The <select> element can also be used as you showed.
>
> That's the trouble with flexibility, there are often several ways of achieving things!
>
> Best wishes
>
> Rhys
>
> -----Original Message-----
> From: www-di-request@... [mailto:www-di-request@...] On Behalf Of José Manuel Cantera Fonseca
> Sent: 20 October 2006 08:07
> To: www-di@...
> Subject: DISelect and the media attribute
>
>
> Hi,
>
> Is this is allowed?
>
> <style type="text/css" src="mystyle.css" media="DISelect expression 1" />
> <style type="text/css" src="mystyle2.css" media="DISelect expression 2" />
> <style type="text/css" src="mystyle4.css" media="DISelect expression 4" />
>
> Or is it a better practice to put:
>
> <sel:select>
> <sel:when expr="">
> <style type="text/css" src="mystyle.css" />
> </sel:when>
> <sel:when expr="">
> <style type="text/css" src="mystyle2.css" />
> </sel:when>
> <sel:otherwise>
> <style type="text/css" src="mystyle4.css" />
> </sel:otherwise>
> </sel:select>
>
> ?
>
> Thanks for your responses
>
>
>
>
>

Re: DISelect and the media attribute

2006-10-20T02:06:28Z

Thanks Rhys, for your quick response.

Taking into account that different expression languages can be together
in authoring unit, wouldn't it be better to define a more specific
syntax for the expressions?

For example JSP 2.0 E.L. expressions are ${a.b > 5}.

DISelect expressions could be

diselect{<expression>}

Or, as DISelect are XPATH expressions, wouldn't it be better that the
expressions were as

xpath{<DISelectExpression>}

Defining the expressions with a prefix will make the specification more
extensible and could even incoporate in a future other E.L.s

What do you think?

Rhys Lewis escribió:

RE: DISelect and the media attribute

2006-10-20T01:47:21Z

Hi Jose,

It is specifically allowed in the full profile of DISelect. Section 7 covers the use of AVTs to set host language attributes. So if your example were, for example, from DIAL, it would be fine. However, you do need the curly brackets to satisfy the AVT syntax, so I think you example would actually need to be:

<style type="text/css" src="mystyle.css" media="{DISelect expression 1}" />
<style type="text/css" src="mystyle2.css" media="{DISelect expression 2}" />
<style type="text/css" src="mystyle4.css" media="{DISelect expression 4}" />

You could of course also code it as

<style type="text/css" src="mystyle.css" expr="DISelect expression 1" />
<style type="text/css" src="mystyle2.css" expr="DISelect expression 2" />
<style type="text/css" src="mystyle4.css" expr="DISelect expression 4" />

where the expressions evaluate to true or false rather than to some value of media. The <select> element can also be used as you showed.

That's the trouble with flexibility, there are often several ways of achieving things!

Best wishes

Rhys

-----Original Message-----
From: www-di-request@... [mailto:www-di-request@...] On Behalf Of José Manuel Cantera Fonseca
Sent: 20 October 2006 08:07
To: www-di@...
Subject: DISelect and the media attribute

Hi,

Is this is allowed?

<style type="text/css" src="mystyle.css" media="DISelect expression 1" />
<style type="text/css" src="mystyle2.css" media="DISelect expression 2" />
<style type="text/css" src="mystyle4.css" media="DISelect expression 4" />

Or is it a better practice to put:

<sel:select>
<sel:when expr="">
<style type="text/css" src="mystyle.css" />
</sel:when>
<sel:when expr="">
<style type="text/css" src="mystyle2.css" />
</sel:when>
<sel:otherwise>
<style type="text/css" src="mystyle4.css" />
</sel:otherwise>
</sel:select>

?

Thanks for your responses

DISelect and the media attribute

2006-10-20T01:06:40Z

Hi,

Is this is allowed?

<style type="text/css" src="mystyle.css" media="DISelect expression 1" />
<style type="text/css" src="mystyle2.css" media="DISelect expression 2" />
<style type="text/css" src="mystyle4.css" media="DISelect expression 4" />

Or is it a better practice to put:

<sel:select>
<sel:when expr="">
<style type="text/css" src="mystyle.css" />
</sel:when>
<sel:when expr="">
<style type="text/css" src="mystyle2.css" />
</sel:when>
<sel:otherwise>
<style type="text/css" src="mystyle4.css" />
</sel:otherwise>
</sel:select>

?

Thanks for your responses

RE: DISelect when and switch/case in XFORMS

2006-10-19T05:47:54Z

Hello Jose,

This is a good point.

The group was a little uncomfortable about this when we designed the markup. The issue for us was that it was important for DISelect to be useable in markup languages that don't include XForms. As I may have mentioned earlier, the Timed Text group was looking at our specification at the time. So, we needed DISelect itself not to require other markup that might not be available in other profiles. Hence we ended up needing to specify the if and select markup and to rely on the namespace distinguishing between them.

Best wishes
Rhys

-----Original Message-----
From: www-di-request@... [mailto:www-di-request@...] On Behalf Of José Manuel Cantera Fonseca
Sent: 19 October 2006 10:12
To: www-di@...
Subject: DISelect when and switch/case in XFORMS

Dear all,

I'm here one more time :-) with some doubts. Conceptually, I see the
DISelect <when> very similar to the switch/case XFORMS structure. Why it
as decided not to extend the switch/case already present in XFORMS?

Thanks and Best Regards

RE: Reuse issue in DISelect

2006-10-19T05:24:42Z

Hello Jose,

First let me say that you are absolutely correct, and that it is important to be able to reuse DISelect in very flexible ways. I'll be covering this in the next revision of the DISelect Primer, which is in progress right now. I'm currently working on some examples.

Rotan has already pointed out one mechanism for reuse in a separate answer.

It is possible to use mechanisms based on embedding, as you point out. However, since W3C already has specifications that deal with this (XHTML V2, XInclude etc.), rather than invent a new mechanism, DISelect relies on these other mechanisms. I'll illustrate some in the primer. The idea is to write the DISelect in a separate document and simply to embed it where needed.

Another mechanism, that can reduce the need to rewrite expressions multiple times, relates to the ability to store the value of a DISelect expression in a variable. If the same test needs to be used multiple times within one document, the value of the appropriate expression can be computed once and saved in a DISelect variable. Subsequently, that variable can be used in tests in place of the expression, thus making the tests simpler. I'll illustrate that too in the primer.

On the question of device groups, this is a well known and well understood mechanism for dealing with diversity that is used by many operators and commercial implementations. Unfortunately, as yet there is insufficient basis in the current standards for us to formalise a mechanism for doing this in a standard way. It might be that the Device Descriptions working group might specify a standard property for this kind of device group. If that is the case, we could, in future, add an appropriate XPath function to the minimum set for DISelect to cover this.

In the meantime, and to take account of situations like this, where properties are useful but not yet standardised, we included in DISelect the ability to support extension XPath functions as long as they are outside the reserved DISelect namespace. Commercial implementations provide extensive access to additional properties using this kind of facility. Typically, this does include the ability to determine the group to which a device belongs. In at least one implementation, it is possible to add arbitrary new properties to be associated with individual devices or sets of devices.

Best wishes

Rhys Lewis

-----Original Message-----
From: www-di-request@... [mailto:www-di-request@...] On Behalf Of José Manuel Cantera Fonseca
Sent: 19 October 2006 10:27
To: www-di@...
Subject: Reuse issue in DISelect

Dear all,

Another thread for another question. I'm envisaging the following issue
with DISelect and has to do with the reuse of conditions.

Imagine I'm a developer and bacause of the requirements of my
application I have to put the same selection conditions in several
authoring units. During the lifetime of the project I realize that those
conditions, that are spread over all the authoring units, are not
accurate. So, to fix it, I will have to edit all the authoring units and
change in all places my conditions.

Does DISelect have condition-reuse mechanisms that allow a developer to
avoid this issue?

With respect to those conditions that only has to do with the delivery
context subset composed by device properties (those found in the DDR),
Wouldn't it better that the developer could define (externally) groups
of devices, by means of logical conditions of belonging, and reference
those groups logically in the select expressions within the authoring units?

If due to some reason the conditions change I will only have to change
them in one place, outside the authoring units, that probably will be
developed by designers with no deed knowledge of device specific
technologies.

Thanks and best regards

RE: Reuse issue in DISelect

2006-10-19T04:45:35Z

You can place your conditional calculations in a custom XPath function and merely return Booleans to the DISelect page. If your calculations need to change, just update the XPath function implementation, and all your pages will now be using the new calculations.

Similarly, things like group membership can be dealt with externally.

The point, however, from a standardisation position is that external custom methods will reduce the portability of both the pages and the skills of the developer. So, if/when new properties or concepts (e.g. grouping) are proposed within a standardisation process, this should include the definition of common methods/functions and their binding in expressions such as those used in DISelect.

But of course you already know that. I'm just noting it here for the benefit of others who read this list. The DDWG will hopefully be working on a more comprehensive set of properties/methods and I expect these will be considered by DIWG, and we will see these advances coupled to DISelect in some way.

---Rotan.

-----Original Message-----
From: www-di-request@... [mailto:www-di-request@...] On Behalf Of José Manuel Cantera Fonseca
Sent: 19 October 2006 10:27
To: www-di@...
Subject: Reuse issue in DISelect

Dear all,

Another thread for another question. I'm envisaging the following issue with DISelect and has to do with the reuse of conditions.

Imagine I'm a developer and bacause of the requirements of my application I have to put the same selection conditions in several authoring units. During the lifetime of the project I realize that those conditions, that are spread over all the authoring units, are not accurate. So, to fix it, I will have to edit all the authoring units and change in all places my conditions.

Does DISelect have condition-reuse mechanisms that allow a developer to avoid this issue?

With respect to those conditions that only has to do with the delivery context subset composed by device properties (those found in the DDR), Wouldn't it better that the developer could define (externally) groups of devices, by means of logical conditions of belonging, and reference those groups logically in the select expressions within the authoring units?

If due to some reason the conditions change I will only have to change them in one place, outside the authoring units, that probably will be developed by designers with no deed knowledge of device specific technologies.

Thanks and best regards

Reuse issue in DISelect

2006-10-19T03:27:01Z

Dear all,

Another thread for another question. I'm envisaging the following issue
with DISelect and has to do with the reuse of conditions.

Imagine I'm a developer and bacause of the requirements of my
application I have to put the same selection conditions in several
authoring units. During the lifetime of the project I realize that those
conditions, that are spread over all the authoring units, are not
accurate. So, to fix it, I will have to edit all the authoring units and
change in all places my conditions.

Does DISelect have condition-reuse mechanisms that allow a developer to
avoid this issue?

With respect to those conditions that only has to do with the delivery
context subset composed by device properties (those found in the DDR),
Wouldn't it better that the developer could define (externally) groups
of devices, by means of logical conditions of belonging, and reference
those groups logically in the select expressions within the authoring units?

If due to some reason the conditions change I will only have to change
them in one place, outside the authoring units, that probably will be
developed by designers with no deed knowledge of device specific
technologies.

Thanks and best regards

DISelect when and switch/case in XFORMS

2006-10-19T03:12:20Z

Dear all,

I'm here one more time :-) with some doubts. Conceptually, I see the
DISelect <when> very similar to the switch/case XFORMS structure. Why it
as decided not to extend the switch/case already present in XFORMS?

Thanks and Best Regards

Re: RE: Content selection expressions

2006-10-18T13:49:47Z

Yes I was thinking in using the E.L syntax. Actually we use it in
MyMobileWeb for specifying declarative data binding and some dynamic
aspects of the "declaratively specified" mobile presentation layer.

Thanks one more time

Best Regards

----
José Manuel Cantera Fonseca
Telefónica I+D

----- Mensaje original -----
De: Rhys Lewis <Rhys.Lewis@...>
Fecha: Miércoles, Octubre 18, 2006 6:22 pm
Asunto: RE: Content selection expressions
Para: "José Manuel Cantera Fonseca" <jmcf@...>, "www-di@..."
<www-di@...>

>
> Hello Jose,
>
> Interestingly this is not the first time that DI has been asked
> about the possibility of using DISelect with other expression
> languages. I have some sympathy for this, given how awkward XPath
> expressions look inside XML documents.
>
> Personally, I have no problem with enabling other expression
> languages for DISelect. The base reason for picking XPath initially
> was because it is what is used elsewhere in DIAL, in particularly
> in XForms. Hence, it makes perfect sense for that to be the
> expression language for DISelect used in DIAL. This is not
> necessarily the case in other potential uses of DISelect.
>
> Right now, there is no particular group within DI pressing for
> additional expression languages, so its not likely to happen
> spontaneously. However, if W3C member companies wish to join DIWG,
> or its follow on after rechartering, to carry that work forward, I
> think that it could be easily accommodated in a future revision of
> DISelect.
> By the way, I assume by JSP 2.0 you mean using those expressions in-
> line rather than embedding DISelect in a JSP or servlet. In that
> latter case you can, of course, already do this. I know I have!
>
> Best wishes
> Rhys
>
> -----Original Message-----
> From: www-di-request@... [mailto:www-di-request@...] On
> Behalf Of José Manuel Cantera Fonseca
> Sent: 18 October 2006 15:59
> To: www-di@...
> Subject: Content selection expressions
>
>
> Dear all,
>
> Does the current version of the content selection standard allow to
> include expressions in other languages than XPATH? I'm thinking in
> expressions expressed in Expression Language (JSP 2.0) for example.
>
> Thanks and Best Regards
>
>
>
>

[jmcf.vcf]

begin:vcard version:2.1 end:vcard

Re: RE: XPATH access functions

2006-10-18T13:46:08Z

ok, thanks one more time for your quick responses. I agree with the DDWG
thing

Best Regards

----
José Manuel Cantera Fonseca
Telefónica I+D

----- Mensaje original -----
De: Rotan Hanrahan <Rotan.Hanrahan@...>
Fecha: Miércoles, Octubre 18, 2006 5:47 pm
Asunto: RE: XPATH access functions
Para: José Manuel Cantera Fonseca <jmcf@...>, www-di@...

> The original functions were based on those mentioned in CSS Media
> Queries, specifically to provide a migration path from CSSMQ to the
> more flexible DISelect. They even borrow the CSSMQ names. We call
> these the starter set. But, of course, the community is encouraged
> to consider extending them to access additional properties, not
> just those described in DCI.
>
> One could even envisage a generic property accessor (though a lot
> more thinking would need to go into that idea before we could
> recommend it).
>
> The set of properties to be proposed as an initial vocabulary in
> the DDWG's DDR would be a good start, when the time comes.
>
> ---Rotan.
>
> -----Original Message-----
> From: www-di-request@... [mailto:www-di-request@...] On
> Behalf Of José Manuel Cantera Fonseca
> Sent: 18 October 2006 15:57
> To: www-di@...
> Subject: XPATH access functions
>
>
> Dear all,
>
> My understanding of the access functions is that they are only
> wrappers to the delivery context properties that in a more generic
> way can be accesed using the DCI API.
>
> Is that vision correct?
>
> Thanks and Best Regards
>
>

[jmcf.vcf]

begin:vcard version:2.1 end:vcard

RE: Content selection expressions

2006-10-18T10:22:39Z

Hello Jose,

Interestingly this is not the first time that DI has been asked about the possibility of using DISelect with other expression languages. I have some sympathy for this, given how awkward XPath expressions look inside XML documents.

Personally, I have no problem with enabling other expression languages for DISelect. The base reason for picking XPath initially was because it is what is used elsewhere in DIAL, in particularly in XForms. Hence, it makes perfect sense for that to be the expression language for DISelect used in DIAL. This is not necessarily the case in other potential uses of DISelect.

Right now, there is no particular group within DI pressing for additional expression languages, so its not likely to happen spontaneously. However, if W3C member companies wish to join DIWG, or its follow on after rechartering, to carry that work forward, I think that it could be easily accommodated in a future revision of DISelect.

By the way, I assume by JSP 2.0 you mean using those expressions in-line rather than embedding DISelect in a JSP or servlet. In that latter case you can, of course, already do this. I know I have!

Best wishes
Rhys

-----Original Message-----
From: www-di-request@... [mailto:www-di-request@...] On Behalf Of José Manuel Cantera Fonseca
Sent: 18 October 2006 15:59
To: www-di@...
Subject: Content selection expressions

Dear all,

Does the current version of the content selection standard allow to
include expressions in other languages than XPATH? I'm thinking in
expressions expressed in Expression Language (JSP 2.0) for example.

Thanks and Best Regards

RE: Innovative use of DIAL for IT management

2006-10-18T09:54:08Z

Hello Johannes,

I think that there is a distinction to make here between DISelect processing, within DIAL, and subsequent adaptation that might result from processing the resulting DIAL.

The DISelect module within DIAL is designed to help content authors control expression of content within their markup. In fact, DISelect can be used in line or externally to DIAL. I'll be covering this in a forthcoming revision of the DISelect Primer. Where DISelect is used in an XML document, then its input and output do need to be XML compliant. Where DISelect is used in line within DIAL it controls expression of various parts of the DIAL document. The result is a modified DIAL document where the DISelect statements have been replaced by the appropriately selected content.

Typically, the resulting DIAL is then subsequently processed by further adaptation that can result in it being transformed into any kind of markup, or indeed non-markup, data stream. Current implementations of DIAL do exactly this and can generate any of dozens of types of output stream.

So in terms of your question, the final transformation is still within the adaptation step but is something that applies after DISelect processing modifies the DIAL.

I hope that clarifies the situation.

Best wishes
Rhys

-----Original Message-----
From: www-di-request@... [mailto:www-di-request@...] On Behalf Of Johannes Koch
Sent: 18 October 2006 16:11
To: www-di@...
Subject: Re: Innovative use of DIAL for IT management

Rotan Hanrahan schrieb:
> - Is a document compliant to DIAL if it is XML format?
>
> No. The fragments being generated by the adaptors could, as suggested,
> be valid subsets of a DIAL document. As DIAL is itself an XML language,
> the adaptors must also be producing XML.

Is a DIAL adaptor really required to only produce XML? What about
non-XML formats (e.g. HTML)? Or is this transformation considered to be
a process following the adaptation?
--
Johannes Koch
In te domine speravi; non confundar in aeternum.
(Te Deum, 4th cent.)

RE: XPATH access functions

2006-10-18T09:45:16Z

The original functions were based on those mentioned in CSS Media Queries, specifically to provide a migration path from CSSMQ to the more flexible DISelect. They even borrow the CSSMQ names. We call these the starter set. But, of course, the community is encouraged to consider extending them to access additional properties, not just those described in DCI.

One could even envisage a generic property accessor (though a lot more thinking would need to go into that idea before we could recommend it).

The set of properties to be proposed as an initial vocabulary in the DDWG's DDR would be a good start, when the time comes.

---Rotan.

-----Original Message-----
From: www-di-request@... [mailto:www-di-request@...] On Behalf Of José Manuel Cantera Fonseca
Sent: 18 October 2006 15:57
To: www-di@...
Subject: XPATH access functions

Dear all,

My understanding of the access functions is that they are only wrappers to the delivery context properties that in a more generic way can be accesed using the DCI API.

Is that vision correct?

Thanks and Best Regards

RE: Content selection expressions

2006-10-18T09:41:08Z

DISelect only specifies XPath. Keeping the technology within the scope of existing W3C technologies. Binding to EL is certainly a possibility. MobileAware has its own expression binding for a thematically similar technology, so we know from practical experience this is possible. From a high-level point of view, what is important is the ability to use selection within the content, so that the selection expressions can capture in some way the presentation requirements of the author. It is certainly within the philosophy to consider similar approaches in other domains. But mixing them might be a struggle. A DISelect processor that accepted EL instead of XPath would have additional features (such as bean access) and limitations (such as DOM access).

In terms of DISelect as specified, XPath is the language you use, and you can extend it to provide access to other contextual data if needed. For example, when DDWG eventually produces a vocabulary, someone could create an XPath binding to those properties so that DISelect would be able to use DDR data. (Yes, I think someone will implement that...)

I'm not tending one way or the other. Let's just see what evolves.

---Rotan.

-----Original Message-----
From: www-di-request@... [mailto:www-di-request@...] On Behalf Of José Manuel Cantera Fonseca
Sent: 18 October 2006 15:59
To: www-di@...
Subject: Content selection expressions

Dear all,

Does the current version of the content selection standard allow to include expressions in other languages than XPATH? I'm thinking in expressions expressed in Expression Language (JSP 2.0) for example.

Thanks and Best Regards

RE: Innovative use of DIAL for IT management

2006-10-18T09:31:11Z

You are confusing the term "adaptor". Re-reading the article may
clarify.

The adaptors described in the article adapt a proprietary format (e.g.
comma separated values) into something that is placed within a DIAL
document. As a DIAL document is an XML document, it follows that the
output of the adaptors (as described in the article) must be producing
XML fragments. Specifically, the article describes the production of
XHTML 2 <object> elements.

Completely separate, and *not* described in the article, is the
subsequent adaptation of the complete DIAL document (within which the
previously mentioned XML fragments are contained). This is the document
transformation process. This is *not* described in the cited article.

The result of transforming DIAL can be absolutely anything. HTML, WML,
iMode, music, oil paintings, Braille, SVG, ASCII text, RSS etc etc etc.
None of this is described in the cited article.

The article should be considered a rather unusual and unorthodox use for
DIAL, and is certainly not a use case that was anticipated by DIWG. We
do not discount it, but we would not suggest using it as an example of
how DIAL is intended to be used. By focussing on the article, we may be
causing unnecessary distraction from the true intent of DIAL. I suggest
that a reading of the DIAL Primer [1] would be better.

---Rotan.

[1] http://www.w3.org/TR/dial-primer/

-----Original Message-----
From: www-di-request@... [mailto:www-di-request@...] On Behalf Of
Johannes Koch
Sent: 18 October 2006 16:11
To: www-di@...
Subject: Re: Innovative use of DIAL for IT management

Rotan Hanrahan schrieb:
> - Is a document compliant to DIAL if it is XML format?
>
> No. The fragments being generated by the adaptors could, as suggested,

> be valid subsets of a DIAL document. As DIAL is itself an XML
> language, the adaptors must also be producing XML.

Is a DIAL adaptor really required to only produce XML? What about
non-XML formats (e.g. HTML)? Or is this transformation considered to be
a process following the adaptation?
--
Johannes Koch
In te domine speravi; non confundar in aeternum.
(Te Deum, 4th cent.)

Re: Innovative use of DIAL for IT management

2006-10-18T09:11:29Z

Rotan Hanrahan schrieb:
> - Is a document compliant to DIAL if it is XML format?
>
> No. The fragments being generated by the adaptors could, as suggested,
> be valid subsets of a DIAL document. As DIAL is itself an XML language,
> the adaptors must also be producing XML.

Is a DIAL adaptor really required to only produce XML? What about
non-XML formats (e.g. HTML)? Or is this transformation considered to be
a process following the adaptation?
--
Johannes Koch
In te domine speravi; non confundar in aeternum.
(Te Deum, 4th cent.)

RE: Innovative use of DIAL for IT management

2006-10-18T09:04:18Z

Purely my own thoughts on this...

— How is interoperability provided concerning the terms used within the adapter? For example, “Device” may have a different meaning for the network devices than for digital camera or projector.

The article does not address the issue of vocabularies/ontologies for device concepts. Within specific management domains this may be standardised, such as prescribed branches of the SNMP MIB. But the article does not elaborate on the issue. The discussion on this issue is best addressed to the author (who appears to have a particular expertise in the area of network management metadata).

— Is a document compliant to DIAL if it is XML format?

No. The fragments being generated by the adaptors could, as suggested, be valid subsets of a DIAL document. As DIAL is itself an XML language, the adaptors must also be producing XML. In particular, the author suggests the representation of management data by transforming to XML and from there to an XHTML 2 object. Nothing is said about how such objects should be adapted for rendering purposes. DIAL merely provides a presentation format that is adaptable, specifically by providing the ability to select/remove subsets of a DIAL document based on contextual information. But suppose you decide to select an <object>, then what? Nothing in DIAL says how individual elements or structures should be adapted to the target presentation. It is up to individual adaptation technologies to decide what to do. DIAL merely provides a common authoring language to support adaptation, it does not provide the specifics of the adaptation process. (I am excluding here the facilities provided by DISelect, which forms part of DIAL.) In essence, the article is describing how the management data could be captured and represented in DIAL, but does not explore how such DIAL instances (containing extremely domain-specific structures) would be transformed for presentation on a PC browser. Putting the data into <object> elements does not answer the question of rendering.

— Following this approach, it is required to have a Java program for each proprietary format of each device, right or have I missed something?

Yes. That is my understanding too. Though I suspect that since there are only a handful of generally deployed network-based resource management technologies, re-use or inheritance of code is probably viable.

---Rotan

From: www-di-request@... [mailto:www-di-request@...] On Behalf Of Christian Timmerer (ITEC)
Sent: 18 October 2006 15:29
To: Rhys.Lewis@...; 'Smith, Kevin, VF-Group'; www-di@...
Cc: christian.timmerer@...
Subject: RE: Innovative use of DIAL for IT management

Dear Rhys,

thanks for your reply and clarification. However, I’m sure that members of the DIWG read this article and could probably share their view on this thread.

Thanks.

Best regards,

-Christian

:--

:- Dipl.-Ing. Dr. Christian Timmerer

:- Department of Information Technology (ITEC)

:- Klagenfurt University, Austria

:- http://research.timmerer.com

:----------------------------------------------------------

>> Visit the IT Campus Carinthia

>> http://www.it-campus.at

From: www-di-request@... [mailto:www-di-request@...] On Behalf Of Rhys Lewis
Sent: Tuesday, October 17, 2006 2:17 PM
To: Christian Timmerer (ITEC); Smith, Kevin, VF-Group; www-di@...
Subject: RE: Innovative use of DIAL for IT management

Hi Christian,

Kevin didn’t actually write the article, he merely pointed us to it. I think you probably need to ask Stephen B. Morris, the author. Unfortunately, Stephen is not a member of DIWG, so can’t be reached via this mailing list.

Best wishes

Rhys Lewis, chair DIWG

From: www-di-request@... [mailto:www-di-request@...] On Behalf Of Christian Timmerer (ITEC)
Sent: 17 October 2006 10:54
To: 'Smith, Kevin, VF-Group'; www-di@...
Cc: christian.timmerer@...
Subject: RE: Innovative use of DIAL for IT management

Dear Kevin,

thanks for this article which is very interesting. The article describes how information (in a proprietary format like key-value pairs or comma-separated values) from different devices is transformed into XML format using a Java program(s). The claim is – as I understood it – that this XML document is compliant to DIAL.

I have some questions/comments:

— How is interoperability provided concerning the terms used within the adapter? For example, “Device” may have a different meaning for the network devices than for digital camera or projector.

— Is a document compliant to DIAL if it is XML format?

— Following this approach, it is required to have a Java program for each proprietary format of each device, right or have I missed something?

To be honest, I’m missing the last step, i.e., between the “Adapter” and the “Web browser on the PC”.

Thank you.

Best regards,

-Christian

:--

:- Dipl.-Ing. Dr. Christian Timmerer

:- Department of Information Technology (ITEC)

:- Klagenfurt University, Austria

:- http://research.timmerer.com

:----------------------------------------------------------

>> Visit the IT Campus Carinthia

>> http://www.it-campus.at

From: www-di-request@... [mailto:www-di-request@...] On Behalf Of Smith, Kevin, VF-Group
Sent: Wednesday, October 11, 2006 2:54 PM
To: www-di@...
Subject: Innovative use of DIAL for IT management

Stephen B Morris has posted an innovative use for DIAL at IBM developerworks: http://www-128.ibm.com/developerworks/library/x-dial/

He posits "DIAL provides what might become a standard data platform for IT management.", which is a very exciting, if unexpected, application!

Cheers

Kevin

Content selection expressions

2006-10-18T08:59:10Z

Dear all,

Does the current version of the content selection standard allow to
include expressions in other languages than XPATH? I'm thinking in
expressions expressed in Expression Language (JSP 2.0) for example.

Thanks and Best Regards

XPATH access functions

2006-10-18T08:56:40Z

Dear all,

My understanding of the access functions is that they are only wrappers
to the delivery context properties that in a more generic way can be
accesed using the DCI API.

Is that vision correct?

Thanks and Best Regards

RE: Innovative use of DIAL for IT management

2006-10-18T08:55:02Z

Hi Christian,

I can help with the last two questions:

- Is a document DIAL compliant if it is XML compliant?

No, it's the other way around - a document is XML compliant if it is DIAL compliant (or in the XML terminology, 'valid DIAL is well-formed XML'). Note that DIAL is one of many dialects of XML. It specifies a set of XML elements and attributes, and their structure and types, in the DIAL specification.

- it is required to have a Java program for each proprietary format of each device

You would need a way of parsing each data format, each of which would need to be represented in Java (either as a condition, method, class or package)

For the other questions it's best to ask Mr Morris at http://www-128.ibm.com/developerworks/library/x-dial/

Hope that helps,

Kevin

From: Christian Timmerer (ITEC) [mailto:christian.timmerer@...]
Sent: 18 October 2006 15:29
To: Rhys.Lewis@...; Smith, Kevin, VF-Group; www-di@...
Cc: christian.timmerer@...
Subject: RE: Innovative use of DIAL for IT management

Dear Rhys,

thanks for your reply and clarification. However, I’m sure that members of the DIWG read this article and could probably share their view on this thread.

Thanks.

Best regards,

-Christian

:--

:- Dipl.-Ing. Dr. Christian Timmerer

:- Department of Information Technology (ITEC)

:- Klagenfurt University, Austria

:- http://research.timmerer.com

:----------------------------------------------------------

>> Visit the IT Campus Carinthia

>> http://www.it-campus.at

From: www-di-request@... [mailto:www-di-request@...] On Behalf Of Rhys Lewis
Sent: Tuesday, October 17, 2006 2:17 PM
To: Christian Timmerer (ITEC); Smith, Kevin, VF-Group; www-di@...
Subject: RE: Innovative use of DIAL for IT management

Hi Christian,

Kevin didn’t actually write the article, he merely pointed us to it. I think you probably need to ask Stephen B. Morris, the author. Unfortunately, Stephen is not a member of DIWG, so can’t be reached via this mailing list.

Best wishes

Rhys Lewis, chair DIWG

From: www-di-request@... [mailto:www-di-request@...] On Behalf Of Christian Timmerer (ITEC)
Sent: 17 October 2006 10:54
To: 'Smith, Kevin, VF-Group'; www-di@...
Cc: christian.timmerer@...
Subject: RE: Innovative use of DIAL for IT management

Dear Kevin,

thanks for this article which is very interesting. The article describes how information (in a proprietary format like key-value pairs or comma-separated values) from different devices is transformed into XML format using a Java program(s). The claim is – as I understood it – that this XML document is compliant to DIAL.

I have some questions/comments:

—     How is interoperability provided concerning the terms used within the adapter? For example, “Device” may have a different meaning for the network devices than for digital camera or projector.

—     Is a document compliant to DIAL if it is XML format?

—     Following this approach, it is required to have a Java program for each proprietary format of each device, right or have I missed something?

To be honest, I’m missing the last step, i.e., between the “Adapter” and the “Web browser on the PC”.

Thank you.

Best regards,

-Christian

:--

:- Dipl.-Ing. Dr. Christian Timmerer

:- Department of Information Technology (ITEC)

:- Klagenfurt University, Austria

:- http://research.timmerer.com

:----------------------------------------------------------

>> Visit the IT Campus Carinthia

>> http://www.it-campus.at

From: www-di-request@... [mailto:www-di-request@...] On Behalf Of Smith, Kevin, VF-Group
Sent: Wednesday, October 11, 2006 2:54 PM
To: www-di@...
Subject: Innovative use of DIAL for IT management

          Stephen B Morris has posted an innovative use for DIAL at IBM developerworks: http://www-128.ibm.com/developerworks/library/x-dial/

He posits "DIAL provides what might become a standard data platform for IT management.", which is a very exciting, if unexpected, application!

Cheers

Kevin

RE: Innovative use of DIAL for IT management

2006-10-18T08:29:28Z

Dear Rhys,

thanks for your reply and clarification. However, I’m sure that members of the DIWG read this article and could probably share their view on this thread.

Thanks.

Best regards,

-Christian

:--

:- Dipl.-Ing. Dr. Christian Timmerer

:- Department of Information Technology (ITEC)

:- Klagenfurt University, Austria

:- http://research.timmerer.com

:----------------------------------------------------------

>> Visit the IT Campus Carinthia

>> http://www.it-campus.at

Hi Christian,

Best wishes

Rhys Lewis, chair DIWG

Dear Kevin,

I have some questions/comments:

— How is interoperability provided concerning the terms used within the adapter? For example, “Device” may have a different meaning for the network devices than for digital camera or projector.

— Is a document compliant to DIAL if it is XML format?

— Following this approach, it is required to have a Java program for each proprietary format of each device, right or have I missed something?

To be honest, I’m missing the last step, i.e., between the “Adapter” and the “Web browser on the PC”.

Thank you.

Best regards,

-Christian

:--

:- Dipl.-Ing. Dr. Christian Timmerer

:- Department of Information Technology (ITEC)

:- Klagenfurt University, Austria

:- http://research.timmerer.com

:----------------------------------------------------------

>> Visit the IT Campus Carinthia

>> http://www.it-campus.at

Stephen B Morris has posted an innovative use for DIAL at IBM developerworks: http://www-128.ibm.com/developerworks/library/x-dial/

He posits "DIAL provides what might become a standard data platform for IT management.", which is a very exciting, if unexpected, application!

Cheers

Kevin

RE: Innovative use of DIAL for IT management

2006-10-17T06:16:42Z

Hi Christian,

Best wishes

Rhys Lewis, chair DIWG

Dear Kevin,

I have some questions/comments:

— How is interoperability provided concerning the terms used within the adapter? For example, “Device” may have a different meaning for the network devices than for digital camera or projector.

— Is a document compliant to DIAL if it is XML format?

— Following this approach, it is required to have a Java program for each proprietary format of each device, right or have I missed something?

To be honest, I’m missing the last step, i.e., between the “Adapter” and the “Web browser on the PC”.

Thank you.

Best regards,

-Christian

:--

:- Dipl.-Ing. Dr. Christian Timmerer

:- Department of Information Technology (ITEC)

:- Klagenfurt University, Austria

:- http://research.timmerer.com

:----------------------------------------------------------

>> Visit the IT Campus Carinthia

>> http://www.it-campus.at

Stephen B Morris has posted an innovative use for DIAL at IBM developerworks: http://www-128.ibm.com/developerworks/library/x-dial/

He posits "DIAL provides what might become a standard data platform for IT management.", which is a very exciting, if unexpected, application!

Cheers

Kevin