Ticket #916 (closed task: wontfix)

Opened 9 months ago

Last modified 3 weeks ago

Define a naming convention for Model classes and rename all Model classes

Reported by: pradeep Assigned to:
Priority: high Milestone: 0.9.1
Component: ambra Version: 0.9-SNAPSHOT
Keywords: Cc:
Blocking: Blocked By:

Description

Currently all model classes occupy the primary name and thus making folks come up with adhoc names for classes that are view/input-handling specific. eg. the *Info classes or the Web* classes. Maybe by having a formal name suffix for the model classes will free up the name-space a bit better. One convention can be to append the word 'Model'. eg. AnnotationModel?, ArticleModel?, UserModel?, FoafModel?, RepresentationModel?, ReplyModel?, RatingModel?, CommentModel?, FormalCorrectionModel? etc. This goes well with the notion of a 'content-model' also. If anyone has better suggestion, please update this ticket.

Dependency Graph

Change History

04/19/08 02:41:06 changed by pradeep

  • owner deleted.

12/19/08 07:23:30 changed by amit

  • status changed from new to closed.
  • resolution set to wontfix.
  • milestone set to 0.9.1.

I am not sure. I think the main confusion here occured because of early mis-understanding on what otm-models in ambra/libs was about. All content-model classes should go here and the term 'model' should be avoided as far as possible. As for naming of classes, I think the fact that they are all in same place (otm-models) should convey what they are being used for. I am going to open a separate ticket to move left-over 'model' classes in webapp to otm-models.