[Home] [By Thread] [By Date] [Recent Entries]
or allow embeddings that can be archived simultaneously. The spec could be extended as further specs for archiving embedded or linked objects are approved. Executable functions should always be prohibited - ie they should be replaced in the archive by the result of the execution. Linked objects can be replaced by using the mime encoding (or an xml equivalent) for the cid: method to include the current state of the link in the archive. Rick robert_weir@u... wrote: > > > So, instead of fighting over ODF/OOXML which can survive with or > without > > each other, perhaps ISO/W3C/OASIS/IETF etc should focus on a (possibly) > > XML based archive format for documents and data which preserves basic > > layout, links, binary objects (like jpg, avi, etc) as part of the > > format. Open Office and Microsoft can conform to Government > requirements > > by having a "Save Archive" option. > > > > All sorts of applications, not just office functions could target the > > archive format for long term storage and searching. > > > > There is probably something to be learned from ISO PDF/A in this > regard. One idea I've given some thought to is whether something > like ODF/A, defined as a formal profile or restriction of ODF, would > have significantly greater usefulness for long-term archiving than the > full ODF. ODF/A for example, could disallow scripts/macros, OLE > embeddings, image embeddings other than PNG and JPG format, etc. > > -Rob > ___________________________ > > Rob Weir > Software Architect > Workplace, Portal and Collaboration Software > IBM Software Group > > email: robert_weir@u... > phone: 1-978-399-7122 > blog: http://www.robweir.com/blog/ >
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] |

Cart



