[
Lists Home |
Date Index |
Thread Index
]
> Thousands of developers using Microsoft technologies benefit from viewing XML as strongly typed
> data. Users of the .NET Framework DataSet, ASP.NET web services and SQLXML all utilize XML
> as strongly typed data. However these people are rarely markup weenies thus you won't find them on
> XML-DEV arguing the finer points of the PSVI.
>
> The question isn't whether there are scenarios where strongly typed uses of XML exist or are
beneficial
> because they do and are but whether users of XML in loosely typed or untyped scenarios should be
> penalized for this.
Response from a developer:
I use "typed" processing all the time, but I would like to keep it modular.
No data types in XML, just don't see the necessity.
With most networked apps you can agree on the exact semantics of the content - and describe
it separately in whatever way suits the parties involved best. There is always something
a Schema language cannot describe, and conceivable there can always be a context where a
document's schema should be different or does not matter.
For general interoperability (if that can be achieved) you probably need
Artificial Intelligence, and then it would not even matter if you use XML or not.
Karl
|
