• This specification builds on the Open Services for Lifecycle Collaboration (OSLC) Core v2.0 Specification to define the resources, properties and operations supported by an OSLC Asset Management (OSLC-Asset) provider. Asset Management resources include Assets, Artifacts and supporting resources defined in the OSLC Core specification. @en
  • This vocabulary defines the common characteristics of task management tools or issue tracking systems, such as Jira, Redmine or Trac. @en
  • The Lifecycle Schema provides classes and properties that allow the specification of a lifecycle that any resource may pass through. @en
  • This ontology defines generic concepts related to the life cycle of resource or service. @en
  • The Open Services for Lifecycle Collaboration (OSLC) initiative is creating a family of web services specifications for products, services and other tools that support all phases of the software and product lifecycle. This OSLC Core Specification sets out the common features that every OSLC Service can be expected to support @en
  • Planning and monitoring the execution of software projects can be carried out with different supporting tools, from issue tracking systems to Gantt chart tools or even with using simple spreadsheets. This vocabulary includes the common elements for controlling software development or maintenance projects. @en
  • During the modeling of software processes, work products are traditionally treated as atomic units, with names but no structure, and they are generated or changed during the course of the projects. In fact, the language SPEM does not offer mechanisms to detail the structure of work products, allowing only identify whether it is an artifact, a deliverable or an outcome of the project. The typical work products in the software processes are often documents or source code and they are managed from specialized or generic tools. For example, software modeling tools such as Rational Rose, or version control systems such as Git are examples of specialized tools that provide support to the management of certain types of work products. However, other generic tools such as content management systems, document management systems and collaborative editing systems or wikis can also be used to manage evidences of the processes. The design of models for certain types of work products has been an approach used in model-driven web methodologies. However, it is common the need for adapting and customizing well-known methodologies for their application in concrete situations and in specific organizations, a.k.a. process tailoring. Therefore, a vocabulary to define flexible work products in terms of structure and type of its artifacts is proposed here. @en
  • In Software Engineering, as well as in other disciplines, it is common to use model-editing tools using a visual language. In particular, the editing tools allow you to design UML software models, so that let you manage much of the work products of a project. From the study of several UML tools, such as Enterprise Architect, Visual Paradigm for UML or Rational Rose, this vocabulary has been defined. This vocabulary represents the basic structure of these UML tools, but does not exclude others that allow you to use other visual languages for modeling software systems or other entities. @en
  • This ontology ("wfdesc") describes an abstract workflow description structure, allowing the description of a scientific workflow as a direct acyclic graph, or a dataflow. This ontology is meant as an upper ontology for more specific workflow definitions, and as a way to express abstract workflows. The wfprov ontology shows how to link these descriptions to a provenance trace of a workflow execution. @en
  • The wfprov ontology shows how to express minimal provenance information about the execution of a workflow described using the wfdesc ontology. @en
  • From the study of different wiki systems, such as MediaWiki, Confluence or DokuWiki, this vocabulary has designed. Note that this vocabulary does not fully describe the conceptual model of all types of the wiki systems, but only their main elements. @en