<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">Do we already have an inventorisation of what attributes and object should be included into the model? There have been many discussions, but I am losing grip. Maybe a Wiki? Where people can suggest needed attr next to what already is available on <a href="http://axschema.org">axschema.org</a><div><br></div><div>And what do we do wit axschema? There is the schema (formal) and the implementation (JSON, something else). Shouldn't we split these discussions?</div><div><br></div><div><div>Cheers,</div><div><br></div><div>Chris</div><div><br></div><div><br><div><div>Op 15 dec 2009, om 15:46 heeft Santosh Rajan het volgende geschreven:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div><br></div>response inline<br><br><div class="gmail_quote">On Tue, Dec 15, 2009 at 3:31 PM, Joseph Anthony Pasquale Holsten <span dir="ltr"><<a href="mailto:joseph@josephholsten.com">joseph@josephholsten.com</a>></span> wrote<div>
<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<br>
To your original point, I'm really struggling to understand how to get namespaces into JSON, and everything I've found is either a terrible reincarnation of the HTML/RDFa/QNAME headache, or a one-to-one mapping with RDF or XML. Makes me want to research the TLS+RDF and SAML assertion tech, and I'm in no way comforted by that.<br>
</blockquote><div><br></div><div>Why do you need namespace in JSON? I am quite convinced we can get around this problem with JSON. I would like to know if i missed something here (looks likely).</div><div><br></div><div><br>
</div></div>-- <br><a href="http://hi.im/santosh">http://hi.im/santosh</a><br><br><br>
</blockquote></div><br></div></div></body></html>