An issues list for a particular deliverable, with an id and date. Issue list metadata A resolvable URI for the issues list. The name of the issues list. The date of the latest change to the issues list The revision number of the issues list An individual issue (of any kind). It must have a unique id and a recorded status. A short name for the issue. A detailed description of the issue's nature. What specification the issue is refering to. Optionally, it may include a link to the specific, relevand part of the specification. Editorial issues always refer to 'profile', and should link to the issue in the issues list. The type of the issue (editorial or design) A record of the issue's origin, optionally including its date and a link to where it was raised (e.g., in the mail archive) The WG member(s) who drives the resolution issue and is responsible for summarizing its status to the WG. Justification for the issue; e.g., a use case or architectural motivation. Proposed solutions for the issue. The final resolution of the issue; should be in specification text or nearly so. Related issue