Joe,
Precisely!
Now try and teach this to non-programmers involved in
designing business content transactions.
The examples show how programmers can use these
devices to make their lives easier and simplify coding.
And what is missing is the use case of creating libraries
of re-usable blocks of structures that can be included
into transactions, discovered, contexted and versioned.
OK - I'll not belabour the points again.
Anyway - there's a clear gap in understanding when we
are being asked to provide specific Registry functionality
to help manage namespaces - when:
a) the Registry can already manage extrinsic objects
b) the Registry cannot be expected to magically
program in fluent "namespace" so end users do
not have to grapple with all the syntax nuances.
c) This is what we are trying to avoid people doing IMHO:
<snip-from-the MSDN-training>
As another example, the following XML document shows
how to use the elements from the XML Schema definition
shown earlier in this column:
<d:student xmlns:d='http://www.develop.com/student'>
<d:id>3235329</d:id>
<d:name>Jeff Smith</d:name>
<d:language>C#</d:language>
<d:rating>9.5</d:rating>
</d:student>
</snip-from-the MSDN-training>
Ho hum.
DW.
===================================================================
Message text written by Chiusano Joseph
>
Here's a great Web page that explains namespaces pretty well (IMO):
http://msdn.microsoft.com/webservices/default.aspx?pull=/library/en-us/dnxm
l/html/xml_namespaces.asp
- Joe
<
----------------------------------------------------------------
To subscribe or unsubscribe from this elist use the subscription
manager: <http://lists.oasis-open.org/ob/adm.pl>
