xml for metadata in the web api - anyone using it?

Hi all,

I wanted to get an idea of to which degree people use the XML representation of meta-data in Web API.

We see that maintaining XML support for meta-data is getting increasingly costly and complicated, and is slowing down the development. Most Web apps today use the JSON representation, and increasingly integration between systems are using JSON or even CSV.

Would it be acceptable to remove support for XML for meta-data around 2.24 for July next year?

With metadata I refer to resources such as data elements, data sets and org units. We will not remove support for XML for data values (data value sets).

regards,

Lars

···

Lars Helge Øverland

Lead developer, DHIS 2

University of Oslo

Skype: larshelgeoverland

http://www.dhis2.org

xml metadata (specifically for orgunits) is being used in Rwanda.

Technically it could be changed to use json, but some work would be
required. There is an xslt which is applied to the metadata to strip
some stuff as I recall.

···

On 17 December 2015 at 16:29, Lars Helge Øverland <larshelge@gmail.com> wrote:

Hi all,

I wanted to get an idea of to which degree people use the XML representation
of meta-data in Web API.

We see that maintaining XML support for meta-data is getting increasingly
costly and complicated, and is slowing down the development. Most Web apps
today use the JSON representation, and increasingly integration between
systems are using JSON or even CSV.

Would it be acceptable to remove support for XML for meta-data around 2.24
for July next year?

With metadata I refer to resources such as data elements, data sets and org
units. We will not remove support for XML for data values (data value sets).

regards,

Lars

--
Lars Helge Øverland
Lead developer, DHIS 2
University of Oslo
Skype: larshelgeoverland
http://www.dhis2.org

_______________________________________________
Mailing list: https://launchpad.net/~dhis2-devs
Post to : dhis2-devs@lists.launchpad.net
Unsubscribe : https://launchpad.net/~dhis2-devs
More help : https://help.launchpad.net/ListHelp

For the CSD and DATIM work, we are highly dependent on the XML representation of the metadata.
Cheers,
-carl

···

On Dec 17, 2015, at 11:43 AM, Bob Jolliffe <bobjolliffe@gmail.com> wrote:

xml metadata (specifically for orgunits) is being used in Rwanda.

Technically it could be changed to use json, but some work would be
required. There is an xslt which is applied to the metadata to strip
some stuff as I recall.

On 17 December 2015 at 16:29, Lars Helge Øverland <larshelge@gmail.com> wrote:

Hi all,

I wanted to get an idea of to which degree people use the XML representation
of meta-data in Web API.

We see that maintaining XML support for meta-data is getting increasingly
costly and complicated, and is slowing down the development. Most Web apps
today use the JSON representation, and increasingly integration between
systems are using JSON or even CSV.

Would it be acceptable to remove support for XML for meta-data around 2.24
for July next year?

With metadata I refer to resources such as data elements, data sets and org
units. We will not remove support for XML for data values (data value sets).

regards,

Lars

--
Lars Helge Øverland
Lead developer, DHIS 2
University of Oslo
Skype: larshelgeoverland
http://www.dhis2.org

_______________________________________________
Mailing list: https://launchpad.net/~dhis2-devs
Post to : dhis2-devs@lists.launchpad.net
Unsubscribe : https://launchpad.net/~dhis2-devs
More help : https://help.launchpad.net/ListHelp

_______________________________________________
Mailing list: https://launchpad.net/~dhis2-devs
Post to : dhis2-devs@lists.launchpad.net
Unsubscribe : https://launchpad.net/~dhis2-devs
More help : https://help.launchpad.net/ListHelp

Hi Lars,
Just to clarify, what we are using for DATIM / CSD / mHero / etc. is XML import/export web interface that can be accessed here:

https://apps.dhis2.org/demo/dhis-web-importexport/dxf2MetaDataExport.action

as well as the metadata API:

http://dhis2.github.io/dhis2-docs/master/en/developer/html/ch01s06.html

(which I am assuming the web interface is using).

What we are not using (nor planning on using) is the xml import/export for the individual objects (e.g. under https://play.dhis2.org/dev/api/dataElements/), so as long as support for the main metadata endpoint is retained, we should be OK.

Thanks!

Cheers,

-carl

···

On Dec 17, 2015, at 12:35 PM, Carl Leitner litlfred@ibiblio.org wrote:

For the CSD and DATIM work, we are highly dependent on the XML representation of the metadata.
Cheers,
-carl

On Dec 17, 2015, at 11:43 AM, Bob Jolliffe bobjolliffe@gmail.com wrote:

xml metadata (specifically for orgunits) is being used in Rwanda.

Technically it could be changed to use json, but some work would be
required. There is an xslt which is applied to the metadata to strip
some stuff as I recall.

On 17 December 2015 at 16:29, Lars Helge Øverland larshelge@gmail.com wrote:

Hi all,

I wanted to get an idea of to which degree people use the XML representation
of meta-data in Web API.

We see that maintaining XML support for meta-data is getting increasingly
costly and complicated, and is slowing down the development. Most Web apps
today use the JSON representation, and increasingly integration between
systems are using JSON or even CSV.

Would it be acceptable to remove support for XML for meta-data around 2.24
for July next year?

With metadata I refer to resources such as data elements, data sets and org
units. We will not remove support for XML for data values (data value sets).

regards,

Lars


Lars Helge Øverland
Lead developer, DHIS 2
University of Oslo
Skype: larshelgeoverland
http://www.dhis2.org


Mailing list: https://launchpad.net/~dhis2-devs
Post to : dhis2-devs@lists.launchpad.net
Unsubscribe : https://launchpad.net/~dhis2-devs
More help : https://help.launchpad.net/ListHelp


Mailing list: https://launchpad.net/~dhis2-devs
Post to : dhis2-devs@lists.launchpad.net
Unsubscribe : https://launchpad.net/~dhis2-devs
More help : https://help.launchpad.net/ListHelp