Saturday, 28 May 2011
Thursday, 26 May 2011
Wednesday, 25 May 2011
Tuesday, 24 May 2011
Thursday, 12 May 2011
- Bug 039: No Bug Tracker
- Bug 038: DOM and Multimedia Content
- Re: Bug 037: Meeting F03
- Re: Bug 036: Wrong Section Numbering
- Re: Bug 035: Missing Requirements
- Bug 037: Meeting F03
- Bug 036: Wrong Section Numbering
- Bug 035: Missing Requirements
- Bug 034: Recommendations not Notes
Wednesday, 11 May 2011
- Re: Bug 025: Instances of TestMode
- Bug 033: Alternative Serialisation
- Bug 032: Requirements for JSON
- Bug 031: Relationship to TAP and xUnit XML
- Bug 030: Advanced Usage
- Bug 029: Contributor Names
- Bug 028: DC and DCT
- Bug 027: Defining Terms in Sections
- Bug 026: Domain of assertedBy
- Bug 025: Instances of TestMode
- Bug 024: TestRequirement Terminology
- Bug 023: OutcomeValue and TestMode Metadata
- Bug 022: OutcomeValue Problems
- Bug 021: Pointers and Subjects
- Bug 020: OutcomeValue as a Constrained Literal
- Bug 019: OutcomeValue Metadata
- Bug 018: Useless TestResult Intermediary
- Bug 017: Unclear Meaning of TestRequirement
- Bug 016: The Schema and Guide Conflict
- Bug 015: Unclear TestSubject Subclassing
- Bug 014: earl:Software is Unclear
- Bug 013: Inconsistent Naming
- Bug 012: Group mainAssertor with assertedBy
Tuesday, 10 May 2011
- Bug 011: Terms are Underdefined
- Re: Bug 010: The mainAssertor Property is Aberrant
- Bug 010: The mainAssertor Property is Aberrant
- Bug 009: Vocabulary Terms are Not Reusable
- Bug 008: Ingenious Tool Range
- Bug 007: Vocabulary Control
- Bug 006: Extensibility Policy
- Bug 005: Reification Trick
- Bug 004: EARL Report Profiles
- Bug 003: Machine Readable Conformance Data
- Bug 002: Report Conformance in the Wrong Place
- Bug 001: Unclear Schema
- Bug 000: Metabug