Issue 57625

Summary: Prototype Requirement: Open standard format
Product: oopm Reporter: ooo
Component: wwwAssignee: AOO issues mailing list <issues>
Status: CLOSED OBSOLETE QA Contact: issues <>
Severity: Trivial    
Priority: P3 CC: carsten.klein, issues
Version: current   
Target Milestone: AOO PleaseHelp   
Hardware: All   
OS: All   
Issue Type: TASK Latest Confirmation in: ---
Developer Difficulty: ---
Issue Depends on:    
Issue Blocks: 57601    

Description ooo 2005-11-10 08:29:09 UTC
This task is a part of issue 57601 "Requirements specification for project   
management tool prototype":
Comment 1 ooo 2005-11-10 13:00:08 UTC
The work on an open standard format for project management data has started as 
the Open Project Managament Exchange Format project: 
The project is a collaboration of at least Project Management 
Tool Project and KPlato (Koffice) but project members from other free and open 
source project management tool projects are invited too. 
The work on the format creation is open for everyone. 
Comment 2 officista 2006-12-07 19:38:22 UTC
The topic "file format" is also handled in the issues
- Support for database backend (issue 57626)
- Client server based (issue 57636)
- Client/server architecture to centralize management of resources (issue 57641)
- Export in several formats (issue 57644)
- Data exchange with groupware for shared agendas (issue 57647)
- Import of Microsoft Project files (issue 57651)
- Import of KPlato files (issue 57652)
- Import of Planner files (issue 57653)

Apart of opmef (no action see after Nov-05) jwrolf also posted this link as an
interesting collection of file formats
------ Additional comments from jwrolf Fri Jul 7 19:26:14 -0800 2006 -------
Wide variety of flat file formats, including Microsoft Project Data Interchange.

- file format should be XML
- a database can be an option for the version with advanced features
- if the data is kept on a server (database), there must be the possibility to
work on the project locally and synchronize afterwards (travelling project
- import and export filters can be easily generated through xslt for other XML
formats (using existing filter functions). 
Comment 3 carstenklein 2009-04-03 21:26:06 UTC 

seems to be dead. no longer a requirement for looking into.

Comment 4 carstenklein 2009-04-03 21:27:22 UTC
The rest of this can be summarised as follows:

WE definitely require a new Open Document standard for project data exchange,
not necessarily for storing project data that is.

Comment 5 carstenklein 2009-04-03 21:29:41 UTC
As for the new Open Document standard for project data exchange,
I for my part would wait formulating such until we have a working prototype ready.

Additionally I would add another requirements analysis component, namely


Comment 6 carstenklein 2009-04-03 21:37:15 UTC
However, continues work on that ProjectDocument requires first a definition of
the schema we will be using for our data and meta data models.

And, alas, we will have to also support an extensible schema of some sort in
order to comply to the various requirements that came up during the q&a.

Therefore I would presume that we should call the standardisation group for
establishing a work group for working on the next addition to the standards body
made up by the Open Document Standard, as soon as we have a working prototype at

However, that prototype should already include said extensible data model and
meta data model schema.

Note: We can always orient us on the existing Open Document Standards supported
by for example Write a/o Calc.

However, we do not actually have a mailing component in OOo. Therefore we must
consider this also for the future, especially when it comes to calendaring
information exchange.

Also taking into account here wishes for being able to annotate/comment/discuss
existing tasks/milestones/projects, aka scheduled items.

Comment 7 Rob Weir 2013-07-30 02:46:27 UTC
Reset assignee on issues not touched by assignee in more than 1000 days.
Comment 8 Marcus 2017-05-20 09:11:35 UTC