[acm-tf] Functionality

Hello,

as logical next step of Denis' suggestion and the feedback, that it
would make sense to start a list of functionality and not only saying it
must have any functionality.

To make it easier I suggest to divide functionality into 2 parts.

Object functionality and content functionality.

Object functionality describes how the object should behave in the hole
environment of the database (hierarchy, place, ...)

Content functionality describes the content that should be offered by
the object within the object (2 mail addresses, url attribute, ...)

Please do _not_ comment at this point on each of these things, we should
just collect all ideas of functionality and discuss them later. Please ;-)

I think we all agree on the following Object Functionalities:

- a good name that is easy to understand (e.g. abuse-c)
- reference it only once from INET(6)num and AUT-NUM.
- hierarchical design.
- be compatible with actual and future db design.
- flexible
- can not be linked by anyone to anywhere
- mandatory or not mandatory object
-

On a Content side we have:

- contains e-mail and abuse-mailbox attribute
- query restriction on all attributes without abuse-mailbox attribute
- contain url attribute for optional website of abuse team.
-

So please add all your ideas and recommendations to this lists. And
discuss it later via ML or in person on another conference call. As soon
as we agreed on which functionality should be implemented I suggest
asking Denis and other from the database group what would be the best
technical way to get things into production. Just an idea.

Thanks,

Tobias

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 267 bytes
Desc: OpenPGP digital signature
URL: <https://www.ripe.net/ripe/mail/archives/acm-tf/attachments/20110504/696fca55/attachment.sig>