On Thu, Nov 06, 2008 at 04:03:01PM -0000, Stephens, Owen wrote:
> > In addition to DC-TEXT [1], there is a MoinMoin wiki syntax
> > for embedding DSP constraints into a human-readable wiki
> > document in a form that a script can extract to XML [2].
> > To see this applied to the Eprints profile [3], run the
> > script DSP2XML [4].  The source code is available at [5].
> > 
> > Tom
> > 
> > [1] http://dublincore.org/documents/dc-text/
> > [2] http://dublincore.org/documents/2008/10/06/dsp-wiki-syntax/
> > [3] http://dublincore.org/architecturewiki/EprintsApplicationProfile
> > [4]
> >
> http://dublincore.org/architecturewiki/EprintsApplicationProfile?action
> > =DSP2XML
> > [5] http://dublincore.org/documents/2008/10/06/dsp-wiki-
> > syntax/DescriptionSetProfile-dist.zip
> 
> Very neat - but it seems the reverse of what I'd instinctively look to
> do - that is, start with an XML version of the DSP and then integrate
> into a human readable environment?

DCMI does that with the documentation for DCMI Metadata
Terms; XML source is used to generate fresh Web pages and
RDF schemas whenever a term is added or changed.  However,
these documents and schemas are meant to be edited by just
one person and periodically published as archived snapshots.

The idea behind focusing on the wiki document was to make it
easier for people to work on the development of application
profile collaboratively.  Because everything outside the
embedded brackets is ignored in generating the XML, people are
free to add notes or strike-throughs, and they can use the
readable wiki diffs to see what's being changed.  The idea
is to help people move from a readable draft to prototype
without having to move everything out of the collaborative
editorial environment.

Tom

-- 
Tom Baker <[log in to unmask]>