[
Lists Home |
Date Index |
Thread Index
]
My thoughts on various sections:
:::4. An interpretation of XML and namespaces:::
This section doesn't seem to give an interpretation of namespaces especially
after previous section leaves the reader hanging but instead seems to dwell on
the philosphical question of what should be done about elements with no
namespace URI.I think that entire section is an unecessary digression that
disrupts the flow of the article.
:::5. An interpretation of schemas:::
I like the way this section describes the relationship (or lack thereof)
between namespaces and schemas.
:::8. A proposal for an answer to the riddle : the Namespace Description
Language:::
You state
"What should I obtain when resolving a namespace name ? A Namespace
Description Language document. This is NOT a collection of names, but a
program can build a collection of names from it.
Apart from the different names appearing in the namespace, what information
could the NDL document provide ? Well, I'm not sure yet, but I think that for
each name which corresponds to an element name, there should be the definition
of the correponding element type URI. This URI would enable us to fetch a
meta-data RD and get some associated resources, like a human-readable
documentation of the general meaning (e.g. out of any pattern) of the tag."
This reads like a reinvention of RDDL to me. The interesting problems that
RDDL doesn't solve are
(a.) Where to place RDDL files for XML documents containing elements from
multiple namespaces such as MSFT's annotated XSD schemas for creating XML
views of relational data that typically contain elements from 2 or 3
namespaces (as a practical example)
and similarly
(b.) Where to place RDDL files for namespaces that do not have a resolvable
namespace URI.
Your description of a NDL doesn't seem to address these problems.
--
THINGS TO DO IF I BECOME AN EVIL OVERLORD #229
If I have several diabolical schemes to destroy the hero, I will set
all of them in motion at once rather than wait for them to fail and
launch them successively.
----- Original Message -----
From: "Nicolas Lehuen" <nicolas.lehuen@ubicco.com>
To: "Jonathan Borden" <jborden@mediaone.net>; "Leigh Dodds"
<ldodds@ingenta.com>; <xml-dev@lists.xml.org>; "Joe English"
<jenglish@flightlab.com>
Sent: Saturday, January 19, 2002 9:13 AM
Subject: [xml-dev] Re: What a namespace is.
> I've updated the article I wrote on my Web site :
>
> http://nicolas.lehuen.com/Articles/Programming/Ideas/fog0000000033.html
>
> It is not authoritative in anyway. I used this article to try to sum up the
> series of assumptions and ideas I have about XML, namespaces, schemas and
> our needs for a meta-data resource directory system. I hope this will help
> us to understand each other. I'm open to any remarks of sarcasms (though
> I'd prefer the sarcasms to be sent privately than on the list ;). My deepest
> wish is to have a constructive debate about those issues, and I will welcome
> any remark that can help me improve the article, on both technical and
> English aspects.
>
> I'll read Jonathan's presentations and texts from now on.
>
> Best regards,
> Nicolas
>
>
>
> -----------------------------------------------------------------
> The xml-dev list is sponsored by XML.org <http://www.xml.org>, an
> initiative of OASIS <http://www.oasis-open.org>
>
> The list archives are at http://lists.xml.org/archives/xml-dev/
>
> To subscribe or unsubscribe from this list use the subscription
> manager: <http://lists.xml.org/ob/adm.pl>
_________________________________________________________
Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.com
|
