Changes between Version 12 and Version 13 of RdsMaintenanceProcedureTest

Show
Ignore:
Timestamp:
02/05/14 10:43:54 (10 years ago)
Author:
lhella (IP: 80.202.81.134)
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • RdsMaintenanceProcedureTest

    v12 v13  
    2424 
    2525=== Evaluation of the Change Request === 
    26 The CR is checked for completeness and consistency by the PCA RD Maintenance Team staff, and the CR is given status identifier "'''''for evaluation'''''". This step includes ensuring that all mandatory administrative and meta-data entries are appropriately filled-in and that any necessary accompanying items are sufficient for evaluation.  This check is fully automated. 
     26The CR is checked for completeness and consistency by the PCA RD Maintenance Team staff, and the CR is given status identifier "'''''for evaluation'''''". This step includes ensuring that all mandatory administrative and meta-data entries are appropriately filled-in and that any necessary accompanying items are sufficient for evaluation.  This check is fully automated. 
    2727 
    28 If this initial check is satisfactory the Proposer is notified about the status update. When a CR has passed this initial check, the content will be uploaded to the PCA Development endpoint. If the CR is deemed not to be satisfactory, the Proposer is notified with the reason(s) for rejection. 
     28If this initial check is satisfactory the Proposer is notified about the status update. When a CR has passed this initial check, the content will be uploaded to the PCA Development endpoint. If the CR is deemed not to be satisfactory, the Proposer is notified with the reason(s) for rejection. 
    2929 
    3030If the quality of the information in the CR is satisfactory, the PCA RD Maintenance Team Staff sets the status of the Change Request to "'''''for validation'''''" and notifies the Proposer about status update. If the CR is deemed not to be satisfactory, the Proposer is notified with the reason(s) for rejection. 
     
    3535The PCA SIG Validation Team Responsible determines whether the Change Request (Work Package) is within the scope of the PCA RDL and valid for evaluation (or should be rejected). 
    3636 
    37 For the validation to be satisfactory (valid) more than half (a simple majority) of the PCA SIG Validation Team members must approve the proposed updates. If the Proposer of a CR is a SIG, then a validation team must be assigned by the PCA TAB. The team must consist of domain experts that has been part of developing the CR, external domain experts and ISO 15926 experts. 
     37For the validation to be satisfactory (valid) more than half (a simple majority) of the PCA SIG Validation Team members must approve the proposed updates. If the Proposer of a CR is a SIG, then a validation team must be assigned by the PCA TAB. The team must consist of domain experts that has been part of developing the CR, external domain experts and ISO 15926 experts. 
    3838 
    3939=== Resolution of the CR === 
     
    5151 
    5252== Definition and clarification of terms == 
    53 ''Add definition of terms by modifying definitions in ISO ST_DBS N52 (Rev 1)'' 
    54  
    5553=== Terms for general use === 
    5654 * PCA 
Home
About PCA
Reference Data Services
Projects
Workgroups