metanorma-ieee 1.2.10 → 1.2.12

data/lib/isodoc/ieee/word_authority.rb

@@ -138,8 +138,8 @@ module IsoDoc
       end
 
       def feedback_style(docxml)
-        docxml.at("//div[@class = 'boilerplate-feedback']")&.xpath("./div")
-          &.each_with_index do |div, i|
+        f = docxml.at("//div[@class = 'boilerplate-feedback']") or return
+        f.xpath("./div").each_with_index do |div, i|
           i.zero? or div.elements.first.previous = "<p>&#xa0;</p>"
           i == 4 and
             div.xpath(".//p[br]").each do |p|
@@ -182,6 +182,7 @@ module IsoDoc
         if f = docxml.at("//div[@class = 'abstract']")
           f.previous_element.remove
           abstract_cleanup1(f, dest)
+          abstract_header(dest)
           f.remove
         elsif f = docxml.at("//div[@type = 'scope']")
           abstract_cleanup1(f, dest)

data/lib/metanorma/ieee/boilerplate.adoc

@@ -25,49 +25,18 @@ Piscataway, NJ 08854, USA
 IEEE Standards
 documents are made available for use subject to important notices and legal
 disclaimers. These notices and disclaimers, or a reference to this page (https://standards.ieee.org/ipr/disclaimers.html[]),
-appear in all standards and may be found under the heading “Important Notices
-and Disclaimers Concerning IEEE Standards Documents.”
+appear in all IEEE standards and may be found under the heading "Important Notices
+and Disclaimers Concerning IEEE Standards Documents."
 
 ==== Notice and Disclaimer of Liability Concerning the Use of IEEE Standards Documents
 
-IEEE Standards documents are
-developed within the IEEE Societies and the Standards Coordinating Committees
-of the IEEE Standards Association (IEEE SA) Standards Board. IEEE develops its
-standards through an accredited consensus development process, which brings
-together volunteers representing varied viewpoints and interests to achieve the
-final product. IEEE Standards are documents developed by volunteers with
-scientific, academic, and industry-based expertise in technical working groups.
-Volunteers are not necessarily members of IEEE or IEEE SA, and participate
-without compensation from IEEE. While IEEE administers the process and
-establishes rules to promote fairness in the consensus development process,
-IEEE does not independently evaluate, test, or verify the accuracy of any of
-the information or the soundness of any judgments contained in its standards.
-
-IEEE makes no warranties or
-representations concerning its standards, and expressly disclaims all
-warranties, express or implied, concerning this standard, including but not
-limited to the warranties of merchantability, fitness for a particular purpose
-and non-infringement. In addition, IEEE
-does not warrant or represent that the use of the material contained in its
-standards is free from patent infringement. IEEE standards documents are
-supplied “AS IS” and “WITH ALL FAULTS.”
-
-Use of an IEEE standard is wholly
-voluntary. The existence of an IEEE Standard does not imply that there are no
-other ways to produce, test, measure, purchase, market, or provide other goods
-and services related to the scope of the IEEE standard. Furthermore, the
-viewpoint expressed at the time a standard is approved and issued is subject to
-change brought about through developments in the state of the art and comments
-received from users of the standard.
-
-In publishing and
-making its standards available, IEEE is not suggesting or rendering
-professional or other services for, or on behalf of, any person or entity, nor
-is IEEE undertaking to perform any duty owed by any other person or entity to
-another. Any person utilizing any IEEE Standards document, should rely upon his
-or her own independent judgment in the exercise of reasonable care in any given
-circumstances or, as appropriate, seek the advice of a competent professional
-in determining the appropriateness of a given IEEE standard.
+IEEE Standards documents are developed within IEEE Societies and subcommittees of IEEE Standards Association (IEEE SA) Board of Governors. IEEE develops its standards through an accredited consensus development process, which brings together volunteers representing varied viewpoints and interests to achieve the final product. IEEE standards are documents developed by volunteers with scientific, academic, and industry-based expertise in technical working groups. Volunteers involved in technical working groups are not necessarily members of IEEE or IEEE SA and participate without compensation from IEEE. While IEEE administers the process and establishes rules to promote fairness in the consensus development process, IEEE does not independently evaluate, test, or verify the accuracy of any of the information or the soundness of any judgments contained in its standards.
+
+IEEE makes no warranties or representations concerning its standards, and expressly disclaims all warranties, express or implied, concerning all standards, including but not limited to the warranties of merchantability, fitness for a particular purpose and non-infringement IEEE Standards documents do not guarantee safety, security, health, or environmental protection, or compliance with law, or guarantee against interference with or from other devices or networks. In addition, IEEE does not warrant or represent that the use of the material contained in its standards is free from patent infringement. IEEE Standards documents are supplied "AS IS" and "WITH ALL FAULTS."
+
+Use of an IEEE standard is wholly voluntary. The existence of an IEEE standard does not imply that there are no other ways to produce, test, measure, purchase, market, or provide other goods and services related to the scope of the IEEE standard. Furthermore, the viewpoint expressed at the time a standard is approved and issued is subject to change brought about through developments in the state of the art and comments received from users of the standard. 
+
+In publishing and making its standards available, IEEE is not suggesting or rendering professional or other services for, or on behalf of, any person or entity, nor is IEEE undertaking to perform any duty owed by any other person or entity to another. Any person utilizing any IEEE Standards document should rely upon their own independent judgment in the exercise of reasonable care in any given circumstances or, as appropriate, seek the advice of a competent professional in determining the appropriateness of a given IEEE standard.
 
 IN NO EVENT SHALL IEEE
 BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR
@@ -81,22 +50,16 @@ DAMAGE WAS FORESEEABLE.
 
 ==== Translations
 
-The IEEE consensus
-development process involves the review of documents in English only. In the
-event that an IEEE standard is translated, only the English version published
-by IEEE is the approved IEEE standard.
+The IEEE consensus balloting process involves the review of documents in English only. In the event that an IEEE standard is translated, only the English language version published by IEEE is the approved IEEE standard.
+
+==== Use by artificial intelligence systems
+
+In no event shall material in any IEEE Standards documents be used for the purpose of creating, training, enhancing, developing, maintaining, or contributing to any artificial intelligence systems without the express, written consent of IEEE SA in advance. “Artificial intelligence” refers to any software, application, or other system that uses artificial intelligence, machine learning, or similar technologies, to analyze, train, process, or generate content. Requests for consent can be submitted using the Contact Us form.
+
 
 ==== Official statements
 
-A statement, written
-or oral, that is not processed in accordance with the IEEE SA Standards Board
-Operations Manual shall not be considered or inferred to be the official
-position of IEEE or any of its committees and shall not be considered to be,
-nor be relied upon as, a formal position of IEEE. At lectures, symposia,
-seminars, or educational courses, an individual presenting information on IEEE
-standards shall make it clear that the presenter’s views should be considered
-the personal views of that individual rather than the formal position of IEEE,
-IEEE SA, the Standards Committee, or the Working Group.
+A statement, written or oral, that is not processed in accordance with the IEEE SA Standards Board Operations Manual is not, and shall not be considered or inferred to be, the official position of IEEE or any of its committees and shall not be considered to be, or be relied upon as, a formal position of IEEE or IEEE SA. At lectures, symposia, seminars, or educational courses, an individual presenting information on IEEE standards shall make it clear that the presenter’s views should be considered the personal views of that individual rather than the formal position of IEEE, IEEE SA, the Standards Committee, or the Working Group. Statements made by volunteers may not represent the formal position of their employer(s) or affiliation(s). News releases about IEEE standards issued by entities other than IEEE SA should be considered the view of the entity issuing the release rather than the formal position of IEEE or IEEE SA.
 
 ==== Comments on standards
 
@@ -108,18 +71,16 @@ Suggestions for changes in
 documents should be in the form of a proposed change of text, together with
 appropriate supporting comments. Since IEEE standards represent a consensus of
 concerned interests, it is important that any responses to comments and
-questions also receive the concurrence of a balance of interests. For this
-reason, IEEE and the members of its Societies and Standards Coordinating
-Committees are not able to provide an instant response to comments, or
-questions except in those cases where the matter has previously been addressed.
+questions also receive the concurrence of a balance of interests. For this reason, IEEE and the members of its Societies and subcommittees of the IEEE SA Board of Governors are not able to provide an instant response to comments or questions, except 
+in those cases where the matter has previously been addressed.
 For the same reason, IEEE does not respond to interpretation requests. Any
 person who would like to participate in evaluating comments or in revisions to
-an IEEE standard is welcome to join the relevant IEEE working group. You can
+an IEEE standard is welcome to join the relevant IEEE SA working group. You can
 indicate interest in a working group using the Interests tab in the Manage
 Profile & Interests area of the https://development.standards.ieee.org/myproject-web/public/view.html#landing[IEEE SA myProject system].footnote:[Available at: https://development.standards.ieee.org/myproject-web/public/view.html#landing[].]
 An IEEE Account is needed to access the application.
 
-Comments on standards should be submitted using the https://standards.ieee.org/content/ieee-standards/en/about/contact/index.html[Contact Us] form.footnote:[Available at: https://standards.ieee.org/content/ieee-standards/en/about/contact/index.html[].]
+Comments on standards should be submitted using the https://standards.ieee.org/about/contact/[Contact Us] form.footnote:[Available at: https://standards.ieee.org/about/contact/[].]
 
 ==== Laws and regulations
 
@@ -141,14 +102,7 @@ with applicable laws and regulations.
 
 ==== Copyrights
 
-IEEE draft and approved
-standards are copyrighted by IEEE under US and international copyright
-laws. They are made available by IEEE and are adopted for a wide variety of
-both public and private uses. These include both use, by reference, in laws and
-regulations, and use in private self-regulation, standardization, and the
-promotion of engineering practices and methods. By making these documents
-available for use and adoption by public authorities and private users, IEEE
-does not waive any rights in copyright to the documents.
+IEEE draft and approved standards are copyrighted by IEEE under U.S. and international copyright laws. They are made available by IEEE and are adopted for a wide variety of both public and private uses. These include both use by reference, in laws and regulations, and use in private self-regulation, standardization, and the promotion of engineering practices and methods. By making these documents available for use and adoption by public authorities and private users, neither IEEE nor its licensors waive any rights in copyright to the documents.
 
 ==== Photocopies
 
@@ -183,7 +137,7 @@ In
 order to determine whether a given document is the current edition and whether
 it has been amended through the issuance of amendments, corrigenda, or errata,
 visit https://ieeexplore.ieee.org/browse/standards/collection/ieee/[IEEE Xplore]
-or https://standards.ieee.org/content/ieee-standards/en/about/contact/index.html[contact IEEE].footnote:[Available at https://ieeexplore.ieee.org/browse/standards/collection/ieee[].]
+or https://standards.ieee.org/about/contact/[contact IEEE].footnote:[Available at https://ieeexplore.ieee.org/browse/standards/collection/ieee[].]
 For more information about the IEEE SA or IEEE’s standards development process,
 visit the IEEE SA Website.
 
@@ -198,7 +152,7 @@ Users are encouraged to periodically check for errata.
 
 ==== Patents
 
-IEEE Standards are developed in compliance with the https://standards.ieee.org/about/sasb/patcom/materials.html[IEEE SA Patent Policy].footnote:[Available at: https://standards.ieee.org/about/sasb/patcom/materials.html[].]
+IEEE standards are developed in compliance with the https://standards.ieee.org/about/sasb/patcom/materials.html[IEEE SA Patent Policy].footnote:[Available at: https://standards.ieee.org/about/sasb/patcom/materials.html[].]
 
 Attention is called to
 the possibility that implementation of this standard may require use of subject
@@ -227,17 +181,7 @@ Standards Association.
 
 ==== IMPORTANT NOTICE
 
-IEEE Standards do not
-guarantee or ensure safety, security, health, or environmental protection, or
-ensure against interference with or from other devices or networks. IEEE
-Standards development activities consider research and information presented to
-the standards development group in developing any safety recommendations. Other
-information about safety practices, changes in technology or technology implementation,
-or impact by peripheral systems also may be pertinent to safety considerations
-during implementation of the standard. Implementers and users of IEEE Standards
-documents are responsible for determining and complying with all appropriate
-safety, security, environmental, health, and interference protection practices
-and all applicable laws and regulations.
+Technologies, application of technologies, and recommended procedures in various industries evolve over time. The IEEE standards development process allows participants to review developments in industries, technologies, and practices, and to determine what, if any, updates should be made to the IEEE standard. During this evolution, the technologies and recommendations in IEEE standards may be implemented in ways not foreseen during the standard’s development. IEEE standards development activities consider research and information presented to the standards development group in developing any safety recommendations. Other information about safety practices, changes in technology or technology implementation, or impact by peripheral systems also may be pertinent to safety considerations during implementation of the standard. Implementers and users of IEEE Standards documents are responsible for determining and complying with all appropriate safety, security, environmental, health, data privacy, and interference protection practices and all applicable laws and regulations.
 
 [[boilerplate-participants]]
 === Participants

data/lib/metanorma/ieee/cleanup_ref.rb

@@ -23,9 +23,7 @@ module Metanorma
         @i = IsoDoc::IEEE::PresentationXMLConvert
           .new({ lang: @lang, script: @script, locale: @locale })
         @i.i18n_init(@lang, @script, @locale)
-        bib.sort do |a, b|
-          sort_biblio_key(a) <=> sort_biblio_key(b)
-        end
+        bib.sort { |a, b| sort_biblio_key(a) <=> sort_biblio_key(b) }
       end
 
       # Alphabetic by rendering: author surname or designation, followed by title
@@ -58,9 +56,17 @@ module Metanorma
 
       def normref_cleanup(xmldoc)
         super
+        normref_no_ordinals(xmldoc)
         normref_reorder(xmldoc)
       end
 
+      def normref_no_ordinals(xmldoc)
+        xmldoc.xpath("//references[@normative = 'true']/bibitem/" \
+                    "docidentifier[@type = 'metanorma']").each do |d|
+                      /^\[?\d+\]?$/.match?(d.text) and d.remove
+        end
+      end
+
       def normref_reorder(xmldoc)
         xmldoc.xpath("//references[@normative = 'true']").each do |r|
           biblio_reorder1(r)

data/lib/metanorma/ieee/isodoc.rng

@@ -17,7 +17,7 @@
   these elements; we just want one namespace for any child grammars
   of this.
 -->
-<!-- VERSION v1.3.2 -->
+<!-- VERSION v1.3.3 -->
 <grammar xmlns:a="http://relaxng.org/ns/compatibility/annotations/1.0" xmlns="http://relaxng.org/ns/structure/1.0" datatypeLibrary="http://www.w3.org/2001/XMLSchema-datatypes">
   <include href="reqt.rng"/>
   <include href="basicdoc.rng">
@@ -331,9 +331,9 @@
       <zeroOrMore>
         <ref name="table-note"/>
       </zeroOrMore>
-      <optional>
+      <zeroOrMore>
         <ref name="source"/>
-      </optional>
+      </zeroOrMore>
     </define>
     <define name="FigureAttr">
       <optional>
@@ -380,9 +380,9 @@
       <zeroOrMore>
         <ref name="note"/>
       </zeroOrMore>
-      <optional>
+      <zeroOrMore>
         <ref name="source"/>
-      </optional>
+      </zeroOrMore>
     </define>
     <define name="source">
       <element name="source">

data/lib/metanorma/ieee/version.rb

@@ -1,5 +1,5 @@
 module Metanorma
   module IEEE
-    VERSION = "1.2.10".freeze
+    VERSION = "1.2.12".freeze
   end
 end

data/metanorma-ieee.gemspec

@@ -23,9 +23,9 @@ Gem::Specification.new do |spec|
   spec.bindir        = "exe"
   spec.executables   = spec.files.grep(%r{^exe/}) { |f| File.basename(f) }
   spec.require_paths = ["lib"]
-  spec.required_ruby_version = Gem::Requirement.new(">= 2.7.0")
+  spec.required_ruby_version = Gem::Requirement.new(">= 3.1.0")
 
-  spec.add_dependency "metanorma-standoc", "~> 2.8.4"
+  spec.add_dependency "metanorma-standoc", "~> 2.9.0"
   spec.add_dependency "mnconvert", "~> 1.20"
   spec.add_dependency "pubid"
 

metadata

@@ -1,14 +1,14 @@
 --- !ruby/object:Gem::Specification
 name: metanorma-ieee
 version: !ruby/object:Gem::Version
-  version: 1.2.10
+  version: 1.2.12
 platform: ruby
 authors:
 - Ribose Inc.
 autorequire: 
 bindir: exe
 cert_chain: []
-date: 2024-06-17 00:00:00.000000000 Z
+date: 2024-07-22 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: metanorma-standoc
@@ -16,14 +16,14 @@ dependencies:
     requirements:
     - - "~>"
       - !ruby/object:Gem::Version
-        version: 2.8.4
+        version: 2.9.0
   type: :runtime
   prerelease: false
   version_requirements: !ruby/object:Gem::Requirement
     requirements:
     - - "~>"
       - !ruby/object:Gem::Version
-        version: 2.8.4
+        version: 2.9.0
 - !ruby/object:Gem::Dependency
   name: mnconvert
   requirement: !ruby/object:Gem::Requirement
@@ -333,7 +333,7 @@ required_ruby_version: !ruby/object:Gem::Requirement
   requirements:
   - - ">="
     - !ruby/object:Gem::Version
-      version: 2.7.0
+      version: 3.1.0
 required_rubygems_version: !ruby/object:Gem::Requirement
   requirements:
   - - ">="