Re: [xml-dev] The year is 2027, and we need to examine archived XML docu

["bryan rasmussen" <rasmussen.bryan@gmail.com>]

Well, this seems to be a good time to point to the Danish FESD
Archiving standard, written in glorious Danish!
http://www.oio.dk/files/Arkivstruktur_Godkendt_std.pdf

from the OIO description:

http://www.oio.dk/dataudveksling/fesd?o=bd8a9c1811c3c28a6786e1319110ef89

somewhat poor translation:

 Standardization of the datamodel for Archive structure is a part of
the complete standardization of FESD datamodel, which is being
developed with a focus on securing interoperability between government
agencies while at the same time creating a groundwork for developing
and standardization of modules.

The purpose in standardizing the datamodel for Archive structure is
primarily to secure description of an informational archive with focus
on acceptance and delivery at governmental archives, including the
giving of storage and disclosure requirements.


Furthermore the purpose is to describe and thereby identify logical
document similarities, which will be archived and used in a
FESD-solution, but which is not a part of the informational archive
(not case related documents)

finally the standard should describe the relation to the complete data
model in relation to subject systematic and connection to case and
document entities.


There is no discussion of a delivery module which would handle the
functional requirements with delivery to governmental archives, but
only the standardization of the data model for archive structure. For
standardization of the delivery module please refer to
FESD-Standardization group methode hearing of delivery module in
February 2005


quoted danish:

FESD Arkivstruktur

Standardisering af datamodel for Arkivstruktur er en del af den
samlede standardisering af FESD datamodellen, som udvikles med henblik
på at sikre interoperabiliteten mellem myndigheder samt skabe grundlag
for udvikling og standardisering af moduler.

Formålet med at standardisere datamodel for Arkivstruktur er primært
at sikre beskrivelse af det forvaltningsmæssige arkiv med henblik på
godkendelse og aflevering hos Statens Arkiver, herunder angivelse af
bevarings- og anmeldelsesoplysninger.

Endvidere er formålet at kunne beskrive og dermed identificere logiske
dokumentsamlinger, som arkiveres og benyttes i en FESD-løsning, men
som ikke er en del af det forvaltningsmæssige arkiv (ikke sagsbundne
dokumenter).

Endelig skal standarden beskrive relationen til den samlede datamodel
i forhold til emnesystematik og tilknytning til sags- og
dokumententiteterne.

Der er ikke tale om et afleveringsmodul, der håndterer de funktionelle
krav ved aflevering til offentligt arkiv, men alene standardisering af
datamodel for Arkivstruktur. For standardisering af Afleveringsmodul
henvises til FESD-standardiseringsgruppens metodehøring af
afleveringsmodul i februar 2005.



Not exactly sure if I find this the right way of doing it.


Cheers,
Bryan Rasmussen


On 9/10/07, Rick Marshall <rjm@zenucom.com> wrote:
> 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@us.ibm.com 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@us.ibm.com
> > phone: 1-978-399-7122
> > blog: http://www.robweir.com/blog/
> >
>
> _______________________________________________________________________
>
> XML-DEV is a publicly archived, unmoderated list hosted by OASIS
> to support XML implementation and development. To minimize
> spam in the archives, you must subscribe before posting.
>
> [Un]Subscribe/change address: http://www.oasis-open.org/mlmanage/
> Or unsubscribe: xml-dev-unsubscribe@lists.xml.org
> subscribe: xml-dev-subscribe@lists.xml.org
> List archive: http://lists.xml.org/archives/xml-dev/
> List Guidelines: http://www.oasis-open.org/maillists/guidelines.php
>
>