Merge branch 'master' into b-qm-remove-cm_stuff

README.md

@@ -7,15 +7,15 @@ This repository is for managing the development of OSLC Open Project
 specifications including Core 3.0, OSLC Query, Tracked Resource Sets,
 Configuration Management, and all the various OSLC domain specifications.
 
-| Title | Description |Editor|
+| Title | Description |Responsible|
 |-------|-------------|------|
-| [Core 3.0 WD](https://oslc-op.github.io/oslc-specs/specs/core/oslc-core.html) | A collection of specifications that defines the basic patterns, protocols and capabilities of OSLC clients and servers. **PSD WIP** | Jim Amsden |
-| [Quality Management 2.1 WD](https://oslc-op.github.io/oslc-specs/specs/qm/quality-management-spec.html) | **PSD WIP** | TBD |
-| [Change Management 3.0 WD](https://oslc-op.github.io/oslc-specs/specs/cm/change-mgt-spec.html) | **PSD 02 ready** | Jim Amsden |
+| [Change Management 3.0 WD](https://oslc-op.github.io/oslc-specs/specs/cm/change-mgt-spec.html) | **PSD 02 ready** | Andrew |
+| [Core 3.0 WD](https://oslc-op.github.io/oslc-specs/specs/core/oslc-core.html) | A collection of specifications that defines the basic patterns, protocols and capabilities of OSLC clients and servers. **PSD WIP** | Jim/Andrew |
+| [Quality Management 2.1 WD](https://oslc-op.github.io/oslc-specs/specs/qm/quality-management-spec.html) | **PSD WIP** | Andrew |
+| [Requirements Management 2.1 WD](https://oslc-op.github.io/oslc-specs/specs/rm/requirements-management-spec.html) | TBD | Jad/Andrew |
+| [Tracked Resource Set 3.0 WD](https://oslc-op.github.io/oslc-specs/specs/trs/tracked-resource-set.html) | Allows servers to expose a set of resources whose state can be tracked by clients. **WD WIP** | Nick |
 | [Query 3.0 WD](https://oslc-op.github.io/oslc-specs/specs/query/oslc-query.html) | Defines a simple, implementation independent selection and projection query capability. | TBD |
-| [Tracked Resource Set 3.0 WD](https://oslc-op.github.io/oslc-specs/specs/trs/tracked-resource-set.html) | Allows servers to expose a set of resources whose state can be tracked by clients. | Nick Crossley |
-| [Requirements Management 2.1 WD](https://oslc-op.github.io/oslc-specs/specs/rm/requirements-management-spec.html) | TBD | Jad El-khoury |
-| [Configuration Management 1.0 WD](https://oslc-op.github.io/oslc-specs/specs/config/oslc-config-mgt.html) | Domain spec for managing versions and configurations of linked data resources from multiple domains. |Nick Crossley|
+| [Configuration Management 1.0 WD](https://oslc-op.github.io/oslc-specs/specs/config/oslc-config-mgt.html) | Domain spec for managing versions and configurations of linked data resources from multiple domains. |Nick|
 | [Asset Management 2.1 WD](https://oslc-op.github.io/oslc-specs/specs/asset/asset-management-spec.html) | TBD | NA |
 | [Automation 2.1 WD](https://oslc-op.github.io/oslc-specs/specs/auto/automation-spec.html) | Domain spec for automation of sequences of actions on OSLC resources. | NA |
 | [Performance Monitoring 2.1 WD](https://oslc-op.github.io/oslc-specs/specs/perfmon/performance-monitoring-spec.html) | TBD | NA |

specs/asset/asset-management-spec.html

@@ -370,11 +370,11 @@ <h2>Base Requirements</h2>
 <section id="baseCompliance">
 <h2>Base Compliance</h2>
 
-<p class=‘conformance’>This specification is based on [[!OSLCCore3]]. OSLC Asset Management servers
+<p class="conformance">This specification is based on [[!OSLCCore3]]. OSLC Asset Management servers
 MUST be compliant with both the core specification,  MUST follow all the mandatory requirements in the normative sections of this specification, and SHOULD follow all the guidelines and recommendations in both
 these specifications.</p>
 
-<p class=‘conformance’>An OSLC Asset Management server MUST implement the domain vocabulary defined in <a href="http://docs.oasis-open.org/oslc-domains/qm/v2.1/asset-v2.1-part2-asset-management-vocab.html">OSLC Asset Management Version 2.1. Part 2: Vocabulary</a>
+<p class="conformance">An OSLC Asset Management server MUST implement the domain vocabulary defined in <a href="http://docs.oasis-open.org/oslc-domains/qm/v2.1/asset-v2.1-part2-asset-management-vocab.html">OSLC Asset Management Version 2.1. Part 2: Vocabulary</a>
 
 <p>The following table summarizes the requirements from OSLC Core Specification
 as well as some additional requirements specific to the Asset domain. Note that
@@ -1006,4 +1006,4 @@ <h2>Change History</h2>
 
 </body>
 
-</html>
+</html>

specs/qm/quality-management-spec.html

@@ -232,14 +232,16 @@
 
 <section id='sotd'></section>
 
-<section id='intro' class='informative'>
-  <h2>Introduction</h2>
-  <p>This section is non-normative.</p>
+<section id='intro'>
+  <h1>Introduction</h1>
+  <section id='overview' class='informative'>
+  <h1>Overview</h1>
   <p>This specification builds on the OSLC Core Specification to define the resources and operations supported by an Open Services for Lifecycle Collaboration (OSLC) Quality Management (QM) provider.</p>
   <p>Quality Management resources define the test plans, test cases, and test results of the software delivery lifecycle. They represent individual resources along with their relationships to other shared resource types such change requests and requirements. The intent of this specification is to define the set of HTTP-based RESTful interfaces in terms of HTTP methods: GET, POST, PUT and DELETE, HTTP response codes, mime type handling and resource formats. The capabilities of the interface definitions are driven by key integration scenarios and therefore don't represent a complete setup of operations on resources or resource types. The resource formats and operations may not match exactly the native models supported by quality management service providers but are intended to be compatible with them. </p>
   <p>A key approach to supporting these scenarios is to delegate operations, as driven by service provider contributed user interfaces, as much as possible and not require a service provider to expose its complete data model and application logic. </p>
+  </section>
 
-  <section id='terminology' class='informative'>
+  <section id='terminology'>
     <h2>Terminology</h2>
     <p>Terminology is based on OSLC Core Overview [[!OSLCCore3]],
       W3C Linked Data Platform [[LDP]],
@@ -682,10 +684,24 @@ <h2>Version Compatibility with 2.0 Specifications</h2>
 
 <section class='appendix informative'>
   <h2>Acknowledgements</h2>
-  <p>This section is non-normative.</p>
-  <p>The following individuals have participated in the creation of the V2.0 specification and are gratefully acknowledged:</p>
 
-<p><b>Participants</b>:</p><p style="margin-left: 40px">
+  <p>The following individuals have participated in the creation of this specification and are gratefully acknowledged:</p>
+
+<p><b>Project Governing Board</b>:</p><p style="margin-left: 40px">
+James Amsden, IBM (co-chair)<br>
+Andrii Berezovskyi, KTH (co-chair)<br>
+Bill Chown, Mentor<br>
+Wesley Coelho, Tasktop<br>
+Axel Reichwein, Koneksys<br>
+</p>
+
+<p><b>Techical Steering Committee</b>:</p><p style="margin-left: 40px">
+James Amsden, IBM<br>
+Andrii Berezovskyi, KTH<br>
+Axel Reichwein, Koneksys<br>
+</p>
+
+<p><b>OSLC QM 2.0 contributors</b>:</p><p style="margin-left: 40px">
     Gray Bachelor (IBM - Editor)<br>
     Dave Johnson (IBM)<br>
     Ingrid Jorgensen (Tieto)<br>

specs/qm/quality-management-vocab.html

@@ -137,9 +137,11 @@
   <section id='toc'></section>
   <section id='sotd'></section>
 
-<section id="introduction" class="informative">
-<h2>Introduction</h2>
+<section id="introduction">
+<h1>Introduction</h1>
 
+<section id="overview" class="informative">
+  <h2>Overview</h2>
 <p>This specification defines a vocabulary and resource shapes for OSLC
     Quality Management resources. The intent is to define resources needed to
     support common integration scenarios and not to provide a comprehensive
@@ -154,11 +156,10 @@ <h2>Introduction</h2>
   <img src="oslc_qm_resources.png" />
   <figcaption>OSLC Quality Management 2.1 resource relationship overview</figcaption>
 </figure>
-
-
+</section>
 
 <section id="terminology">
-<h1>Terminology</h1>
+<h2>Terminology</h2>
 <p>Terminology is based on OSLC Core Overview [[!OSLCCore3]], W3C Linked Data
     Platform [[!LDP]], W3C's Architecture of the World Wide Web [[WEBARCH]],
     Hyper-text Transfer Protocol [[!HTTP11]].</p>

specs/recon/recon-resource-def.txt

@@ -1,17 +1,17 @@
 <section id="Resource-Definitions">
     <h2>Resource Definitions</h2>
 
-    <p class=‘conformance’>Resources defined by this specification can have properties other than those described here, in any namespace. It
+    <p class="conformance">Resources defined by this specification can have properties other than those described here, in any namespace. It
       is RECOMMENDED that any additional properties exist in their own unique namespace and not use the
       namespaces defined in this specification.</p>
 
-    <p class=‘conformance’>A list of properties is defined for each type of resource. Most of these properties are identified in <a
+    <p class="conformance">A list of properties is defined for each type of resource. Most of these properties are identified in <a
         href="https://archive.open-services.net/bin/view/Main/OSLCCoreSpecAppendixA.html"> OSLC Core Appendix A: Common Properties</a> and in the
       <a href="https://archive.open-services.net/wiki/reconciliation/Common-IT-Resource-Type-Vocabulary-Version-2.0/index.html">Common IT Resource Type vocabulary</a>. Any
       exceptions are noted. Relationship properties refer to other resources. These resources may be in any OSLC domain
       (including the Reconciliation domain).</p>
 
-    <p class=‘conformance’>For all resource types defined in this specification, all <strong>required</strong> properties (those defined
+    <p class="conformance">For all resource types defined in this specification, all <strong>required</strong> properties (those defined
       with an occurrence of <strong>exactly-one</strong> or <strong>one-or-many</strong>) MUST exist
       for each resource and must be provided when requested. All other properties are optional, and might not exist on
       some or any resources; those that do not exist will not be present in the returned representation even if
@@ -20,14 +20,14 @@
       own namespaces for such properties, or use standard Dublin Core or RDF namespaces and properties where
       appropriate.</p>
 
-    <p class=‘conformance’>If no specific set of properties is requested, <strong>all</strong> properties MUST be returned
+    <p class="conformance">If no specific set of properties is requested, <strong>all</strong> properties MUST be returned
       - both those defined in this specification as well as any provider-specific ones. See <a
         href="https://archive.open-services.net/bin/view/Main/OslcCoreSpecification.html#Selective_Property_Values">Selective Property Values</a>
       in the OSLC Core Specification.</p>
 
-    <p class=‘conformance’>Consumers should note that some resources may have a very large number of related resources, and that some
+    <p class="conformance">Consumers should note that some resources may have a very large number of related resources, and that some
       resources may be very large and/or expensive to compute. For this reason, consumers are strongly
         RECOMMENDED to use the <code>oslc.properties</code> parameter to limit the properties returned from a
       request to the subset required. See <a
         href="https://archive.open-services.net/bin/view/Main/OslcCoreSpecification.html#Selective_Property_Values">Selective Property Values</a>
-      in the OSLC Core Specification.</p>
+      in the OSLC Core Specification.</p>