W3C home > Mailing lists > Public > public-device-apis@w3.org > June 2010

RE: updates to Policy Framework and Profile

From: Suresh Chitturi <schitturi@rim.com>
Date: Tue, 22 Jun 2010 16:08:32 -0500
Message-ID: <D37CC1B151BD57489F4F89609F168FE805EA3DCD@XCH01DFW.rim.net>
To: <Frederick.Hirsch@Nokia.com>, <public-device-apis@w3.org>
Hi Frederick, all,

While reviewing the framework document, I encountered the following:

1) Lack of definitions for 'access request' and 'access query'. I assume
they are the same? It might be good to describe it in a subsection under
core concepts. 
2) Would it make sense to describe all the steps illustrated in logical
model under "4.2 Processing Rules" section? Right now, it is split into
"Processing Rules" and "Feature and Capability Processing Rules" which
is somewhat mis-leading. For e.g. are these done independently or is it
reasonable to say that they may be both may be evaluated in one shot?
3) As stated earlier (in one of the conference calls), I think we need
to understand the relation of this policy framework with the widgets
specifications (i.e. configuration file that includes <feature> and WARP
<access>). For example, how does the policy get evaluated in this case
when both a policy file is present and "policy type" elements such as
<feature> and <access> are declared in the widget package?



-----Original Message-----
From: public-device-apis-request@w3.org
[mailto:public-device-apis-request@w3.org] On Behalf Of
Sent: Monday, June 21, 2010 9:43 AM
To: public-device-apis@w3.org
Cc: Frederick.Hirsch@Nokia.com
Subject: updates to Policy Framework and Profile

I have made a number of changes to the Poilcy Framework and Profile
documents since last Thursday:

1. Edits to Framework based on Dom's editorial suggestions

2. Some additional restructuring of Framework document, added sections
for concepts including trust, features and capabilities. Added material
on trust from Nokia contribution.  Consolidated attribute definitions 

3. Profile - Moved attribute definitions from Framework to Profile

4. Profile - Incorporated examples from example document

5. Fixed numerous validation errors in Framework and Profile, both
validate now. Fixed markup for RFC language to ReSpec convention, got
rid of most <em> markup, using <code> where appropriate.

6. Fixed link checker issues in Framework/Profile, both ok now (though
some same document links may be to wrong destination since there were
duplicate ids defined.)

7. Removed Marcin from Policy editors list.

Dom also fixed additional formatting issues, thanks Dom.

I'll be looking at the content and organization more, but wanted to get
some of the basics out of the way in the first pass. 

Please review the documents so we can plan to publish later this week.


regards, Frederick

Frederick Hirsch

This transmission (including any attachments) may contain confidential information, privileged material (including material protected by the solicitor-client or other applicable privileges), or constitute non-public information. Any use of this information by anyone other than the intended recipient is prohibited. If you have received this transmission in error, please immediately reply to the sender and delete this information from your system. Use, dissemination, distribution, or reproduction of this transmission by unintended recipients is not authorized and may be unlawful.
Received on Tuesday, 22 June 2010 21:09:07 UTC

This archive was generated by hypermail 2.3.1 : Monday, 23 October 2017 14:53:44 UTC