mime-types-data 3.2015.1120 → 3.2016.0221

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA1:
-  metadata.gz: 8019c22df10fb74742b68ba3150dc999e05272fd
-  data.tar.gz: d080290bd6ff77e569f286f6b1e08fd6b45ceda7
+  metadata.gz: bbd0e723900e0e1a5c21fe887f16604681e1764f
+  data.tar.gz: f299a5efaa2b0b6600b8c2125d521da9c6ea127a
 SHA512:
-  metadata.gz: aa2fd323ec7b07cd3319e8f585b1f1b7989dee7a1e970100c19861e3c9b3f1eb43b867d620decfcbe1ab09818ce69170431ffeab4fcd619c1c7752223ea8ccf1
-  data.tar.gz: 4cb89350012aac62e0d8ef810fcc2ad8f94f4c0790d2d22cfa65e5866f98e619aa46ec42194517fb49c52ce0883ea1929119c51f44cb46bc92f85aff11a05665
+  metadata.gz: 6c74ea4eb08d6132d4d1f5059aa51828c292ed6b61e3e9339918c43c51a4cd31ca1b791786e7280efb430720534614103f9cebcc0660d34c4e2bd18c1ca989dc
+  data.tar.gz: 1cb8192f22c9c3989a28e3fc157f32074f1054987624675c342883aeef2597ba7de396b3f487e557af12ae61482e74e898f8ef12dc8925fc3accdab72fcc5c3f

data/Code-of-Conduct.md

@@ -1,43 +1,75 @@
-## Contributor Code of Conduct
+# Contributor Covenant Code of Conduct
 
-As contributors and maintainers of this project, and in the interest of
-fostering an open and welcoming community, we pledge to respect all people who
-contribute through reporting issues, posting feature requests, updating
-documentation, submitting pull requests or patches, and other activities.
+## Our Pledge
 
-We are committed to making participation in this project a harassment-free
-experience for everyone, regardless of level of experience, gender, gender
-identity and expression, sexual orientation, disability, personal appearance,
-body size, race, ethnicity, age, religion, or nationality.
+In the interest of fostering an open and welcoming environment, we as
+contributors and maintainers pledge to making participation in our project and
+our community a harassment-free experience for everyone, regardless of age,
+body size, disability, ethnicity, gender identity and expression, level of
+experience, nationality, personal appearance, race, religion, or sexual
+identity and orientation.
+
+## Our Standards
+
+Examples of behavior that contributes to creating a positive environment
+include:
+
+* Using welcoming and inclusive language
+* Being respectful of differing viewpoints and experiences
+* Gracefully accepting constructive criticism
+* Focusing on what is best for the community
+* Showing empathy towards other community members
 
 Examples of unacceptable behavior by participants include:
 
-* The use of sexualized language or imagery
-* Personal attacks
-* Trolling or insulting/derogatory comments
+* The use of sexualized language or imagery and unwelcome sexual attention or
+  advances
+* Trolling, insulting/derogatory comments, and personal or political attacks
 * Public or private harassment
-* Publishing other's private information, such as physical or electronic
-  addresses, without explicit permission
-* Other unethical or unprofessional conduct.
+* Publishing others' private information, such as a physical or electronic
+  address, without explicit permission
+* Other conduct which could reasonably be considered inappropriate in a
+  professional setting
+
+## Our Responsibilities
+
+Project maintainers are responsible for clarifying the standards of acceptable
+behavior and are expected to take appropriate and fair corrective action in
+response to any instances of unacceptable behavior.
 
 Project maintainers have the right and responsibility to remove, edit, or
 reject comments, commits, code, wiki edits, issues, and other contributions
-that are not aligned to this Code of Conduct. By adopting this Code of Conduct,
-project maintainers commit themselves to fairly and consistently applying these
-principles to every aspect of managing this project. Project maintainers who do
-not follow or enforce the Code of Conduct may be permanently removed from the
-project team.
+that are not aligned to this Code of Conduct, or to ban temporarily or
+permanently any contributor for other behaviors that they deem inappropriate,
+threatening, offensive, or harmful.
 
-This code of conduct applies both within project spaces and in public spaces
-when an individual is representing the project or its community.
+## Scope
+
+This Code of Conduct applies both within project spaces and in public spaces
+when an individual is representing the project or its community. Examples of
+representing a project or community include using an official project e-mail
+address, posting via an official social media account, or acting as an
+appointed representative at an online or offline event. Representation of a
+project may be further defined and clarified by project maintainers.
+
+## Enforcement
 
 Instances of abusive, harassing, or otherwise unacceptable behavior may be
