[LOPSA-Standards-Project] project summary?

[Ross West]

Hi there,

(Quick side note: I've applied some filters on my end for this list email
so replies go back to the list for public consumption.)

> One of key, distinguishing features of Drupal is that everything
> comes out of a database. The categories establish hierarchical
> relationships (single or multiple inheritance), the fields that we
> establish, even the data.

I've been doing the crash course in the past day with Drupal, and it
seems fairly suited to doing this kind of thing.  That's a great
relief knowing that we don't need to recode something major.

> yes indeed. the category system makes all of this possible and
> sortable/viewable with little extra work.
> maybe this will help: http://drupal.org/handbook/modules/taxonomy

> yes, custom form-pages are easy. (flexinode -
> http://drupal.org/handbook/modules/flexinode)

Thanks, this helps considerably in my learning of the drupal system
(currently have a created a small test environment running with it)

>> As to the taxonomies, probably we'll find that multiple sets would be
>> required, but we have to be as flexible as possible, since there is no
>> way we can predict what could be of interest in the future.

> Indeed.

In doing some more thinking on this, I'm wonder on the idea of
creating two main content types.  One being the raw data node in which
the actual standard (RFC/etc) is listed with comments and tags (as you
proposed earlier).

The second would be a subject entry - closely (directly?) aligned to
the taxonomy category. Thereby providing some kind of central topical
description of the linked data nodes. Ie: ethernet cabling to
TIA/EIA-568-B.

And to expand on that thought - (since it seems you know the drupal
system much better than myself) - would there be a module that tracks
the child -> parent (and vice versa) looking for non-existent nodes to
make a list of things that need to be filled in?  The reason would be
to allow someone to add a node of data, link to another (non-existant)
node to be filled later (potentially by someone else).

> All created content automatically has a created date associated with it.
> Are you thinking of something in addition to this?

I'm thinking of something like a "last verified time/by who" method.
Just to do some tracking for stale data. For example: RFCs - new ones
are released that update older ones (RFC2821 obsoletes RFC821), and
others stay around for ages (RFC791).

This way it's easy to pull up a listing of nodes that haven't been
checked in a long time, and someone can verify if the data is still
valid.



Cheers,
  Ross.

--
Join the Lopsa Standards Project! http://lopsa.org/LOPSAProjects for details
(NOTE: This email is a reply to a non-list email,
but is directed to the project mailing list for archives)