Why, you dont need schemata in JavaScript for you object
notation, the
JSON itself is both the definition of the shape and the shape
itself
(content).
Schemas are useful for tools, like data transformation tools.
More than this, a schema is a specification and a contract.
Indeed, people do need schemas to know what are they talking about !
The problem with relational databases was not that they HAD schemas --
as I think all
database modeling sooner or later gets one-- but:
1. Schema had to pre-exit the data. You couldn't get just start typing
data.
2. Schemas were not open.
3. Schemas could not be extracted (as a post processing step) from the
data
4. You could only have one schema for your data
5. Changing the data required changing the schema first.
Ok, now XML does have a schema language, and despite all the problems,
it's useful, and solves
some of the problems above.
Both RDF and JSON suffer from the fact that there is no general and
standard way to describe metadata in a contract
-- and that's why they'll probably NOT be used in places where a
contract between the communicating parties is needed:
e.g. financials, healthcare, military.
Those kind of users will continue to use XML, because of XSD.
But talking about the need for schemas (and/or XML vs. JSON): please
give a look at this:
http://schema.org/
Bing, Google and Yahoo! have come together to provide a shared
collection of schemas that webmasters can use.
There is RDF in there. There is JSON in there.
Where is xsd in there ? :-)
Best regards
Dana
_______________________________________________
[email protected]
http://x-query.com/mailman/listinfo/talk
