#openstandard — Public Fediverse posts

If you are curious about (nearly) everything we did the past months at the GCVE.eu initiative:

https://gcve.eu/2026/08/13/gcve-recent-activities-standards-software-and-a-growing-gna-community/

We published a recap blog post.

#gcve #cve #vulnerability #vulnerabilitymanagement #cra #cybersecurity #openstandard #opensource

Sightings have long been a major topic of discussion in the CTI community, particularly in the field of vulnerability management. We have now published a GCVE BCP to standardise the format that has been implemented, tested and used operationally in Vulnerability-Lookup for some time.

Thanks to everyone (Cédric Bonhomme, Éireann Leverett, Andras Iklody, Sami Mokaddem and many more) who participated in discussions and worked on the implementation details of sightings over the past several years. These efforts had a strong focus on practical implementation, while BCP-12 specifically addresses sightings in the context of vulnerability management.

BCP-12 is still a draft open for review, but it already provides a strong foundation for existing implementations.

https://gcve.eu/2026/08/01/gcve-bcp-12-a-standard-sighting-format-for-vulnerabilities/

#cve #cra #gcve #vulnerabilitymanagement #cybersecurity #openstandard

Frustrated with Samsung Notes locking my notes into their ecosystem, your data isn't really yours. No good alternative existed.
So I started ONF, an open vendor-neutral format for handwritten digital notes. Standard ZIP under the hood, fully open spec, designed for the long term.
Early draft + C++ reference implementation on GitHub. Looking for experienced people to help get it right:
https://github.com/Powerbambus/open-notes-format
#opensource #foss #openstandard #handwriting #opendocument

I noticed today that #MSOffice Online now has an option to save files as #odt instead of #pttx. It made me wonder, can we change our files at work to open formats and still have the MS using colleagues use them properly? That would be a great step :awesome:!

Sadly, it seems not. Saving in MS Office breaks a lot of design in the files. Opening the pttx in @libreoffice works perfectly fine. Saving from there as odt does as well. But then MS Office considers the working odt file "corrupt", disallowing online view.

Seems like MS Office their implementation of open document standards are still lacking, so for anything requiring collaboration with MS Office users we're still stuck in proprietary formats. Sad :blobcatverysad:.

#Microsoft #proprietary #openstandard #openstandaarden #opensource #LibreOffice #sovereignity #digitaleautonomie #digitalesoevereiniteit

I still don’t understand standards committees composed of people who have never implemented software. They design a standard without ever confronting the realities of implementation, then wonder why no one adopts it.

#openstandard #standard

🔒 New release: “Internet.nl now tests on the latest @NCSC_NL TLS guidelines”
➡️ https://en.internet.nl/article/release-1.11/
❓ Are your web and mailservers ready for future-proof TLS?
🌐 Keeping your configuration up-to-date makes the internet more secure.
🚀 Have fun testing and improving if needed!

#TLS #security #openstandard

This week I ended up the 5 article series about #SWHID, the intrinsic, persistent and standardised software artifacts identifier.

Check them out:

1. What is the Best Way to Identify Software? Introducing SWHID https://toscalix.com/2026/03/10/what-is-the-best-way-to-identify-software-introducing-swhid/

2. Description of SWHID: Syntax. https://toscalix.com/2026/03/17/description-of-swhid-syntax/

3. SWHID Is An #OpenStandard, Governed Under #OpenGovernance. https://toscalix.com/2026/03/24/swhid-is-an-open-standard-governed-under-open-governance/

4. SWHID and #pURL. https://toscalix.com/2026/03/31/swhid-and-purl/

5. SWHID in Practice: https://toscalix.com/2026/04/07/swhid-in-practice-sbom-verification-cra-compliance-and-traceability-use-cases/

Once again, an important standard is behind a paywall: prEN 4709-02 from CENELEC. It matters for both security and safety, and could benefit everyone, yet access remains restricted.

@EUCommission do you plan to force CENELEC to publish and release publicly the standards?

#cenelec #paywall #drone #standard #openstandard

