#ditaxml — Public Fediverse posts
Live and recent posts from across the Fediverse tagged #ditaxml, aggregated by home.social.
-
"The future of enterprise technical documentation will not belong to organizations that merely generate more content with AI. It will belong to organizations that build semantically governed, operationally validated, and explainable knowledge ecosystems around AI generation.
Large language models are remarkable language-generation systems, but they remain fundamentally probabilistic, and no amount of vector-based probabilistic augmentation, recursive prompt gymnastics, or trillions of additional parameters magically transforms probabilistic token prediction into deterministic operational intelligence — regardless of what the AI snake-oil salesmen on LinkedIn insist between inspirational rocket-ship emojis. LLMs predict statistically likely outputs. They do not inherently understand operational correctness, governance policy, procedural safety, rollback integrity, regulatory compliance, or whether the “helpful” configuration change they just suggested is going to quietly detonate a production Kubernetes cluster at 2:13 a.m. while everyone is asleep and the on-call engineer is reconsidering their career choices.
That is not a moral failure of AI. It is simply the architectural reality of probabilistic systems pretending to perform deterministic operational reasoning often enough to make people dangerously optimistic.
This is precisely why deterministic models and governance matter.
Structured content, semantic markup, metadata governance, provenance tracking, DOM Graph RAG, iiRDS frameworks, knowledge graphs, RDF and OWL ontologies, context graphs, deterministic inference engines, orchestration platforms, Docs-as-Tests automation, and runtime observability together create something fundamentally different from prompt engineering. They create governed operational ecosystems capable of supporting trustworthy enterprise AI at scale."
#AI #GenerativeAI #DocsAsTests #LLMs #AgenticAI #DITAXML #AIAgents #TechnicalWriting #SoftwareDocumentation
-
"The future of enterprise technical documentation will not belong to organizations that merely generate more content with AI. It will belong to organizations that build semantically governed, operationally validated, and explainable knowledge ecosystems around AI generation.
Large language models are remarkable language-generation systems, but they remain fundamentally probabilistic, and no amount of vector-based probabilistic augmentation, recursive prompt gymnastics, or trillions of additional parameters magically transforms probabilistic token prediction into deterministic operational intelligence — regardless of what the AI snake-oil salesmen on LinkedIn insist between inspirational rocket-ship emojis. LLMs predict statistically likely outputs. They do not inherently understand operational correctness, governance policy, procedural safety, rollback integrity, regulatory compliance, or whether the “helpful” configuration change they just suggested is going to quietly detonate a production Kubernetes cluster at 2:13 a.m. while everyone is asleep and the on-call engineer is reconsidering their career choices.
That is not a moral failure of AI. It is simply the architectural reality of probabilistic systems pretending to perform deterministic operational reasoning often enough to make people dangerously optimistic.
This is precisely why deterministic models and governance matter.
Structured content, semantic markup, metadata governance, provenance tracking, DOM Graph RAG, iiRDS frameworks, knowledge graphs, RDF and OWL ontologies, context graphs, deterministic inference engines, orchestration platforms, Docs-as-Tests automation, and runtime observability together create something fundamentally different from prompt engineering. They create governed operational ecosystems capable of supporting trustworthy enterprise AI at scale."
#AI #GenerativeAI #DocsAsTests #LLMs #AgenticAI #DITAXML #AIAgents #TechnicalWriting #SoftwareDocumentation
-
"The future of enterprise technical documentation will not belong to organizations that merely generate more content with AI. It will belong to organizations that build semantically governed, operationally validated, and explainable knowledge ecosystems around AI generation.
Large language models are remarkable language-generation systems, but they remain fundamentally probabilistic, and no amount of vector-based probabilistic augmentation, recursive prompt gymnastics, or trillions of additional parameters magically transforms probabilistic token prediction into deterministic operational intelligence — regardless of what the AI snake-oil salesmen on LinkedIn insist between inspirational rocket-ship emojis. LLMs predict statistically likely outputs. They do not inherently understand operational correctness, governance policy, procedural safety, rollback integrity, regulatory compliance, or whether the “helpful” configuration change they just suggested is going to quietly detonate a production Kubernetes cluster at 2:13 a.m. while everyone is asleep and the on-call engineer is reconsidering their career choices.
That is not a moral failure of AI. It is simply the architectural reality of probabilistic systems pretending to perform deterministic operational reasoning often enough to make people dangerously optimistic.
This is precisely why deterministic models and governance matter.
Structured content, semantic markup, metadata governance, provenance tracking, DOM Graph RAG, iiRDS frameworks, knowledge graphs, RDF and OWL ontologies, context graphs, deterministic inference engines, orchestration platforms, Docs-as-Tests automation, and runtime observability together create something fundamentally different from prompt engineering. They create governed operational ecosystems capable of supporting trustworthy enterprise AI at scale."
#AI #GenerativeAI #DocsAsTests #LLMs #AgenticAI #DITAXML #AIAgents #TechnicalWriting #SoftwareDocumentation
-
"The future of enterprise technical documentation will not belong to organizations that merely generate more content with AI. It will belong to organizations that build semantically governed, operationally validated, and explainable knowledge ecosystems around AI generation.
Large language models are remarkable language-generation systems, but they remain fundamentally probabilistic, and no amount of vector-based probabilistic augmentation, recursive prompt gymnastics, or trillions of additional parameters magically transforms probabilistic token prediction into deterministic operational intelligence — regardless of what the AI snake-oil salesmen on LinkedIn insist between inspirational rocket-ship emojis. LLMs predict statistically likely outputs. They do not inherently understand operational correctness, governance policy, procedural safety, rollback integrity, regulatory compliance, or whether the “helpful” configuration change they just suggested is going to quietly detonate a production Kubernetes cluster at 2:13 a.m. while everyone is asleep and the on-call engineer is reconsidering their career choices.
That is not a moral failure of AI. It is simply the architectural reality of probabilistic systems pretending to perform deterministic operational reasoning often enough to make people dangerously optimistic.
This is precisely why deterministic models and governance matter.
Structured content, semantic markup, metadata governance, provenance tracking, DOM Graph RAG, iiRDS frameworks, knowledge graphs, RDF and OWL ontologies, context graphs, deterministic inference engines, orchestration platforms, Docs-as-Tests automation, and runtime observability together create something fundamentally different from prompt engineering. They create governed operational ecosystems capable of supporting trustworthy enterprise AI at scale."
#AI #GenerativeAI #DocsAsTests #LLMs #AgenticAI #DITAXML #AIAgents #TechnicalWriting #SoftwareDocumentation
-
"The future of enterprise technical documentation will not belong to organizations that merely generate more content with AI. It will belong to organizations that build semantically governed, operationally validated, and explainable knowledge ecosystems around AI generation.
Large language models are remarkable language-generation systems, but they remain fundamentally probabilistic, and no amount of vector-based probabilistic augmentation, recursive prompt gymnastics, or trillions of additional parameters magically transforms probabilistic token prediction into deterministic operational intelligence — regardless of what the AI snake-oil salesmen on LinkedIn insist between inspirational rocket-ship emojis. LLMs predict statistically likely outputs. They do not inherently understand operational correctness, governance policy, procedural safety, rollback integrity, regulatory compliance, or whether the “helpful” configuration change they just suggested is going to quietly detonate a production Kubernetes cluster at 2:13 a.m. while everyone is asleep and the on-call engineer is reconsidering their career choices.
That is not a moral failure of AI. It is simply the architectural reality of probabilistic systems pretending to perform deterministic operational reasoning often enough to make people dangerously optimistic.
This is precisely why deterministic models and governance matter.
Structured content, semantic markup, metadata governance, provenance tracking, DOM Graph RAG, iiRDS frameworks, knowledge graphs, RDF and OWL ontologies, context graphs, deterministic inference engines, orchestration platforms, Docs-as-Tests automation, and runtime observability together create something fundamentally different from prompt engineering. They create governed operational ecosystems capable of supporting trustworthy enterprise AI at scale."
#AI #GenerativeAI #DocsAsTests #LLMs #AgenticAI #DITAXML #AIAgents #TechnicalWriting #SoftwareDocumentation
-
Seems legit... I've started to use it and it has been a great help when browsing a huge Git repository Vs doing the same over OxigenXML.
"DitaCraft is a lightweight extension that brings DITA support directly into VS Code, one of the most popular code editors. It provides:
- Syntax highlighting for .dita, .ditamap, and .bookmap files.
Real-time validation against DITA 1.3 standards.
- Seamless integration with DITA-OT for multi-format publishing (HTML5, PDF, EPUB, and more).
- Smart navigation, live preview, and 21 code snippets to generate bookmap, ditamap,topic templates.Whether you’re a technical writer, developer, or student, DitaCraft helps you focus on learning DITA — without the complexity.
(...)
Who Is DitaCraft For?- Beginners who want to learn DITA without the complexity of professional tools.
- Developers who need a lightweight DITA editor integrated into VS Code.
- Students exploring structured authoring and technical documentation.
- Technical writers who want a free, open-source alternative for quick edits and validation.
The Future of DitaCraft
DitaCraft is an ongoing project, and I welcome contributions from the community! Whether you’re a DITA expert or a beginner, your feedback and ideas can help shape the future of this tool.
Try DitaCraft today and simplify your DITA journey! 🔗 Install DitaCraft from the VS Code Marketplace"
#DITA #DITAXML #XML #VSCode #VisualStudioCode #StructuredWriting #TechnicalWriting #DitaCraft
-
Yep, DITA XML is still rocking in the technical communication world and technical writers need to have at least some familiarity with the topic.
https://learningdita.com/pluginfile.php/1/tool_certificate/issues/1762964073/6088999983MC.pdf
#DITA #DITAXML #TechnicalWriting #TechnicalCommunication #StructuredWriting
-
#TechnicalWriting #DITA #XML #DITAXML #Documentation #InformationArchitecture #StructuredAuthoring: "DITA is defined in its specification as “an XML-based architecture for authoring, producing, and delivering topic-oriented, information-typed content that can be reused and single-sourced in a variety of ways”. Originally developed by IBM in the early 2000s, DITA stands for Darwin Information Typing Architecture. “Darwin” refers to the naturalist Charles Darwin and his theory of evolution, reflecting DITA’s principles of specialization, inheritance, and adaptation.
DITA topics are standalone, context-free blocks of content, with content types kept clearly separate. There are three main topic types in DITA, all of which are inherited from the base topic type <topic>:
<concept>: background information that users must know before using the product
<task>: step-by-step instructions that users need to perform a task
<reference>: product specifications, commands, or other reference material
You create a document by selecting which existing topics should be reused and referencing them in what’s called a DITA map (similar to a table of contents).
Being an open standard, DITA has no proprietary restrictions. But while you’re not forced to buy a specific tool to use it, commercial XML editors have many features, such as visual editing and validation, that make writing DITA content much easier."
https://mastertcloc.unistra.fr/2024/04/26/dita-xml-documentation-reasons/
-
DITA-OT 4.2.2 has been released. #ditaOt #ditaxml
https://github.com/dita-ot/dita-ot/releases/tag/4.2.2 -
DITA-OT 4.2.1 has been released
✨ For details on what’s new, see the Release Notes at dita-ot.org/4.2/release-notes/
-
We released DITA-OT 4.2 today. See https://www.dita-ot.org/4.2/release-notes/ for details. #ditaOt #ditaXml
-
Hi there!
We're looking to bring a new Technical Specialist on board at @Scriptorium to assist with #DITAxml development work. This is a full time remote (US) job.
If you have experience with or interest in making DTD updates, developing DITA OT plugins for publishing, CCMS configuration, or scripting to support structured authoring/management/publishing needs, we'd love to hear from you!
More detail here: https://www.scriptorium.com/careers/
-
We released DITA-OT 4.1.2 the other day. See https://www.dita-ot.org/4.1/release-notes/#v4.1.2 for details.
I fixed a bug that was likely already in 1.0, so it may have been an 18 year old bug 😳
-
DITA-OT 4.1 has been released. See https://www.dita-ot.org/4.1/release-notes/ for more details. #ditaOt #ditaXml
-
Off to Las Vegas for the Adobe EXPERIENCE MAKERS Content Management Forum. See you there? I’ll have a few copies of our Content Transformation book to hand out. @Scriptorium #ContentManagement #digitaltransformation #DITAxml
-
Seriously, #Adobe? A 33% increase in the subscription price for #FrameMaker? Most of my clients have moved to #OxygenXML for #DITAxml authoring, so this may be the time to finally cut my ties. I’ve been a FrameMaker user/developer for over 30 years. A bit bittersweet. Looks like I have a month to make some final plugin updates. Will see how that goes. :-(