1 / 28

So, you have learnt how a specification is updated via CRs and edited by the WG Secretary.

The lonely road or How a spec gets from WG Secretary to the server, and how it gets published as an ETSI deliverable. So, you have learnt how a specification is updated via CRs and edited by the WG Secretary. If you haven’t, then read this first: http://www.etsi.org.

bcarper
Download Presentation

So, you have learnt how a specification is updated via CRs and edited by the WG Secretary.

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. The lonely roadorHow a spec gets from WG Secretary to the server, and how it gets published as an ETSI deliverable

  2. So, you have learnt how a specification is updated via CRs and edited by the WG Secretary. If you haven’t, then read this first: http://www.etsi.org Now get a fascinating insight into the adult phase of a spec’s life cycle.

  3. The WG Secretary sends the updated new spec to the Specifications Manager – normally by e-mail.

  4. The Specifications Manager extracts the spec (or specs) from the e-mail ...

  5. …and files the incoming specs by date and by provider in a holding area.

  6. The source file is then examined.

  7. Correct title?(according to database)

  8. Correct version?(according to database)

  9. Correct date?(according to TSG meeting)

  10. Correct Release?(according to CRs approved)

  11. Correct logos?(GSM specs require GSM logo)

  12. Correct keywords?(per WPM)

  13. Correct template?(3gpp_70.dot)

  14. Correct layout?(in print layout view)

  15. Correct pagination?(ToC compared with actual layout)

  16. Correct change history?(cf. CR database)

  17. The presence of any necessary ancillary files (ASN.1, C code, ATS TTCN, PICS, …) is checked.

  18. If the Specifications Manager is not satisfied that the spec is correct in these respects …

  19. … he will return it to the WG Secretary for correction.

  20. But if all is well …

  21. … the MCC database record is updated to show that the spec exists.

  22. And so is the generic record in the ETSI WPM database.

  23. Then the spec is put on the the internal network drive:

  24. …and on to the external file server: http://www.3gpp.org/ftp/Specs/2000-12/R1999/24_series/

  25. …if the spec is to be published by the SDOs (i.e. it pertains to a frozen release), it is converted to PDF format*: * The ETSI route is shown.

  26. Its subsequent treatment in ETSI is described in a separate presentation.

  27. In addition, its version-specific record in WPM is created and details filled in:

  28. And so to the next spec … last slide

More Related