Lists Home |
Date Index |
Hmm. That may be a worth a try. I'll have to give it a bit of thought.
I'd still need the import_model element and aliasing because the
namespace mechanism doesn't instruct a processor to import the model??
But having both seems to be a bit redundant...
Thank you for your suggestion!
Dare Obasanjo wrote:
>> Neither method is exactly XML-happy. You expect the attribute value to
>> be a literal value with no hidden meaning for a processor to detect, as
>> would be necessary with the dot notation.
> This is the ideal case but isn't true in most XML applications including W3C technologies such as XSLT,W3C XML Schema and WSDL. This is due to the practice of embedding qualified names (QNames) in attribute values. In your example I would do
> <model xmlns:example="http://www.example.com/sample_model.xml <http://www.example.com/sample_model.xml> " >
> <import_model name="example"
> uri="http://www.example.com/sample_model.xml <http://www.example.com/sample_model.xml> " />
> <variable name="A" units="example:meter_per_cm2"/>
> PS: A good overview of XML namespaces is provided at http://www.jclark.com/xml/xmlns.htm
> PPS: A more in depth overview is available at http://msdn.microsoft.com/library/en-us/dnexxml/html/xml05202002.asp