Jørn Wildt

Does anybody know of a standard XML format for exporting of web documents?

It would be quite nice if Pagesetter was able to generate a standard XML document from the various publications made with the system. The format should be something that you could import into another system with ease. This is close to, but not exactly, the same as an RSS export, the difference being that RSS publishes headlines, whereas I want to publish the whole publication.

Does anybody have a need for such a feature?

How should the document be described? It is rather easy to generate a Schema definition for the publication types, but how should that schema be published? Is it something you embed in the exported publications or should it rather exist on some URL for reference?

It would in fact also be easy to generate a WSDL document (with HTTP GET bindings) from the publication type and thereby be able to access Pagesetter documents as web services (not SOAP - only HTTP GET). Would anybody find that usefull?

AFAIK phpMyAdmin has an Export to XML feature. I would rather re-use this feature...

BTW: An export of the publication type definition seems more whishable :-)


J?rg

Type export is definitely more interesting than document exporting, agreed.

This sounds like a useful feature but it is definitely not on my A list. I can see it being used to back up and restore specific publications or the entire set of publications for a publication type.

As far as the WSDL document goes, what does that gives me? I am not familiar with that.

The WSDL let's you, among other things, automatically create C# and Java classes for access to Pagesetter information as a web service using XML. This means easy integration (reading) with Pagesetter from an external Java or Microsoft frmework.

The WSDL is an XML interface description of a web service.

ideas on formats:

There could be the following set of files:
Pagesetter_typedef.xsd - containing exact informations on document structure, mins and maxes.
pagesetter_content.xml - containing all content in a structured format
pagesetter_workflow.xml - containing the workflow data, permissions (? not sure), etc
pagesetter_workflow.xsd - maybe its good to use a official workflow description format .. there are a lot out there, maybe on thats worth to be used to avoid re-invention of wheel ;))

Packed together in a tar.gz file they could be handeled easily and through the xsd descriptors, there is a good chance to establish a rock solid import process.


S.
aka master of disaster