Forums / Developer / DTD / schema for content package

DTD / schema for content package

Next topic

Author	Message
Gabriel Ambuehl	Tuesday 26 July 2005 5:21:08 am I'm trying to write some import module but after some moments I paused and figured that everything I need is already in place. Obviously, the content package facility can already deal with most if not all data types perfectly. If only there were any docs on it, preferably with a DTD and some comments on how to use it... Visit http://triligon.org
zurgutt -	Tuesday 26 July 2005 5:28:28 am I concur. I have made a universal xml input extension to import a node tree from any other system with their attributes, to transfer whole sites to ez. I used the functions at http://ez.no/products/ez_publish_cms/documentation/development/importing_attribute_data to actually insert data, however documented xml interface would be much better and it actually has to exist cause packages use it. We would need api docs and documented dtd for each datatype. Certified eZ developer looking for projects. zurgutt at gg.ee

Author

Message

Tuesday 26 July 2005 5:21:08 am

I'm trying to write some import module but after some moments I paused and figured that everything I need is already in place. Obviously, the content package facility can already deal with most if not all data types perfectly.

If only there were any docs on it, preferably with a DTD and some comments on how to use it...

Visit http://triligon.org

zurgutt -

Tuesday 26 July 2005 5:28:28 am

I concur. I have made a universal xml input extension to import a node tree from any other system with their attributes, to transfer whole sites to ez. I used the functions at http://ez.no/products/ez_publish_cms/documentation/development/importing_attribute_data
to actually insert data, however documented xml interface would be much better and it actually has to exist cause packages use it. We would need api docs and documented dtd for each datatype.

Certified eZ developer looking for projects.
zurgutt at gg.ee