Deprecated stuff

[caprenter]

Should there be something added to the schema so that when something is deprecated we can read that from the schema?

So far I think we have deprecated both elements and attributes.

If this was desirable it could go into 1.05 and 2.01 possibly

[Bjwebb]

It would be good to have machine readable deprecation information. Ideally this should include the version it was deprecated in.

[bill-anderson]

Yes

Deprecated items cannot be removed from the schema - but should be clearly marked

From: caprenter [mailto:notifications@github.com]
Sent: 27 March 2014 13:56
To: IATI/IATI-Schemas
Subject: [IATI-Schemas] Deprecated stuff (#58)

Should there be something added to the schema so that when something is deprecated we can read that from the schema?

So far I think we have deprecated both elements and attributes.

If this was desirable it could go into 1.05 and 2.01 possibly

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/58.

---

This email has been scanned by the Symantec Email Security.cloud service.
For more information please visit http://www.symanteccloud.com

---

---

This email has been scanned by the Symantec Email Security.cloud service.
For more information please visit http://www.symanteccloud.com

---

[caprenter]

This will not make it into 1.05 and is not needed in 2.01 yet. It clearly needs more thought and work, so switching milestone

[akmiller01]

I'm guessing the direction that was chosen here was just to let deprecated elements be automatically discovered via comparing past versions of the schema.