This specification defines the OSLC vocabulary terms for OSLC Systems Modeling Language Version 2.0. Part 1: Specification, and OSLC representation of the OMG Systems Modeling Language v2.

Introduction

This specification defines vocabulary terms for OSLC Systems Modeling Language Version 2.0 [[!SysML]] resources. The intent is to define resources needed to support common integration scenarios that utilize OMG Systems Modeling Language v2. The resource formats are intended to define RDF resources that enable model elements in typical Model-Based Systems Engineering methods using SysML v2 to integrate with other OSLC resources including Requirements, Archaitecture Management Resources, Change Requests, Test case, etc.

Terminology

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]]. Terminology for this specification is defined in part 1 of the multi-part specification.

References

In addition to the namespace URIs and namespace prefixes oslc, rdf, dcterms and foaf defined in the OSLC Core specification, OSLC SysML v2 defines the namespace URI of http://open-services.net/ns/sysmlv2# with a namespace prefix of oslc_sysmlv2

This specification also uses these namespace prefix definitions:

SysML v2 Vocabulary Terms

Property value types that are not defined in the following sections, are defined in [[!OSLCCore3]].

OSLC SysML v2 defines a set of properties for OMG SysML v2 resources. However, service implementations are free to extend this set of properties. Clients MUST preserve properties it does not recognize when updating resources. OSLC SysML v2 Servers MAY ignore properties that it does not recognize. Additional properties may come from existing vocabularies (ie. Dublin Core, OWL). When additional properties do not come from a known vocabulary, it is recommended that they exist in their own unique namespace, and providers SHOULD NOT reuse namespaces defined in these specifications.

All RDF/XML resources that include links with annotations MUST begin with an outer <rdf:RDF> element. This outer XML element is required to support the ability to include annotations on ‘link’ properties with additional <rdf:Description> elements reifying statements about the link.

Service implementations and clients MUST be prepared to accept any form of valid RDF/XML. For example the following two resource forms are equivalent. 

<rdf:RDF
   xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
   xmlns:oslc="http://open-services.net/ns/core#"
   xmlns:oslc_sysmlv2="http://open-services.net/ns/sysmlv2#"
   xmlns:dcterms="http://purl.org/dc/terms/">

    <oslc_sysmlv2:PartDef rdf:about="https://example.com/resources/res1">
      <dcterms:title>Service Interface</dcterms:title>
      <dcterms:identifier>res1</dcterms:identifier>
      <oslc:serviceProvider rdf:resource="http://open-services.net/ns/sysmlv2#"/>
    </oslc_sysmlv2:PartDef>
</rdf:RDF>

is equivalent to

<rdf:RDF
   xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
   xmlns:oslc="http://open-services.net/ns/core#"
   xmlns:dcterms="http://purl.org/dc/terms/">

    <rdf:Description rdf:about="https://example.com/resources/res1">
      <dcterms:title>Service Interface</dcterms:title>
      <dcterms:identifier>res1</dcterms:identifier>
      <rdf:type rdf:resource="http://open-services.net/ns/sysmlv2#PartDef" />
      <oslc:serviceProvider rdf:resource="http://open-services.net/ns/sysmlv2#"/>
    </rdf:Description>
</rdf:RDF>

This specification defines a number of specific, commonly occurring vocabulary terms (OWL classes), properties and values. Servers may define additional classes and provide additional properties as needed.

Conformance

OSLC SysML v2 servers MUST use the vocabulary terms defined here where required, and with the meanings defined here.

OSLC SysML v2 servers MAY augment this vocabulary with additional classes, properties, and individuals.