Replace references to gh-pages with main.

Author: gkellogg

README.md

@@ -1,6 +1,6 @@
 # rdf-tests
 Repository for the RDF Tests Community Group
 
-See the [gh-pages](https://w3c.github.io/rdf-tests) branch for the main contents.
+To view (HTML) files can be [read directly](https://w3c.github.io/rdf-tests/).
 
 The index.html files are built using a Ruby tool-chain based on the corresponding manifest.ttl files. Update using `rake`. Requires Ruby, rdf-turtle and json-ld gems to be installed.

index.html

@@ -189,16 +189,16 @@ <h1>RDF Test Curation</h1>
   The <a href="http://json-ld.org/test-suite/">JSON-LD Test Suite</a> is managed through the <a href="https://github.com/json-ld/json-ld.org/">json-ld/json-ld.org</a> GitHub repository. <a href="http://github.com/json-ld/json-ld.org/issues">Issues</a> should be filed in that repository.
 </p>
 
-<p>The work of the CG is being performed on <a href="http://github.com/w3c/rdf-tests" target="_blank" rel="external nofollow">GitHub</a>. The list of test suites managed, is available through the <a href="https://w3c.github.io/rdf-tests/" target="_blank" rel="external nofollow">gh-pages view</a>. The general process followed is the following:</p>
+<p>The work of the CG is being performed on <a href="http://github.com/w3c/rdf-tests" target="_blank" rel="external nofollow">GitHub</a>. The list of test suites managed, is available through the <a href="https://w3c.github.io/rdf-tests/" target="_blank" rel="external nofollow">HTML view</a>. The general process followed is the following:</p>
 <ul>
 <li>New test suites may be added via a PR request against the rdf-tests repository, or by filing an issue using the <a href="http://github.com/w3c/rdf-tests/issues" target="_blank" rel="external nofollow">issue tracker</a> for subsequent activity.</li>
 <li>Proposed changes to a given test suite may be discussed on <a href="mailto:[email protected]" target="_blank">[email protected]</a> (<a href="https://lists.w3.org/Archives/Public/public-rdf-tests/" target="_blank">archive</a>), but ultimately should result in an <em>issue</em> being created on the <a href="http://github.com/w3c/rdf-tests/issues" target="_blank" rel="external nofollow">issue tracker</a>.</li>
-<li>Changes should either be made on a separate fork of the repository, and integrated via pull request, or on a feature branch within the main repository (prefix branch name with &#8220;feature-&#8221; or &#8220;issue-n-&#8220;, where &#8220;n&#8221; is the issue number relating to the proposed update). Any change that results in a functional change to an existing test suite <em class="rfc2119">MUST</em> be included by consensus of this group, and the related comments group of the associated working group, and <em class="rfc2119">SHOULD</em> have two implementations which pass the tests. Once consensus is reached, a pull request including this feature branch may be integrated into the main (gh-pages) branch.<br />
+<li>Changes should either be made on a separate fork of the repository, and integrated via pull request, or on a feature branch within the main repository (prefix branch name with &#8220;feature-&#8221; or &#8220;issue-n-&#8220;, where &#8220;n&#8221; is the issue number relating to the proposed update). Any change that results in a functional change to an existing test suite <em class="rfc2119">MUST</em> be included by consensus of this group, and the related comments group of the associated working group, and <em class="rfc2119">SHOULD</em> have two implementations which pass the tests. Once consensus is reached, a pull request including this feature branch may be integrated into the main branch.<br />
 Note that naming conventions for tests often make conflicting overlaps inevitable, so consider this when naming new tests and formatting the test manifests.</li>
-<li>Some updates, e.g. more extensive updates to the SPARQL test suite, may require branching off of, and merging back into, a separate feature branch, so that a set of changes can be staged before updating the gh-pages branch.</li>
+<li>Some updates, e.g. more extensive updates to the SPARQL test suite, may require branching off of, and merging back into, a separate feature branch, so that a set of changes can be staged before updating the main branch.</li>
 <li>After a changes to a given test suite become stable, a “release” branch can be created to record the state of the test suite at that time.</li>
 <li>All changes affecting a given test suite should be broadcast to the appropriate comments list (<a href="mailto:[email protected]">[email protected]</a> or <a href="mailto:[email protected]">[email protected]</a> at this point).</li>
-<li>Implementations can typically access a given test suite using the <a href="https://w3c.github.io/rdf-tests/" target="_blank" rel="external nofollow">gh-pages view</a>. For example, the Turtle test manifest can be accessed at  <a href="https://w3c.github.io/rdf-tests/turtle/manifest.ttl" rel="external nofollow">https://w3c.github.io/rdf-tests/turtle/manifest.ttl</a>. Accessing test suites though an alternative branch via HTTP requires the use of a different facility, such as <a href="https://raw.githubusercontent.com/w3c/rdf-tests/gh-pages/turtle/manifest.ttl" target="_blank" rel="external nofollow">https://raw.githubusercontent.com/w3c/rdf-tests/gh-pages/turtle/manifest.ttl</a>, where &#8220;gh-pages&#8221; is replaced by the appropriate branch name.</li>
+<li>Implementations can typically access a given test suite using the <a href="https://w3c.github.io/rdf-tests/" target="_blank" rel="external nofollow">HTML view</a>. For example, the Turtle test manifest can be accessed at  <a href="https://w3c.github.io/rdf-tests/turtle/manifest.ttl" rel="external nofollow">https://w3c.github.io/rdf-tests/turtle/manifest.ttl</a>. Accessing test suites though an alternative branch via HTTP requires the use of a different facility, such as <a href="https://raw.githubusercontent.com/w3c/rdf-tests/main/turtle/manifest.ttl" target="_blank" rel="external nofollow">https://raw.githubusercontent.com/w3c/rdf-tests/main/turtle/manifest.ttl</a>, where &#8220;main&#8221; is replaced by the appropriate branch name.</li>
 </ul>
 
 <p>The group is chaired by <a href="http://greggkellogg.net/foaf#me">Gregg Kellogg</a>. The W3C staff contact is xxx. If you are member of the Community Group, and you want to gain a “push” right to this repository, please contact <a href="mailto:[email protected]">[email protected]</a>, providing your github ID.</p>