> I propose the term aliases...
Hey, that's good... relatively free of distracting associations.
> and that we start defining what
> properties would be content, and what would be properties
> of both aliases and originals (targets), whereever the
> target may live. How it is implemented in the core, and
> how it is presented in the admin interface is at this
> moment of relatively little importance.
>
> To kick it off, here's my idea:
>
> article content:
> title, content, abstract, author, url, revisor, revised,
> revision, approved, approver, locker, locked
>
> article alias/target:
> calstart, caldays, name, score
>
> article dunno:
> creator, created, extra*, view, icon, print, type
> topic content:
> description, revised, revisor, revision
>
> topic alias/target:
> name, owner, score
>
> topic dunno:
> extra, creator, created
I'm not sure about some of these parameters... the
manual is a little thin on detail in some cases.
Shouldn't creator/created be available to both? Or
should there be a separate field for 'editor'? Also,
how would the parameters of extendable records
be handled?
Paul
--
This is The Midgard Project's mailing list. For more information,
please visit the project's web site at http://www.midgard-project.org
To unsubscribe the list, send an empty email message to address
[EMAIL PROTECTED]
