Reading the #JsonLD framing document and just…

It is not weakening my instinct that what they really want is to be working in #XML—with #XPath and #XSLT and #XSD—and not in JSON.

Earlier today I gave an impromptu demo of how #XSD works to a coworker and you'd swear I just revealed Santa was real.

There is a simply enormous number of Devs whose only knowledge of #XML tech is second hand retellings of stories about how "Draconian" error handling was oh so terrible, ignoring that we don't use notepad anymore and have modern IDEs that sort everything.

I wonder how to fix this. I really need to get XSD working in xRust next I think, possibly before DTDs.

I'm starting to scrap the bottom of the barrel when it comes to #XML parser conformance tests. Almost everything that remains require me to:

1- Support external DTDs
2- Validate DTDs

So the questions to consider:

1- Instead of validating DTDs, should I look at something like #XSD or #RelaxNG instead?

2- Is it acceptable practice to bundle popular DTDs like #XHTML with the project so we can minimize the network calls? I don't think that'd be a bad idea, so long as licensing allows it.

goetas-webservices/xsd2php 0.4.7 has been just released!
More info on https://github.com/goetas-webservices/xsd2php/releases/tag/0.4.7
#xml #xsd #api

A gift for those with too little schema definition in their life. #xml #xsd #software #barf https://release.niem.gov/niem/niem-core/4.0/niem-core.xsd