OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index]
RE: [xml-dev] Static resolution of names is preferred over dynamicresolution of names

Thanks for following up.

I personally do not face that sort of problems and I still have use for XML in my projects for the last 15 years or so.

One of the great strength of xml is the availability of tools and I personally find it "easy". This is also why I prefer rdf/xml as I can do a lot using the same tools and most of my (sport or video) data comes in xml. So xsl tranform is handy, which I also use for gathering linked data from dbpedia or via other apis.

One of the dangers of xml is that you can end up with complex data structures if you are not careful. For me this is more the issue.

As for JSON,Javascript developers certainly have an attraction for JSON. I also came across JSON making ajax calls to my triple store which API returns JSON or actually arrays. Another framework where this arises is in SOA where SOAP still makes extensive use of xml and REST prefers JSON.

So I'd like to know more about the development environment where you meet these problems.

Best, Jean-Pierre

From: Michael Kay [mike@saxonica.com]
Sent: 18 April 2016 10:23
To: Evain, Jean-Pierre
Cc: Christopher R. Maden; xml-dev@lists.xml.org
Subject: Re: [xml-dev] Static resolution of names is preferred over dynamic resolution of names

> I think I eventually have to ask...
> What's the matter?

The "matter" is that XML and its programming APIs are excessively complex. This has several undesirable consequences:

* People write poor-quality applications that don't achieve full interoperability

* People struggle to get those applications working at all (see StackOverflow)

* People abandon XML and use alternatives such as JSON, which brings a different set of problems.

Namespaces are a very significant component of this excess complexity.

Now, digging ourselves out of this hole is not easy and may well be impossible. But it's still useful to try and understand how we got into it.

Michael Kay

> I have been very happily using namespaces and prefixes with xml and rdf/xml for years. I always saw only advantages in it and no hindrances.
> I have also followed with interest the work done to carry this information in JSON (which need came late but eventually surfaced).
> So, again, what's the problem if there is one.
> As for the statement about namespaces being the result of some political process, then it proves that politics can helps, sometimes :--)
> Jean-pierre


This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed.
If you have received this email in error, please notify the system manager. This footnote also confirms that this email message has been swept by the mailgateway

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index]

News | XML in Industry | Calendar | XML Registry
Marketplace | Resources | MyXML.org | Sponsors | Privacy Statement

Copyright 1993-2007 XML.org. This site is hosted by OASIS