W3C home > Mailing lists > Public > public-webtiming@w3.org > February 2016

Re: [timingobject] Access restrictions for timing objects

From: François Daoust via GitHub <sysbot+gh@w3.org>
Date: Mon, 29 Feb 2016 16:52:04 +0000
To: public-webtiming@w3.org
Message-ID: <issue_comment.created-190285497-1456764723-sysbot+gh@w3.org>
I agree that it would be useful to expose a property that tells 
whether a `TimingObject` instance is read/write or read-only.

I would suggest to use a `readOnly` boolean property similar to that 
used for `input` fields in HTML:
http://w3c.github.io/html/sec-forms.html#elementdef-input

A boolean property will not allow to capture more granular access 
control rights, but I would not do that unless there is a compelling 
reason to do so. Timing providers may reject update operations that 
they do not want to allow for a given user, and applications can 
implement the logic necessary to prevent such errors from happening in
 the first place.

-- 
GitHub Notification of comment by tidoust
Please view or discuss this issue at 
https://github.com/webtiming/timingobject/issues/21#issuecomment-190285497
 using your GitHub account
Received on Monday, 29 February 2016 16:52:10 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 19:25:15 UTC