Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Implementation Report: Dec 2018 Test Fest Results #314

Merged
merged 52 commits into from
Dec 20, 2018

Conversation

mmccool
Copy link
Contributor

@mmccool mmccool commented Dec 3, 2018

Ready to merge. Results of Dec 2018 Testfest.

Recent updates:

  1. Updates to track TD master branch
    • For example, recent JSON-LD preprocessing updates)
  2. Security section (refers to external documents that don't yet exist, however)
    • This is intended to satisfy requirements stated in the WoT WG Charter
  3. Improved link management
    • Links to TD spec now open a separate named frame
  4. Test specifications
  5. Test results
  6. Updates to mergeresults.js script and test cases

mmccool and others added 30 commits November 29, 2018 23:06
After some discussions and analysis of assertions.
To do for type information.
Mark everything "at risk" that we do not yet have a test for.
Add Hitachi's Implementation Description.
Update how assertions should be documented
@mmccool mmccool changed the title WIP: Implementation Report updates (the series continues...) Implementation Report: Dec 2018 Test Fest Results Dec 20, 2018
@mmccool mmccool changed the title Implementation Report: Dec 2018 Test Fest Results WIP: Implementation Report: Dec 2018 Test Fest Results Dec 20, 2018
@mmccool mmccool changed the title WIP: Implementation Report: Dec 2018 Test Fest Results Implementation Report: Dec 2018 Test Fest Results Dec 20, 2018
@mmccool
Copy link
Contributor Author

mmccool commented Dec 20, 2018

Ready to merge; updated to master branch of TD spec. Note most edits are to things in the testing directory, however there are a couple of tweaks to ids in the spec itself to either make them consistent with the content or (in the case of td-at-type) avoid a syntax error (@ is not a valid character in HTML ids).

(OK, OK, technically @ is allowed in HTML5, but it was not allowed in HTML4, and the old td-@type id was causing various problems, so... as the id is generally invisible, except in the implementation report, on balance I think it's better to change it to avoid compatibility problems).

@mmccool mmccool merged commit f1eedca into w3c:master Dec 20, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

5 participants