In search of a good name... [message #602134] |
Thu, 04 March 2010 10:36  |
Eclipse User |
|
|
|
Hi,
I am looking for a good name for a construct used in b3. It is currently
called BuildResult - but this name is not good as the same structure is
used as input to the logic that produces a build result.
The BuildResult is basically a set of URIs, and a set of named and typed
values.
The name AnnotadedURIGroup is one possibility, or even the shorter
URIGroup (as there is no unannotated group to confuse it with).
Other possible names (thinking about the role of the class) could be
BuildData, ResourceData, BuildResources.
So, does anyone have ideas what this "Bunch of URIs and stuff" should be
called? (I am leaning towards URIGroup)
Regards
- henrik
|
|
|
Re: In search of a good name... [message #602142 is a reply to message #602134] |
Thu, 04 March 2010 14:27  |
Eclipse User |
|
|
|
On 03/04/2010 04:36 PM, Henrik Lindberg wrote:
> Hi,
> I am looking for a good name for a construct used in b3. It is currently
> called BuildResult - but this name is not good as the same structure is
> used as input to the logic that produces a build result.
>
> The BuildResult is basically a set of URIs, and a set of named and typed
> values.
>
> The name AnnotadedURIGroup is one possibility, or even the shorter
> URIGroup (as there is no unannotated group to confuse it with).
>
> Other possible names (thinking about the role of the class) could be
> BuildData, ResourceData, BuildResources.
>
> So, does anyone have ideas what this "Bunch of URIs and stuff" should be
> called? (I am leaning towards URIGroup)
>
I think URIGroup is too limiting but I like BuildResources. It keeps the door open if we want to add more attributes to
it later. I like the name because this is something that is passed between builders.
- thomas
|
|
|
Powered by
FUDForum. Page generated in 0.58317 seconds