 |
Open Services for Lifecycle Collaboration Performance Monitoring Vocabulary
|
Status: Under Construction

Draft covering 2.0 Scenarios - 9 May 2012
Authors
Contributors
Table of Contents
License
This work is licensed under a
Creative Commons Attribution License.
Notation and Conventions
The key words “MUST”, “MUST NOT”, “REQUIRED”, “SHALL”, “SHALL NOT”, “SHOULD”, “SHOULD NOT”, “RECOMMENDED”, “MAY”, and “OPTIONAL” in this document are to be interpreted as described in
RFC2119. Domain name examples use
RFC2606.
Introduction
(this section is informative)
This vocabulary defines elements, i.e. re-usable types and properties, added by the Open Services for Lifecycle Collaboration (OSLC) Performance Monitoring domain. It is managed by the
OSLC Performance Monitoring Working Group. Think of them as contributions to a distributed dictionary.
Any of its elements can be used in any context, as long as such usage does not conflict with any normative requirements (MUST, etc) imposed here. Indeed, encouraging broad re-use of a minimal size dictionary in many different contexts is the purpose of separating the elements from their re-use in a specific context like Performance Monitoring. This is why there are no "occurs" constraints here, for example. "Occurs" constraints imposed in order to meet one set of sceanarios, e.g. Performance Monitoring 2.0, may be different than the constraints needed for other scenarios.
Namespaces
In addition to the namespace URIs and namespace prefixes defined in the
OSLC Core specification, OSLC Performance Monitoring defines the namespace URI of
http://open-services.net/ns/perfmon#
with a namespace prefix of
oslc_perf
. This namespace URI and prefix are used to designate the resources and properties defined here.
Resource: Performance Monitoring Record (old way)
- Name:
PerformanceMonitoringRecord
- Description: A resource representing performance monitoring information.
- Type URI
http://open-services.net/ns/perfmon#PerformanceMonitoringRecord
PerformanceMonitoringRecord Properties (old way)
Prefixed Name |
Value-type |
Description |
OSLC Core: Common Properties |
dcterms:contributor |
AnyResource |
Contributor or contributors to resource (reference: Dublin Core). It is likely that the target resource will be an foaf:Person but that is not necessarily the case. |
dcterms:created |
DateTime |
Timestamp of resource creation (reference: Dublin Core) |
dcterms:creator |
AnyResource |
Creator or creators of resource (reference: Dublin Core). It is likely that the target resource will be an foaf:Person but that is not necessarily the case. |
dcterms:description |
XMLLiteral |
Descriptive text (reference: Dublin Core) about resource represented as rich text in XHTML content. SHOULD include only content that is valid and suitable inside an XHTML <div> element. |
dcterms:identifier |
String |
A unique identifier for a resource. Assigned by the service provider when a resource is created. Not intended for end-user display. |
dcterms:modified |
DateTime |
Timestamp of latest resource modification (reference: Dublin Core) |
rdf:type |
Resource |
The resource type URIs. |
dcterms:subject |
String |
Tag or keyword for a resource. Each occurrence of a dc:subject property denotes an additional tag for the resource. |
dcterms:title |
XMLLiteral |
Title (reference: Dublin Core) of the resource represented as rich text in XHTML content. |
oslc:instanceShape |
Resource |
Resource Shape that provides hints as to resource property value-types and allowed values. |
oslc:serviceProvider |
Resource |
The scope of a resource is a link to the resource's OSLC Service Provider. |
Prefixed Name |
Value-type |
Description |
OSLC Performance Monitoring: Start of additional properties |
oslc_perf:responseTime |
Resource |
Response time. |
Resources
Prefixed Name |
Description |
oslc_perf:PerformanceMonitoringRecord |
A resource representing performance monitoring information. |
Properties
Appendix A: Samples (this section is informative)
See
PmVocabularySamples?
Appendix C: Notices and References
Contributors
Reporting Issues
The working group participants who author and maintain this document monitor a distribution list where issues or questions can be raised, see
Performance Monitoring Mailing List
Also the issues found with this specification and their resolution can be found at
PmSpecificationV2Issues? .
Authors and Contact Information
Intellectual Property Covenant
The members of the Working Group (or as appropriate, their employers) have documented a Patent Non-Assertion Covenant and/or Patent License for implementations of Specifications based on this vocabulary, e.g. the Performance Monitoring 2.0 Specification, as described in the open-services.net
Terms of Use.
References