search

t3-innovation-network / OCF-Collab

0 stars 0 forks source link

XML vs JSON for data envelope #7

Closed neaf closed 4 years ago

neaf commented 4 years ago

Maybe there's an obvious answer but I have to ask:

We're using JSON for the registry files, search results API and potentially for the ODLR licenses.

Is there a reason why the competency framework metadata is an exception using XML? Could we use JSON?

stuartasutton commented 4 years ago

@neaf, we don't use XML at all. The entire focus of the T3 projects, of which OCF Collab is a part, is to support linked data on the open web. T3 stands for: (1) Linked Data, (2) AI and (3) Distributed Ledger Technology. The mapping output is massively linked data and thus RDF serialized as JSON-LD. There is some plain JSON data (e.g., the NodeDirectories) that uses plain JSON, but it is an exception. The competency frameworks are JSON-LD to support linking things like job postings, curriculum & training documents, to competencies over the open web.

neaf commented 4 years ago

Gosh, you're completely right. I have no idea why it stuck to my head and I didn't confirm before writing this issue.

Sorry for the trouble.

stuartasutton commented 4 years ago

No problem, my friend.