- From: Shane McCarron <notifications@github.com>
- Date: Thu, 21 Apr 2016 16:04:59 -0700
- To: w3c/browser-payment-api <browser-payment-api@noreply.github.com>
- Cc:
- Message-ID: <w3c/browser-payment-api/issues/148/213152950@github.com>
Just for completeness... there are several other "registries" maintained by the W3C: - RDFa maintains an "initial context" in which CURIE prefixes are registered [1] - There is a registry of "rel" values maintained for HTML5 [2] - There is a collection of base "role" values for XHTML and HTML [3] - There was a naming "model" for XHTML family markup languages and DOCTYPEs that defined a more distributed model for registering document types [4] - The Role Attribute defines an extension mechanism that uses the web as registry, but requires dereferencable end-points [5] - JSON-LD defines an arbitrary extension mechanism via dereferencable contexts - again using the web as the registry [6] I am sure there are more. That was off the top of my head (and things I have worked on). [1] https://www.w3.org/2011/rdfa-context/rdfa-1.1 [2] https://wiki.whatwg.org/wiki/RelExtensions [3] https://www.w3.org/1999/xhtml/vocab [4] https://www.w3.org/TR/2008/REC-xhtml-modularization-20081008/conformance.html#s_conform_naming_rules [5] https://www.w3.org/TR/2013/REC-role-attribute-20130328/#extending-the-collection-of-roles [6] https://www.w3.org/TR/json-ld/#the-context --- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/w3c/browser-payment-api/issues/148#issuecomment-213152950
Received on Thursday, 21 April 2016 23:05:40 UTC