FW: [ARCH] two minor issues in current MMI-Arch spec

Jakob,
  As part of W3C process, we need to know if you accept our response to the issues you raised here.  Please let us know if you do.  If we do not hear from you within two weeks, we will assume that you accept our response.

Thankyou,
Jim Barnett

-----Original Message-----
From: Jim Barnett 
Sent: Monday, May 16, 2011 9:51 AM
To: Jakob Sachse; www-multimodal@w3.org
Subject: RE: [ARCH] two minor issues in current MMI-Arch spec

Jacob,
  We accept these comments and will update the specification accordingly.

- Jim Barnett

-----Original Message-----
From: www-multimodal-request@w3.org [mailto:www-multimodal-request@w3.org] On Behalf Of Jakob Sachse
Sent: Sunday, March 27, 2011 9:40 AM
To: www-multimodal@w3.org
Subject: [ARCH] two minor issues in current MMI-Arch spec

Hallo,

I have been reviewing the current specification. Even though it yet makes
quite a mature impression I found some flaws that may should be revised.

The .xsd files in Appendix C require a valid mmi-representation to have
qualified attributes.
------------------------------------------------------------
attributeFormDefault="qualified"
elementFormDefault="qualified"
------------------------------------------------------------

Given that it seems Appendix B is not in line with the spec.
Examples there  (see exerpt below)  are not using qualified attributes.
------------------------------------------------------------
<mmi:newContextRequest source="someURI" target="someOtherURI"
requestID="request-1">
</mmi:newContextRequest>
------------------------------------------------------------

On the other side examples in Appendix E are valid to the xsd definition:
------------------------------------------------------------
<mmi:startRequest mmi:requestID="1.237204761416E12"
mmi:context="IM_dcc3c320-9e88-44fe-b91d-02bd02fba1e3"
mmi:target="GUI">
  <mmi:contentURL>login</mmi:contentURL>
  <mmi:data>
    <gui resourceid="login" xml:lang="de-DE">
      <data id="back" enabled="false"/>
      <data id="next" enabled="false"/>
    </gui>
  </mmi:data>
</mmi:startRequest>
------------------------------------------------------------


Another minor issue I came across was that in Appendix F.2 the spec states:
------------------------------------------------------------
[...]The parameter timeout is optional and describes the maximum delay
in milliseconds.[...]
------------------------------------------------------------

Whereas the following sequence diagrams are using seconds as time unit.
------------------------------------------------------------
timeout:
e.g. 30 sec
------------------------------------------------------------


That's what I came across so far. Overall it is fair to say that the
working draft makes a good impression on me.


Regards,
Jakob Sachse.



					
-------------------------------------------------------------------------------------------------------------------
CONFIDENTIALITY NOTICE: This e-mail and any files attached may contain confidential and proprietary information of Alcatel-Lucent and/or its affiliated entities. Access by the intended recipient only is authorized. Any liability arising from any party acting, or refraining from acting, on any information contained in this e-mail is hereby excluded. If you are not the intended recipient, please notify the sender immediately, destroy the original transmission and its attachments and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Copyright in this e-mail and any attachments belongs to Alcatel-Lucent and/or its affiliated entities.

Received on Monday, 27 June 2011 14:02:51 UTC