User Tools

Site Tools


glossary

Getting Started

  • Objective of the system
    • Workflow, begin, end
  • Accessing JIRA
    • URL, login
  • JIRA and OMG
    • Task Forces, Issues
  • Task Force configuration
    • data, members, scope
  • Handling Issues
    • Creation, proposals, voting, wiki
  • Handling Ballots
    • Creation, voting, closing,
  • Report
    • Document numbers, attachments

JIRA Report Configuration

Chairs must setup some information regarding the Report.

The information they must fill the following concepts:

  • Target version number (the specification is defined by OMG Staff)
    • This is the version that wil be produced by the Task Force.
    • For Finalization Task Forces the version number should be a dot zero number (e.g 1.0, 2.0)
    • For Revision Task Forces the version should be a dot greater than zero (e.g 1.1, 2.2)
  • Inventory Files
    • The documents included in the Inventory must be submitted to the OMG to obtain a document number. This number is then entered in the form.
    • The document number for the report
    • The Specification document clean
    • The Specification document with change bars
  • Supporting Documents
    • Each document is submitted separately, each one receiving a document number. No support for details of a zip file in this section.

Supporting Documents

  • line format: docNumber##fileName
  • from docNumber system obtains:
    • Title
    • Description
    • status (Normative, Informative, Ancillary)
  • fileName is used to generate the document URL

Machine Readable Documents (submitted documents)

  • line format: docNumber##fileName##dependsOn
  • from docNumber system obtains:
    • Title
    • Description
    • status (Normative, Informative, Ancillary)
  • fileName is used to generate the document URL
  • dependsOn supports multiple files separated by semi-colons (;)

Machine Readable Documents (zip file)

  • line format: docNumber##zip
  • from docNumber system obtains:
    • Title
    • Description
    • status (Normative, Informative, Ancillary)
  • fileName is used to generate the document URL
  • dependsOn supports multiple files separated by semi-colons (;)
  • line format inner files: –##fileName##dependsOn##description
  • fileName is used to generate the document URL, please make the file inside the zip the same as the URL path

Glossary

TF = Task Force

Any OMG stablished group to handle a specification / version

JIRA Fields

Specification/Version

This field is a cascading select list populated with the list of specs and versions defined by OMG. Public submission forms use this field to identify the target of the issue.

Management of this list will be done via the following options:

  • upload a list via a Admin Script
  • when a new TF is created that refers to a new Spec/Version
  • edit the custom field configuration manually from the Admin Section (for super user fixing only)

This field also manages the relationship between JIRA Projects and the versions they edit. e.g.: Project BPMN_2_0 is handling issues for BPMN 2.0.

The format of the list is TBD

glossary.txt · Last modified: 2014/08/08 08:15 by admin