This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 25040 - [OMA-PUSH] reference should be more specific
Summary: [OMA-PUSH] reference should be more specific
Status: RESOLVED INVALID
Alias: None
Product: WebAppsWG
Classification: Unclassified
Component: Push API (show other bugs)
Version: unspecified
Hardware: PC All
: P2 normal
Target Milestone: ---
Assignee: Bryan Sullivan
QA Contact: public-webapps-bugzilla
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-03-13 12:12 UTC by Arthur Barstow
Modified: 2015-10-06 11:29 UTC (History)
3 users (show)

See Also:

Attachments

Description Arthur Barstow 2014-03-13 12:12:20 UTC 
The Push API's [OMA-PUSH] reference is <http://technical.openmobilealliance.org/Technical/release_program/push_v2_3.aspx> and that resource lists over 25 documents including over 10 specifications. This seems too "loose" for a Normative reference and as such the specific document(s) should be identified. 

On the other hand, if the intent is for this reference to be non-normative, the reference is probably ok but the reference should be moved to the Informative references section i.e. section B.2.
Comment 1 Michael[tm] Smith 2014-03-21 06:03:18 UTC 
(In reply to Art Barstow from comment #0)
> The Push API's [OMA-PUSH] reference is
> <http://technical.openmobilealliance.org/Technical/release_program/push_v2_3.
> aspx> and that resource lists over 25 documents including over 10
> specifications. This seems too "loose" for a Normative reference and as such
> the specific document(s) should be identified. 
> 
> On the other hand, if the intent is for this reference to be non-normative,
> the reference is probably ok but the reference should be moved to the
> Informative references section i.e. section B.2.

Yes, as should a number of other things are currently listed as normative refs. See bug 25108.
Comment 2 Arthur Barstow 2015-10-06 11:29:39 UTC 
The Push API spec no longer references OMA specs so this bug is now considered invalid <https://w3c.github.io/push-api/#references>.