Fwd: New OASIS logo and font color for TC file production (plus new Security Considerations section)

FYi, so I can reference this is in a GitHub issue.

    

    
Best,

      Kris

      

      Kristen James Eberlein

      Chair, OASIS DITA Technical Committee

      Principal consultant, Eberlein Consulting

      www.eberleinconsulting.com

      +1 919 622-1501; kriseberlein (skype)

      

    

    

      

      -------- Forwarded Message --------
      
        
          

            Subject:
            
            New OASIS logo and font color for TC file production
              (plus new Security Considerations section)
          

          

            Date: 
            Thu, 26 Jul 2018 15:14:14 -0400
          

          

            From: 
            Paul Knight <>
          

          

            To: 
            G. Ken Holman <>,
              Kristen Eberlein <>, Jim
              Amsden <>, Bob Stayton
              <>, Romano Jason
              <>, Norman Walsh
              <>, Michael S. Tsirkin
              <>, Rob Godfrey
              <>, Mr. Stefan Hagen
              <>
          

          

            CC: 
            Chet Ensign <>
          

        
      
      

      

      
Hi all,
        

        

        
You are among the most active TC leaders and editors
          involved with "self-publishing" TCs, preparing HTML and likely
          PDF files.

        

        

        
For Work Products based on the OASIS MS-Word or Open Office
          templates, this is probably not applicable - we will handle
          the changes discussed below during your next publication
          cycle.

        

        

        
The OASIS team is in the process of updating our logo and
          related color schemes, and we'd like to make these elements
          available for you to use in your future publications. We may
          not be aware of all the ways the logo and color elements are
          referenced and used, so please let us know what we can do to
          help you implement this change. We will likely need to draw on
          your expertise.

        

        

        
I've also included below the background for a
          highly-recommended new document section (Security
          Considerations). 

        

        

        
We expect the logo modifications to be fairly
          non-disruptive, involving a new logo file and a single changed
          color for titles and section headings.

        

        

        
The first example was just published at:

        
http://docs.oasis-open.org/bdxr/bdx-smp/v2.0/csprd01/bdx-smp-v2.0-csprd01.html

        

        

        
Here are the initial details, below.  Please let me or Chet
          know if you have any questions or concerns, or if you know of
          other TCs who need this information.  As noted below, we want
          to discuss a strategy for DocBook users with interested
          members.
          

          

          
************
             begin
              logo and font info *********
          

          

            
PREVIOUS:

            
Logo: http://docs.oasis-open.org/templates/OASISLogo.jpg
              (203x54)

            
Title and section header text color: OASIS purple 
              #3B006F  (59-00-111 RGB) or  #66116D (102-17-109 RGB)

            
CSS file: http://docs.oasis-open.org/templates/css/OASIS_Specification_Template_v1-0.css

            

              
or

              
DocBook
                CSS files: 

              
-
                http://docs.oasis-open.org/templates/DocBook/spec-0.6/css/oasis-spec.css 
                or

            

            

              -
                http://docs.oasis-open.org/templates/DocBook/spec-0.7/css/oasis-spec.css 

            
or OTHER ?? - please let us know.  
              

            

            
NEW:

            
Logo: http://docs.oasis-open.org/templates/OASISLogo-v2.0.jpg
              (250x55)

            
Title and section header text color: OASIS dark blue 
              #446CAA  (68-108-170 RGB)

            
CSS file: http://docs.oasis-open.org/templates/css/OASIS_Specification_Template_v2-0.css

            
or 

            
DocBook CSS files - we still need to address an update
              strategy here! Please contact me and Chet so we can keep
              you up to date.

            

            

            
DISCUSSION:

            
The new logo file switches the positions of the graphic
              "bug" and the word "OASIS", and has no border.

            
Other versions of the logo file are available by
              contacting me or Chet, if needed:

            
- with higher resolution

            
- other formats (PNG, EPS, AI, as well as JPG)

            
- with a border

            
- with a black background

            
- the "bug" by itself

            

            

            
The new logo file has a bit wider aspect ratio than the
              previous one. The letter "O" is round. To avoid
              compressing the logo and distorting the text, please
              update the pixel measurements in HTML or XML code when
              using the new file, similar to:

            

            

            

            
<a href=""https://www.oasis-open.org/"
                moz-do-not-send="true">https://www.oasis-open.org/">

            
  <img src=""http://docs.oasis-open.org/templates/OASISLogo-v2.0.jpg"
                moz-do-not-send="true">http://docs.oasis-open.org/templates/OASISLogo-v2.0.jpg"
              alt="OASIS logo" width="250" height="55" />

            
</a>

            

            

            

          

          
***************** end of logo and font info *********

          
***************** begin Security Considerations
            ***********

          

            The 
                Security
                  Considerations section is intended to
              help you (as specification developers) share your insights
              into security aspects of your specifications with the
              implementers or users of your specifications.  We are
              including this section as part of each new standards-track document
              template.

          

          

            

          

              
Please add new major section named "Security
                Considerations"

              

              

              
(Note: OASIS strongly recommends that Technical
                Committees consider issues that could affect security
                when implementing their specification and document them
                for implementers and adopters. For some purposes, you
                may find it required, e.g. if you apply for IANA
                registration.

              
While it may not be immediately obvious how your
                specification might make systems vulnerable to attack,
                most specifications, because they involve communications
                between systems, message formats, or system settings,
                open potential channels for exploit. For example, IETF
                [RFC3552] lists “eavesdropping, replay, message
                insertion, deletion, modification, and
                man-in-the-middle” as well as potential denial of
                service attacks as threats that must be considered and,
                if appropriate, addressed in IETF RFCs. 

              
In addition to considering and describing foreseeable
                risks, this section should include guidance on how
                implementers and adopters can protect against these
                risks.

              
We encourage editors and TC members concerned with
                this subject to read Guidelines for Writing RFC Text on
                Security Considerations, IETF [RFC3552], for more
                information.)

              

              

              
Also, if you reference RFC 3552 within your "Security
                Considerations" section, please add it to "Non-Normative
                References":

              

              

              
[RFC3552]	Rescorla,
                E. and B. Korver, "Guidelines for Writing RFC Text on
                Security Considerations", BCP 72, RFC 3552, DOI
                10.17487/RFC3552, July 2003, <https://www.rfc-editor.org/info/rfc3552>.

              

                *****************
                  end of Security Considerations ***********
                

              

            

          

          

          
Best regards,

          
Paul

          

          

          
New and old logo files attached:

          

          

          

            

            

            

            

            

          

          

          

          -- 

          

            

              

                

                  

                    

                      

                        
Paul
                              Knight  - Tel: +1 781-883-1783

                            OASIS
                            - Advancing open standards for the
                            information society - Document
                              Process Analyst

                          

                        

                        

                        
Borderless
                            Cyber 2018, 3-5
                                  Oct,
                            Washington, D.C.
                          Organized
                            by The World Bank, OASIS, and Georgetown
                            University