-reported by opening an issue or contacting one or more of the project
-maintainers.
+reported by contacting the project team at [INSERT EMAIL ADDRESS]. All
+complaints will be reviewed and investigated and will result in a response that
+is deemed necessary and appropriate to the circumstances. The project team is
+obligated to maintain confidentiality with regard to the reporter of an
+incident. Further details of specific enforcement policies may be posted
+separately.
+
+Project maintainers who do not follow or enforce the Code of Conduct in good
+faith may face temporary or permanent repercussions as determined by other
+members of the project's leadership.
+
+## Attribution
 
-This Code of Conduct is adapted from the [Contributor Covenant][covenant],
-version 1.2.0, available at
-[http://contributor-covenant.org/version/1/2/0/][covenant 1.2.0].
+This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 1.4,
+available at [http://contributor-covenant.org/version/1/4][version]
 
-[covenant]: http://contributor-covenant.org
-[covenant 1.2.0]: http://contributor-covenant.org/version/1/2/0/
+[homepage]: http://contributor-covenant.org
+[version]: http://contributor-covenant.org/version/1/4/

data/History.md

@@ -1,5 +1,33 @@
 # MIME Types Changes by Version
 
+## 3.2016.0221 / 2016-02-21
+
+*   Updated the known extensions list for audio/mp4.
+*   Updated the IANA media registry entries as of release date:
+
+    *   Updated metadata for 3GPP-defined types (there are many),
+        application/cdni, and application/rfc+xml.
+    *   Added application/EmergencyCallData.Comment+xml,
+        application/EmergencyCallData.DeviceInfo+xml,
+        application/EmergencyCallData.ProviderInfo+xml,
+        application/EmergencyCallData.ServiceInfo+xml,
+        application/ppsp-tracker+json, application/problem+json,
+        application/problem+xml, application/vnd.filmit.zfc,
+        application/vnd.hdt, application/vnd.mapbox-vector-tile,
+        application/vnd.ms-PrintDeviceCapabilities+xml,
+        application/vnd.ms-PrintSchemaTicket+xml,
+        application/vnd.ms-windows.nwprinting.oob, application/vnd.tml,
+        model/vnd.rosette.annotated-data-model, and video/H265.
+
+*   Updated to [Contributor Covenant 1.4][Code of Conduct].
+*   Shift the support code in this repository to be developed with Ruby 2.3.
+    This involves:
+
+    *   Adding `frozen_string_literal: true` to all Ruby files.
+    *   Applied some recommended readability and performance suggestions from
+        Rubocop. Ignored some style recommendations, too.
+    *   Replaced some cases of `foo.bar rescue nil` with `foo&.bar`.
+
 ## 3.2015.1120 / 2015-11-20
 
 *   Extracted from [ruby-mime-types][rmt].

data/Rakefile

@@ -1,4 +1,4 @@
-# -*- ruby encoding: utf-8 -*-
+# frozen_string_literal: true
 
 require 'rubygems'
 require 'hoe'

data/lib/mime-types-data.rb

@@ -1 +1,3 @@
+# frozen_string_literal: true
+
 require 'mime/types/data'

data/lib/mime/types/data.rb

@@ -1,7 +1,9 @@
+# frozen_string_literal: true
+
 module MIME
   class Types
     module Data
-      VERSION = '3.2015.1120'
+      VERSION = '3.2016.0221'
 
       # The path that will be used for loading the MIME::Types data. The
       # default location is __FILE__/../../../../data, which is where the data

metadata

@@ -1,14 +1,14 @@
 --- !ruby/object:Gem::Specification
 name: mime-types-data
 version: !ruby/object:Gem::Version
-  version: 3.2015.1120
+  version: 3.2016.0221
 platform: ruby
 authors:
 - Austin Ziegler
 autorequire: 
 bindir: bin
 cert_chain: []
-date: 2015-11-20 00:00:00.000000000 Z
+date: 2016-02-22 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: rdoc
@@ -195,7 +195,7 @@ required_rubygems_version: !ruby/object:Gem::Requirement
       version: '0'
 requirements: []
 rubyforge_project: 
-rubygems_version: 2.4.8
+rubygems_version: 2.5.1
 signing_key: 
 specification_version: 4
 summary: mime-types-data provides a registry for information about MIME media type