Cart
[Home] [By Thread] [By Date] [Recent Entries]
Dare Obasanjo wrote: > ISSUE 1: Namespace URIs should not be HTTP URLs and where possible this shoul > be deprecated. [...] > ISSUE 2: There should be a way to discover information about a Namespace URI > in both human readable and machine comprehendable form. [...] > I'd like to _at_the_very_least_ be > able to a.) discover the semantics of the elements and attributes in the > document by looking up the namespace URI and locating a human readable > document and b.) obtain validation information for the namespace (e.g. the > XSLT schema or DTD for the XSLT namespace) IF the creator of the namespace > (right phrase?) has deigned to make such information available. RDDL is designed to solve *exactly* issue (2). However it can only really work reliably if the namespace creator uses a resolvable URI (i.e., http://*) to identify it, contrary to issue 1. > From where I > sit, RDDL does not give me this although RDDL is the "Worse is better" > solution. RDDL gives you exactly this: a human-readable XHTML document with computer-readable links to computer-processable information (schemas, stylesheets, etc.) relevant to the namespace. What's missing from where you sit? Is it issue 1 (don't use HTTP URIs for namespace names)? --Joe English jenglish@f...
|
