'''NOTE:''' ''Several specifications can define a single feature. The ''navigator'' DOM property is a good example of this case.''
'''QUESTION:''' ''Do we need to make such data hard bind with Our compatibility data must embed the minimum requirement define below. More complete informations regarding the various specifications involved (such as their name or could they status) will be handled separately?''and are out of the scope of that project.
==== Name URLs ====
The name of All the specifications defining the feature. '''QUESTION:''' ''Do we need that name to be localisable?'' ==== URL ==== The URL URLs to the specification various specifications (or specification partsub-parts) defining the feature. ==== State ==== The state of a given specification '''NOTE:''' ''This can cover many ways to define a spec state. for example, the W3C has formal state (e.g. Working Draft, Candidate Recommendation, etc.) where the ECMA has version number for stable specification or code names for unstable specification.''
==== Notes ====
Any complementary information regarding a specifications defining the featuresfeature.
'''QUESTIONNOTE:''' ''Do we need to be able to comment a specification in this context? If yes, it MUST Those notes must be localisable.''
In a feature set, URLs and Notes of the children features are aggregate to provide the associate information of the specifications defining the feature set.
=== Browser ===
