Added 2026/09/2026-09-16-bipro.md

2026/09/2026-09-16-bipro.md

@@ -0,0 +1,102 @@
+While GitHub did not find sufficient information to determine a valid anti-circumvention claim, we determined that this takedown notice contains other valid copyright claim(s).
+
+---
+
+**Are you the copyright holder or authorized to act on the copyright owner's behalf? If you are submitting this notice on behalf of a company, please be sure to use an email address on the company's domain. If you use a personal email address for a notice submitted on behalf of a company, we may not be able to process it.**
+
+Yes, I am authorized to act on the copyright owner's behalf.
+
+**Are you submitting a revised DMCA notice after GitHub Trust & Safety requested you make changes to your original notice?**
+
+No
+
+**Does your claim involve content on GitHub or npm.js?**
+
+GitHub
+
+**Please describe the nature of your copyright ownership or authorization to act on the owner's behalf.**
+
+I am [private] at BiPRO e.V. ([private]). I am submitting this notice on behalf of BiPRO e.V. and have been authorized to do so in connection with the copyrighted technical files described in this notice.  
+BiPRO e.V. develops and distributes technical standards for the German insurance and financial services industry, including XML Schema Definition (XSD) files forming part of its BiPRO release packages.
+
+**Please provide a detailed description of the original copyrighted work that has allegedly been infringed.**
+
+The copyrighted works concerned are XML Schema Definition (XSD) files forming part of BiPRO Release 2.6.0 and BiPRO Release 2.6.1.  
+These XSD files are technical components of the BiPRO standards and data model and are distributed by BiPRO e.V. to authorized users under the applicable BiPRO terms of use. They are not distributed by BiPRO e.V. under an open-source license permitting unrestricted public redistribution.
+The reported GitHub repository contains direct copies of these XSD files.  
+As part of our technical investigation, we compared a file contained in the reported GitHub repository with the corresponding original file from the official BiPRO release package using a SHA-256 cryptographic hash.  
+The file examined was:  
+bipro-prozesse-vertrag-kraftfahrt-2.6.1.xsd
+GitHub copy:   
+[private]  
+The SHA-256 hash of the GitHub-hosted file is identical to the SHA-256 hash of the corresponding file contained in the original BiPRO release package. The two files are therefore byte-for-byte identical.  
+Our investigation identified a total of 59 BiPRO-named XSD files within the affected directory.
+
+**If the original work referenced above is available online, please provide a URL.**
+
+The original XSD release files are proprietary technical files distributed by BiPRO e.V. through its controlled distribution channels and are not publicly published by BiPRO e.V. under an open-source license.  
+The applicable BiPRO terms governing the use of BiPRO standards and their associated technical files are available at:
+https://bipro.net/normnutzungsbedingungen/
+
+**We ask that a DMCA takedown notice list every specific file in the repository that is infringing, unless the entire contents of the repository are infringing on your copyright. Please clearly state that the entire repository is infringing, OR provide the specific files within the repository you would like removed.**
+
+**Based on the above, I confirm that:**
+
+Specific files within the repository are infringing
+
+**Identify only the specific file URLs within the repository that is infringing:**
+
+[private]
+
+**Do you claim to have any technological measures in place to control access to your copyrighted content? Please see our <a href="https://docs.github.com/articles/guide-to-submitting-a-dmca-takedown-notice#complaints-about-anti-circumvention-technology">Complaints about Anti-Circumvention Technology</a> if you are unsure.**
+
+Yes
+
+**What technological measures do you have in place and how do they effectively control access to your copyrighted material?**
+
+BiPRO e.V. makes the affected release artifacts available through an authenticated online environment. Access requires an authorized user account and login.
+However, we are not asserting an anti-circumvention claim in this notice. The original repository owner appears to have been an authorized user who was permitted to access and download the affected release artifacts. Our complaint concerns the subsequent unauthorized reproduction and public redistribution of those files.
+
+**How is the accused project designed to circumvent your technological protection measures?**
+
+It is not.
+We are not alleging that the reported GitHub project is designed to bypass or circumvent BiPRO's authentication or other technological protection measures.
+The affected files appear to have been obtained through authorized access. The basis of this notice is the subsequent unauthorized reproduction and public distribution of the identified copyrighted BiPRO XSD files through the reported GitHub repositories.
+
+**If you are reporting an allegedly infringing fork, please note that each fork is a distinct repository and <i>must be identified separately</i>. Please read more about <a href="https://docs.github.com/articles/dmca-takedown-policy#b-what-about-forks-or-whats-a-fork">forks.</a> As forks may often contain different material than in the parent repository, if you believe any of the repositories or files in the forks are infringing, please list each fork URL below:**
+
+https://github.com/highsource/soap-bipro/tree/master/securess-bipro/src/main/resources/xsd  
+https://github.com/hlapidez/soap-bipro/tree/master/securess-bipro/src/main/resources/xsd  
+https://github.com/housefrommars/soap-bipro/tree/master/securess-bipro/src/main/resources/xsd  
+https://github.com/lheister/soap-bipro/tree/master/securess-bipro/src/main/resources/xsd  
+https://github.com/janLlb/soap-bipro/tree/master/securess-bipro/src/main/resources/xsd
+
+**Based on the representative number of forks I have reviewed, I believe that all or most of the forks are infringing to the same extent as the parent repository.**
+
+**Is the work licensed under an open source license?**
+
+No
+
+**What would be the best solution for the alleged infringement?**
+
+Reported content must be removed
+
+**Do you have the alleged infringer’s contact information? If so, please provide it.**
+
+[private]
+
+**I have a good faith belief that use of the copyrighted materials described above on the infringing web pages is not authorized by the copyright owner, or its agent, or the law.**
+
+**I have taken <a href="https://www.lumendatabase.org/topics/22">fair use</a> into consideration.**
+
+**I swear, under penalty of perjury, that the information in this notification is accurate and that I am the copyright owner, or am authorized to act on behalf of the owner, of an exclusive right that is allegedly infringed.**
+
+**I have read and understand GitHub's <a href="https://docs.github.com/articles/guide-to-submitting-a-dmca-takedown-notice/">Guide to Submitting a DMCA Takedown Notice</a>.**
+
+**So that we can get back to you, please provide either your telephone number or physical address.**
+
+BIPRO e.V., [private]
+
+**Please type your full name for your signature.**
+
+[private]