Is there any accepted standards for having Document Type Definition in JSON?

1 pointmofosyne3 comments

Is it just me or does JSON still lack a community accepted way of having a self validating document.

I've been paying attention to development of CBOR and I am quite interested in the CDDL standard that is being developed for validating CBOR data.

https://tools.ietf.org/html/draft-ietf-cbor-cddl-00#section-4.2

However it is not quite like XML, especially how XML DTD tag links to a document type definition file.

What would be the trajectory of JSON in regards to self validation and is it even needed?

----------

Side Note: I quite like the semantic tagging of CBOR and it would be great if JSON or anything that succeeds JSON would take semantic tagging into mind.

View on HN

<?xml version = "1.0" encoding = "UTF-8" standalone = "yes" ?> <!DOCTYPE address [ <!ELEMENT address (name,company,phone)> <!ELEMENT name (#PCDATA)> <!ELEMENT company (#PCDATA)> <!ELEMENT phone (#PCDATA)> ]> <address> <name>Tanmay Patil</name> <company>TutorialsPoint</company> <phone>(011) 123-4567</phone> </address>

<?xml version = "1.0" encoding = "UTF-8" standalone = "no" ?> <!DOCTYPE address SYSTEM "address.dtd"> <address> <name>Tanmay Patil</name> <company>TutorialsPoint</company> <phone>(011) 123-4567</phone> </address>