On Monday 20 September 2010 00:46:32 Skarpness, Mark wrote: > On Sep 19, 2010, at 4:23 PM, Graham Cobb wrote: > > Take the "compliant" word off the table, reduce the heat in this thread, > > and let marketing do their job of brand creation, don't try to guess what > > they will decide. > > Of course we are not focused on the exact marketing name here (though a > name like "DLNA certified", which shows up on lots of consumer devices, is > pretty similar to "MeeGo Compliant"). > > My point is that the technical contents of the MeeGo compliance spec > absolutely do matter to the marketing people...because that's the > foundation of the marketing messages (i.e. what does "MeeGo Compliant" > actually mean...).
Great, it looks like we are making progress. Here are my proposals for the small number of text changes required to make this a technical definition of applications which will qualify for the marketing brand. I suggest the following replacement text for the Introduction (lines 5-11): ----------- start replacement text ----------- This specification defines the operating system interface and environment of the MeeGo operating system to enable binary application compatibility. It is intended to be used by both application developers and system implementers. This spec defines the requirements for a system to be MeeGo Compliant and the requirements for applications to receive guarantees of compatability across MeeGo Compliant systems. MeeGo is a registered trademark of the Linux Foundation, which controls the usage of the brand and trademark. A requirement for permission to use is compliance with the requirements of this specification. An additional MeeGo brand will be defined for applications which will allow users to quickly recognise applications which are guaranteed to be compatible with their system (possibly subject to the Profile). In this version of MeeGo, this brand will only be available to MeeGo Core Apps (as defined below). Possible extension to other applications is a matter for further study and will be considered for future MeeGo versions. ----------- end replacement text ----------- Replace lines 21-22: System implementations may only claim compliance to a specific profile. Applications may claim compatability with a specific Profile or more generally to MeeGo to target multiple profiles. Delete lines 23-24. The substantive change is the following replacement text for sections 1.3.2 and 1.3.3. ----------- start replacement text ----------- 1.3.2 MeeGo Platform App An application is defined to be a MeeGo Platform App if it meets the following requirements: <Include list from existing section 1.3.2> o It shall be packaged into a single package file with no dependencies on any packages except packages which form part of the MeeGo API or Platform API. o It shall only use APIs and features included in the MeeGo API or Platform API sets. 1.3.3 MeeGo Core App An application is defined to be a MeeGo Core App is it meets the following requirements: o It meets all requirements for a MeeGo Platform App o It shall be packaged into a single package file with no dependencies on any packages except packages which form part of the MeeGo API. o It shall only use APIs and features included in the MeeGo API set. Note that MeeGo Core Apps are a subset of MeeGo Platform Apps. 1.3.4 Forward and Backward Compatability MeeGo Core Apps are assured compatibility with all future versions with the same MeeGo major version number. MeeGo Platform Apps are assured compatibility only with the specific MeeGo version they were built for. There are no assurances that an application constructed for a particular version will run on any earlier version. ----------- end replacement text ----------- In section 3.1, only two small changes are required: Line 141: Application Packages Line 142: Applications SHALL be packaged in RPM package file format. Similarly, in section 3.3: Line 227: Application Executables Line 228: Application executables shall be in the ELF format as described above Lines 231-232: delete. _______________________________________________ MeeGo-dev mailing list [email protected] http://lists.meego.com/listinfo/meego-dev
