Application Parts
Parts
- Storage using a REST interface (can
use any kind of storage)
- Domain Objects (FRBR entities,
whatever)
- have attributes (enforce the
range of values )[need to be predicates]
- have relations (these act like
methods on objects, (property handlers)[also a
predicate]
- Implementers for those objects (What
do implementers do?)
- Create instances of domain
objects
- Find instances meeting
criteria
- Retrieve instances by unique
identifier
- Provide UI snippets for all of
the above:
- search/lookup forms
- field edit/display snippets
- "add new" forms
- Predicates for search
- you will need to map for
different granularity of search
- the query just tells us what you
want not how to do it (separation of query and
implementation)
Can we do this all only using XML?
'Definition of serialization:' in computer
science, in the context of data storage and transmission,
serialization is the process of converting a data structure or
object into a sequence of bits so that it can be stored in a
file, a memory buffer, or transmitted across a network connection
link to be "resurrected" later in ...
Digital Object creation, presentation,
archive
At North Texas I think it is
- creation (scanning and metadata,
catalogin)
- bagit (move to achive)
- archive ingest (of bagit)
- push to presentation (using
bagit)
How can I integrate both XML apps with apps
that need more logic ?
- will xquery and dbxml replace python
and Zope?
Old Thinking
I'm just catching up with some of this thinking that's old but
I think still relevant ( RIPP)
Parts of Zope