I just published The Open Contributions Descriptor format as an IETF Internet-Draft.

#opensource #opendata #openstandard

https://datatracker.ietf.org/doc/draft-dulaunoy-open-contributions-descriptor/

GitAgent – An open standard that turns any Git repo into an AI agent

https://www.gitagent.sh/

#HackerNews #GitAgent #AI #GitRepo #OpenStandard #TechnologyInnovation

TopoBathy Open Standard - Bathymetric Attributed Grid (BAG) [OGC]
--
https://www.ogc.org/standards/bag/ <-- shared open OGC standard 🔗
--
https://www.hydroffice.org/bag/main <-- shared example of #opensource software to interact with the #opendata BAG format 🔗
--
[this post should not be considered an endorsement of a particular product and/or approach]
#GIS #spatial #mapping #opendata #opensource #standard #openstandard #BathymetricAttributedGrid #BAG #format #grid #raster #offshore #OGC #hydrography #submarine #survey #marine #ocean #bottom #hydrospatial #FAIR #openspecification #specification #bathymetry #depth #seafloor #vertical #datum #metadata #hydrographic
#OpenGeospatialConsortium

📢 Coliberator FORUM - 21 martie 2026, ora 10:00
"Formate #libere și standarde #deschise" 🎯
CITT Nortek 🤓, Bălți, Republica Moldova

Este o oportunitate perfectă să discutăm și despre "#NGIZero Commons Fund: #beneficii și #oportunități" la acest eveniment! 🤩
Află mai mult și înscrie-te pentru a participa 👉 https://coliberator.org/2026/forum/

#opensource #openhardware #FOSS #openformat #openstandard

Open Contributions Descriptor — or how to map your contribution in open source, open data, and open standards

🔗 Blog post https://www.foo.be/2026/03/open-contributions-descriptor

#opensource #opendata #openstandard

The Open Contributions Descriptor (OCD) is an open, machine-readable JSON format that allows an organization to publish a structured description of its participation in the open ecosystem.

It's still a bit in flux but the goal of OCD is to make organizational openness discoverable, interoperable, and automatable.

#opensource #openstandard #oss

🔗 Format https://github.com/ossbase-org/Open-Contributions-Descriptor/
🔗 Sample OCD at MISP https://misp-project.org/.well-known/open-contributions.json
🔗 Format discussion https://discourse.ossbase.org/t/open-contributions-descriptor/1024

Have you ever tried doing digital forensics using an SBOM or even just gathering evidence for a technical investigation from one?

No file hashes, a single cryptographic signature covering an arbitrary set of files, and often missing full paths or permissions.

Many SBOM standards need a serious revamp if they are to support DFIR use cases

#dfir #sbom #openstandard

The GCVE.eu initiative will take part in hackathon.lu (14–15 April, Luxembourg), alongside core developers of GCVE-related projects. See you there to build, experiment, and collaborate!

#gcve #cve #opensource #openstandard #hackathon

🔗 https://hackathon.lu

@gcve
@circl

Following a great question from CERT.PL about GCVE KEV assertion format and especially about the confidence level for an evidence of a vulnerability assertion.

We made a first table of confidence level for the evidence in the KEV record format.

#kev #gcve #format #vulnerability #openstandard

🔗 Discussions / Proposal https://discourse.ossbase.org/t/kev-known-exploited-vulnerabilities-potential-format-bcp-07/744/36?u=adulau

🔗 GCVE BCP-07 https://gcve.eu/bcp/gcve-bcp-07/

@gcve

Huge thanks to Cédric @cedric and Jerry Gamblin @jgamblin and the #FOSDEM participants for the great constructive feedback on the new GCVE-BCP-08.

There are still some open questions concerning the existing fields from the CVE program (CNA) and how we would include those in the directory file.

Feel free to comment on update on the discourse below.

#gcve #cve #openstandard #vulnerabilitymanagement #opensource

🔗 Updated early draft version available https://discourse.ossbase.org/t/gcve-bcp-08-gcve-gna-directory-file-draft/754/5?u=adulau