Proposed changes to oslc-core-v3.html

[Jim Amsden <jamsden@us.ibm.com>]

I'm starting through the specifications,
doing one final round of cleanup on the ones ready for public review and
attempting to complete the others. Here's some proposed changes to oslc-core-v3.html:

1. Update the chair and editor configuration information
(DONE)

2. The OSLC Core 3.0 Overview figure is missing Attachments
Do we have the source for these images somewhere?

3. The Glossary includes Resource Shape, but this is not
yet supported by LDP or included in OSLC 3.0. Should this be removed?

4. The loc-heading Vocabularies references Resource Shape
with is not yet supported by LDP. Should this reference be removed?

5. Section 5 references Vocabulary Evolution Guidance
which been concluded and is no longer active: https://wiki.oasis-open.org/oslc-core/VocabStableURINotes.
This should be removed.

6. Should compatibility with previous versions be “interoperability
with”?
Since OSLC is about interoperability between clients and
servers, not compatibility, should we adopt that term and approach to the
relationship between OSLC 2.0 and 3.0?

7. The meaning of the multi-part specification of OSLC
Core 3.0 capabilities needs to be clarified.
Is this paragraphs at the end of the OSLC Core 3.0 section
sufficient?
These documents comprise the multi-part specification
for OSLC Core 3.0. They represent common capabilities that servers MAY
provide and that may be discovered and used by clients. Although OSLC Core
could be useful on its own, it is intended to specify capabilities that
are common across many domains. Servers will generally specifiy conformance
with specific domain specifications, and those domain specificaitons will
describe what parts of OSLC Core are required for conformancde. This allows
servers to implement the capabilities they need in a standard without the
burden of implementing capabilities that are not required. OSLC Core Discovery
may allow clients to determine what capabilities are provided. Any provided
capability MUST meet all the conformacne criteria for that capabilitiy
as defined in the OSLC Core 3.0 specifications.

Jim Amsden, Senior Technical Staff Member
OSLC and Linked Lifecycle Data
919-525-6575