PulseAugur
EN
LIVE 15:54:06

Author criticizes slow pace of RDF and SHACL standards development

The author argues that standards work, particularly for technologies like RDF and SHACL, is often too slow due to lengthy processes involving mailing lists, issue threads, and meetings. They emphasize the need for these standards to encompass a broader range of current use cases, rather than being limited by what they handle well today. A specific example cited is the difficulty of discussing SHACL UI on a smartwatch, highlighting how such cases can be easily excluded by default. AI

RANK_REASON The item is a personal blog post discussing the pace and scope of standards development for RDF and SHACL.

Read on Mastodon — sigmoid.social →

AI-generated summary · Google Gemini · from 1 sources. How we write summaries →

Author criticizes slow pace of RDF and SHACL standards development

COVERAGE [1]

  1. Mastodon — sigmoid.social TIER_1 English(EN) · [email protected] ·

    Standards work is slow: mailing lists, issue threads, meetings where one property name takes three sessions. My latest post explains why I still spend so much t

    Standards work is slow: mailing lists, issue threads, meetings where one property name takes three sessions. My latest post explains why I still spend so much time on it. I want RDF to cover the range of use cases people actually show up with. Not just the range it handles well t…