Home » Archived » B3 » In search of a good name...
|
| Re: In search of a good name... [message #518706 is a reply to message #518609] |
Thu, 04 March 2010 19:27   |
|
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
|
|
|
| Re: In search of a good name... [message #518796 is a reply to message #518706] |
Thu, 04 March 2010 21:30 |
 Henrik Lindberg
Messages: 2509
Registered: July 2009 |
Senior Member |
|
|
Thomas and I had a discussion, and we came to like the term 'BuildBag',
short and snappy, suggest a somewhat unordered collection of build
related stuff...
Unless someone else comes up with something better, I think it is the
winner...
- henrik
Thomas Hallgren <thomas@tada.se> wrote:
> 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
>
--
- henrik
|
|
|
| Re: In search of a good name... [message #518847 is a reply to message #518796] |
Fri, 05 March 2010 04:48 |
Ed Merks
Messages: 33224
Registered: July 2009 |
Senior Member |
|
|
This is a multi-part message in MIME format.
--------------000100090800090706030905
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Henrik,
How about BuildDescriptor?
Henrik Lindberg wrote:
> Thomas and I had a discussion, and we came to like the term 'BuildBag',
> short and snappy, suggest a somewhat unordered collection of build
> related stuff...
> Unless someone else comes up with something better, I think it is the
> winner...
> - henrik
>
> Thomas Hallgren <thomas@tada.se> wrote:
>
>> 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
>>
>>
>
>
>
--------------000100090800090706030905
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: 7bit
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=UTF-8" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
Henrik,<br>
<br>
How about BuildDescriptor? <br>
<br>
<br>
Henrik Lindberg wrote:
<blockquote
cite="mid:1597312897289447834.147318henrik.lindberg-cloudsmith.com@news.eclipse.org"
type="cite">
<pre wrap="">Thomas and I had a discussion, and we came to like the term 'BuildBag',
short and snappy, suggest a somewhat unordered collection of build
related stuff...
Unless someone else comes up with something better, I think it is the
winner...
- henrik
Thomas Hallgren <a class="moz-txt-link-rfc2396E" href="mailto:thomas@tada.se"><thomas@tada.se></a> wrote:
</pre>
<blockquote type="cite">
<pre wrap="">On 03/04/2010 04:36 PM, Henrik Lindberg wrote:
</pre>
<blockquote type="cite">
<pre wrap="">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)
</pre>
</blockquote>
<pre wrap="">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
</pre>
</blockquote>
<pre wrap=""><!---->
</pre>
</blockquote>
</body>
</html>
--------------000100090800090706030905--
Ed Merks
Professional Support: https://www.macromodeling.com/
|
|
|
| Re: In search of a good name... [message #518848 is a reply to message #518796] |
Fri, 05 March 2010 04:48 |
Sebastian Zarnekow
Messages: 3118
Registered: July 2009 |
Senior Member |
|
|
Hi Henrik,
what do you think about BuildContext?
Regards,
Sebastian
--
Need professional support for Eclipse Modeling?
Go visit: http://xtext.itemis.com
Am 05.03.10 03:16, schrieb Henrik Lindberg:
> Thomas and I had a discussion, and we came to like the term 'BuildBag',
> short and snappy, suggest a somewhat unordered collection of build
> related stuff...
> Unless someone else comes up with something better, I think it is the
> winner...
> - henrik
>
> Thomas Hallgren<thomas@tada.se> wrote:
>> 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
>>
>
>
|
|
| |
| Re: In search of a good name... [message #518867 is a reply to message #518847] |
Fri, 05 March 2010 05:48 |
|
Hi Ed,
We discarded BuildInfo on the grounds that this is a bag of built material passed from one builder to another. It's not
information about something concrete but rather the concrete thing. I think BuildDescriptor falls into the same category.
- thomas
On 03/05/2010 10:35 AM, Ed Merks wrote:
> Henrik,
>
> How about BuildDescriptor?
>
>
> Henrik Lindberg wrote:
>> Thomas and I had a discussion, and we came to like the term 'BuildBag',
>> short and snappy, suggest a somewhat unordered collection of build
>> related stuff...
>> Unless someone else comes up with something better, I think it is the
>> winner...
>> - henrik
>>
>> Thomas Hallgren<thomas@tada.se> wrote:
>>
>>> 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
>>>
>>>
>>
>>
>>
|
|
|
| Re: In search of a good name... [message #518878 is a reply to message #518848] |
Fri, 05 March 2010 06:14 |
|
Hi Sebastian,
To me, the term context denotes something that encompasses a process of some sort. Like an evaluation context, query
context, naming context, etc. The BuildBag contains data passed between builders. There might be many instances of such
bags depending on how many builders that are involved.
There is a context already, it contains things needed for the evaluation and we need to reference this when we explain
how a concern is applied (in what context).
- thomas
On 03/05/2010 10:38 AM, Sebastian Zarnekow wrote:
> Hi Henrik,
>
> what do you think about BuildContext?
>
> Regards,
> Sebastian
|
|
|
| Re: In search of a good name... [message #518879 is a reply to message #518878] |
Fri, 05 March 2010 06:14 |
|
Am 05.03.2010 11:44, schrieb Thomas Hallgren:
> Hi Sebastian,
> To me, the term context denotes something that encompasses a process
> of some sort. Like an evaluation context, query context, naming
> context, etc. The BuildBag contains data
BuildData?!
Cheers
/Eike
----
http://thegordian.blogspot.com
http://twitter.com/eikestepper
> passed between builders. There might be many instances of such bags
> depending on how many builders that are involved.
>
> There is a context already, it contains things needed for the
> evaluation and we need to reference this when we explain how a concern
> is applied (in what context).
>
> - thomas
>
>
> On 03/05/2010 10:38 AM, Sebastian Zarnekow wrote:
>> Hi Henrik,
>>
>> what do you think about BuildContext?
>>
>> Regards,
>> Sebastian
>
Cheers
/Eike
----
http://www.esc-net.de
http://thegordian.blogspot.com
http://twitter.com/eikestepper
|
|
|
| Re: In search of a good name... [message #518880 is a reply to message #518879] |
Fri, 05 March 2010 06:14 |
|
On 03/05/2010 11:46 AM, Eike Stepper wrote:
> Am 05.03.2010 11:44, schrieb Thomas Hallgren:
>> Hi Sebastian,
>> To me, the term context denotes something that encompasses a process
>> of some sort. Like an evaluation context, query context, naming
>> context, etc. The BuildBag contains data
> BuildData?!
>
Yes, Henrik suggested that too and I think it's OK. I like BuildBag better though. It's shorter and more about handing
things over :-)
- thomas
|
|
|
| Re: In search of a good name... [message #518881 is a reply to message #518880] |
Fri, 05 March 2010 06:14 |
|
Am 05.03.2010 11:50, schrieb Thomas Hallgren:
> On 03/05/2010 11:46 AM, Eike Stepper wrote:
>> Am 05.03.2010 11:44, schrieb Thomas Hallgren:
>>> Hi Sebastian,
>>> To me, the term context denotes something that encompasses a process
>>> of some sort. Like an evaluation context, query context, naming
>>> context, etc. The BuildBag contains data
>> BuildData?!
>>
> Yes, Henrik suggested that too and I think it's OK. I like BuildBag
> better though. It's shorter
You're kidding :P
Cheers
/Eike
----
http://thegordian.blogspot.com
http://twitter.com/eikestepper
> and more about handing things over :-)
>
> - thomas
Cheers
/Eike
----
http://www.esc-net.de
http://thegordian.blogspot.com
http://twitter.com/eikestepper
|
|
|
| Re: In search of a good name... [message #518882 is a reply to message #518867] |
Fri, 05 March 2010 06:14 |
Ed Merks
Messages: 33224
Registered: July 2009 |
Senior Member |
|
|
Thomas,
I don't think it's actually the built material though right? A build
bag seems to imply a bag that contains a build, i.e., all the binaries
and other stuff that builds pump out the other end. If I understand
correctly it really is information/data about a build, i.e., a
description of a build, of where to find it, of what's there. I
personally rather dislike the term Bag. We might as well call it a
BuildSack. :-P
Thomas Hallgren wrote:
> Hi Ed,
> We discarded BuildInfo on the grounds that this is a bag of built
> material passed from one builder to another. It's not information
> about something concrete but rather the concrete thing. I think
> BuildDescriptor falls into the same category.
>
> - thomas
>
>
> On 03/05/2010 10:35 AM, Ed Merks wrote:
>> Henrik,
>>
>> How about BuildDescriptor?
>>
>>
>> Henrik Lindberg wrote:
>>> Thomas and I had a discussion, and we came to like the term 'BuildBag',
>>> short and snappy, suggest a somewhat unordered collection of build
>>> related stuff...
>>> Unless someone else comes up with something better, I think it is the
>>> winner...
>>> - henrik
>>>
>>> Thomas Hallgren<thomas@tada.se> wrote:
>>>
>>>> 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
>>>>
>>>>
>>>
>>>
>>>
>
Ed Merks
Professional Support: https://www.macromodeling.com/
|
|
| | |
| Re: In search of a good name... [message #518894 is a reply to message #518893] |
Fri, 05 March 2010 11:35 |
Ed Merks
Messages: 33224
Registered: July 2009 |
Senior Member |
|
|
This is a multi-part message in MIME format.
--------------090705080209090403040404
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Henrik,
I think build data gets across the notion that it's information about a
build better than does build material, which again seems more to imply
the actual material results of a build.
Henrik Lindberg wrote:
> I had not read all of the responses before my last reply...
> I am actually not so hot on BuildBag, prefer BuildData or BuildMaterial.
>
> - henrik
> Henrik Lindberg <henrik.lindberg@cloudsmith.com> wrote:
>
>> Ed, Assume you had an allergic reaction to 'BuildBag' :)
>> 'BuildDescriptor' could work, but to me it sounds like it describes an
>> action, rather than the input and output of such an action.
>>
>> How about "BuildMaterial" ?
>>
>>
>
>
>
--------------090705080209090403040404
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: 7bit
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=UTF-8" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
Henrik,<br>
<br>
I think build data gets across the notion that it's information about a
build better than does build material, which again seems more to imply
the actual material results of a build.<br>
<br>
<br>
Henrik Lindberg wrote:
<blockquote
cite="mid:1387245646289480598.815361henrik.lindberg-cloudsmith.com@news.eclipse.org"
type="cite">
<pre wrap="">I had not read all of the responses before my last reply...
I am actually not so hot on BuildBag, prefer BuildData or BuildMaterial.
- henrik
Henrik Lindberg <a class="moz-txt-link-rfc2396E" href="mailto:henrik.lindberg@cloudsmith.com"><henrik.lindberg@cloudsmith.com></a> wrote:
</pre>
<blockquote type="cite">
<pre wrap="">Ed, Assume you had an allergic reaction to 'BuildBag' :)
'BuildDescriptor' could work, but to me it sounds like it describes an
action, rather than the input and output of such an action.
How about "BuildMaterial" ?
</pre>
</blockquote>
<pre wrap=""><!---->
</pre>
</blockquote>
</body>
</html>
--------------090705080209090403040404--
Ed Merks
Professional Support: https://www.macromodeling.com/
|
|
|
| Re: In search of a good name... [message #518903 is a reply to message #518894] |
Fri, 05 March 2010 07:12 |
|
Ed,
It *is* the actual material results.
That's why BuildBag is my favorite. A builder produces something, puts in in a bag for another builder to pick up.
- thomas
On 03/05/2010 12:35 PM, Ed Merks wrote:
> Henrik,
>
> I think build data gets across the notion that it's information about a
> build better than does build material, which again seems more to imply
> the actual material results of a build.
>
>
> Henrik Lindberg wrote:
>> I had not read all of the responses before my last reply...
>> I am actually not so hot on BuildBag, prefer BuildData or BuildMaterial.
>>
>> - henrik
>> Henrik Lindberg<henrik.lindberg@cloudsmith.com> wrote:
>>
>>> Ed, Assume you had an allergic reaction to 'BuildBag' :)
>>> 'BuildDescriptor' could work, but to me it sounds like it describes an
>>> action, rather than the input and output of such an action.
>>>
>>> How about "BuildMaterial" ?
>>>
>>>
>>
>>
>>
|
|
| |
| Re: In search of a good name... [message #519471 is a reply to message #519456] |
Mon, 08 March 2010 17:38 |
Henrik Lindberg
Messages: 2509
Registered: July 2009 |
Senior Member |
|
|
Hi,
I was thinking about that when I suggested "Bag" (a 'multiset').
Thinking a bit more about this, what it contains is really not a
multiset/bag, as each URI would only be represented once (not meaningful
to say that a particular source file, or output file is included more
than once (and the same with annotations/properties)).
So, it is really a Set rather than a Bag, with the logical consequence
of naming the thing "BuildSet". Which I think is the best name so far -
it is a set of things, it is about build data/material/resources, and it
is similar to a corresponding FileSet structure found in other build
technologies.
The only problem with the name BuildSet, is that it probably does not
implement Java Set interface :) because it is a set of two disjunct
types of things (URIs and "variables") - but I can live with that.
- henrik
On 3/8/10 10:15 PM, Erdal Karaca wrote:
> You may also want to consider the mathematical definition of a 'bag'
> used as a data structure: http://en.wikipedia.org/wiki/Multiset
>
|
|
| | |
| Re: In search of a good name... [message #602146 is a reply to message #518706] |
Fri, 05 March 2010 02:16 |
Henrik Lindberg
Messages: 2509
Registered: July 2009 |
Senior Member |
|
|
Thomas and I had a discussion, and we came to like the term 'BuildBag',
short and snappy, suggest a somewhat unordered collection of build
related stuff...
Unless someone else comes up with something better, I think it is the
winner...
- henrik
Thomas Hallgren <thomas@tada.se> wrote:
> 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
>
--
- henrik
|
|
|
| Re: In search of a good name... [message #602151 is a reply to message #602146] |
Fri, 05 March 2010 09:35 |
Ed Merks
Messages: 33224
Registered: July 2009 |
Senior Member |
|
|
This is a multi-part message in MIME format.
--------------000100090800090706030905
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Henrik,
How about BuildDescriptor?
Henrik Lindberg wrote:
> Thomas and I had a discussion, and we came to like the term 'BuildBag',
> short and snappy, suggest a somewhat unordered collection of build
> related stuff...
> Unless someone else comes up with something better, I think it is the
> winner...
> - henrik
>
> Thomas Hallgren <thomas@tada.se> wrote:
>
>> 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
>>
>>
>
>
>
--------------000100090800090706030905
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: 7bit
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=UTF-8" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
Henrik,<br>
<br>
How about BuildDescriptor? <br>
<br>
<br>
Henrik Lindberg wrote:
<blockquote
cite="mid:1597312897289447834.147318henrik.lindberg-cloudsmith.com@news.eclipse.org"
type="cite">
<pre wrap="">Thomas and I had a discussion, and we came to like the term 'BuildBag',
short and snappy, suggest a somewhat unordered collection of build
related stuff...
Unless someone else comes up with something better, I think it is the
winner...
- henrik
Thomas Hallgren <a class="moz-txt-link-rfc2396E" href="mailto:thomas@tada.se"><thomas@tada.se></a> wrote:
</pre>
<blockquote type="cite">
<pre wrap="">On 03/04/2010 04:36 PM, Henrik Lindberg wrote:
</pre>
<blockquote type="cite">
<pre wrap="">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)
</pre>
</blockquote>
<pre wrap="">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
</pre>
</blockquote>
<pre wrap=""><!---->
</pre>
</blockquote>
</body>
</html>
--------------000100090800090706030905--
Ed Merks
Professional Support: https://www.macromodeling.com/
|
|
|
| Re: In search of a good name... [message #602162 is a reply to message #602146] |
Fri, 05 March 2010 09:38 |
Sebastian Zarnekow
Messages: 3118
Registered: July 2009 |
Senior Member |
|
|
Hi Henrik,
what do you think about BuildContext?
Regards,
Sebastian
--
Need professional support for Eclipse Modeling?
Go visit: http://xtext.itemis.com
Am 05.03.10 03:16, schrieb Henrik Lindberg:
> Thomas and I had a discussion, and we came to like the term 'BuildBag',
> short and snappy, suggest a somewhat unordered collection of build
> related stuff...
> Unless someone else comes up with something better, I think it is the
> winner...
> - henrik
>
> Thomas Hallgren<thomas@tada.se> wrote:
>> 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
>>
>
>
|
|
| |
| Re: In search of a good name... [message #602174 is a reply to message #602151] |
Fri, 05 March 2010 10:38 |
|
Hi Ed,
We discarded BuildInfo on the grounds that this is a bag of built material passed from one builder to another. It's not
information about something concrete but rather the concrete thing. I think BuildDescriptor falls into the same category.
- thomas
On 03/05/2010 10:35 AM, Ed Merks wrote:
> Henrik,
>
> How about BuildDescriptor?
>
>
> Henrik Lindberg wrote:
>> Thomas and I had a discussion, and we came to like the term 'BuildBag',
>> short and snappy, suggest a somewhat unordered collection of build
>> related stuff...
>> Unless someone else comes up with something better, I think it is the
>> winner...
>> - henrik
>>
>> Thomas Hallgren<thomas@tada.se> wrote:
>>
>>> 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
>>>
>>>
>>
>>
>>
|
|
|
| Re: In search of a good name... [message #602182 is a reply to message #602162] |
Fri, 05 March 2010 10:44 |
|
Hi Sebastian,
To me, the term context denotes something that encompasses a process of some sort. Like an evaluation context, query
context, naming context, etc. The BuildBag contains data passed between builders. There might be many instances of such
bags depending on how many builders that are involved.
There is a context already, it contains things needed for the evaluation and we need to reference this when we explain
how a concern is applied (in what context).
- thomas
On 03/05/2010 10:38 AM, Sebastian Zarnekow wrote:
> Hi Henrik,
>
> what do you think about BuildContext?
>
> Regards,
> Sebastian
|
|
|
| Re: In search of a good name... [message #602189 is a reply to message #602182] |
Fri, 05 March 2010 10:46 |
|
Am 05.03.2010 11:44, schrieb Thomas Hallgren:
> Hi Sebastian,
> To me, the term context denotes something that encompasses a process
> of some sort. Like an evaluation context, query context, naming
> context, etc. The BuildBag contains data
BuildData?!
Cheers
/Eike
----
http://thegordian.blogspot.com
http://twitter.com/eikestepper
> passed between builders. There might be many instances of such bags
> depending on how many builders that are involved.
>
> There is a context already, it contains things needed for the
> evaluation and we need to reference this when we explain how a concern
> is applied (in what context).
>
> - thomas
>
>
> On 03/05/2010 10:38 AM, Sebastian Zarnekow wrote:
>> Hi Henrik,
>>
>> what do you think about BuildContext?
>>
>> Regards,
>> Sebastian
>
Cheers
/Eike
----
http://www.esc-net.de
http://thegordian.blogspot.com
http://twitter.com/eikestepper
|
|
|
| Re: In search of a good name... [message #602196 is a reply to message #602189] |
Fri, 05 March 2010 10:50 |
|
On 03/05/2010 11:46 AM, Eike Stepper wrote:
> Am 05.03.2010 11:44, schrieb Thomas Hallgren:
>> Hi Sebastian,
>> To me, the term context denotes something that encompasses a process
>> of some sort. Like an evaluation context, query context, naming
>> context, etc. The BuildBag contains data
> BuildData?!
>
Yes, Henrik suggested that too and I think it's OK. I like BuildBag better though. It's shorter and more about handing
things over :-)
- thomas
|
|
|
| Re: In search of a good name... [message #602202 is a reply to message #602196] |
Fri, 05 March 2010 10:54 |
|
Am 05.03.2010 11:50, schrieb Thomas Hallgren:
> On 03/05/2010 11:46 AM, Eike Stepper wrote:
>> Am 05.03.2010 11:44, schrieb Thomas Hallgren:
>>> Hi Sebastian,
>>> To me, the term context denotes something that encompasses a process
>>> of some sort. Like an evaluation context, query context, naming
>>> context, etc. The BuildBag contains data
>> BuildData?!
>>
> Yes, Henrik suggested that too and I think it's OK. I like BuildBag
> better though. It's shorter
You're kidding :P
Cheers
/Eike
----
http://thegordian.blogspot.com
http://twitter.com/eikestepper
> and more about handing things over :-)
>
> - thomas
Cheers
/Eike
----
http://www.esc-net.de
http://thegordian.blogspot.com
http://twitter.com/eikestepper
|
|
|
| Re: In search of a good name... [message #602209 is a reply to message #602174] |
Fri, 05 March 2010 10:54 |
Ed Merks
Messages: 33224
Registered: July 2009 |
Senior Member |
|
|
Thomas,
I don't think it's actually the built material though right? A build
bag seems to imply a bag that contains a build, i.e., all the binaries
and other stuff that builds pump out the other end. If I understand
correctly it really is information/data about a build, i.e., a
description of a build, of where to find it, of what's there. I
personally rather dislike the term Bag. We might as well call it a
BuildSack. :-P
Thomas Hallgren wrote:
> Hi Ed,
> We discarded BuildInfo on the grounds that this is a bag of built
> material passed from one builder to another. It's not information
> about something concrete but rather the concrete thing. I think
> BuildDescriptor falls into the same category.
>
> - thomas
>
>
> On 03/05/2010 10:35 AM, Ed Merks wrote:
>> Henrik,
>>
>> How about BuildDescriptor?
>>
>>
>> Henrik Lindberg wrote:
>>> Thomas and I had a discussion, and we came to like the term 'BuildBag',
>>> short and snappy, suggest a somewhat unordered collection of build
>>> related stuff...
>>> Unless someone else comes up with something better, I think it is the
>>> winner...
>>> - henrik
>>>
>>> Thomas Hallgren<thomas@tada.se> wrote:
>>>
>>>> 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
>>>>
>>>>
>>>
>>>
>>>
>
Ed Merks
Professional Support: https://www.macromodeling.com/
|
|
| | |
| Re: In search of a good name... [message #602589 is a reply to message #518893] |
Fri, 05 March 2010 11:35 |
Ed Merks
Messages: 33224
Registered: July 2009 |
Senior Member |
|
|
This is a multi-part message in MIME format.
--------------090705080209090403040404
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Henrik,
I think build data gets across the notion that it's information about a
build better than does build material, which again seems more to imply
the actual material results of a build.
Henrik Lindberg wrote:
> I had not read all of the responses before my last reply...
> I am actually not so hot on BuildBag, prefer BuildData or BuildMaterial.
>
> - henrik
> Henrik Lindberg <henrik.lindberg@cloudsmith.com> wrote:
>
>> Ed, Assume you had an allergic reaction to 'BuildBag' :)
>> 'BuildDescriptor' could work, but to me it sounds like it describes an
>> action, rather than the input and output of such an action.
>>
>> How about "BuildMaterial" ?
>>
>>
>
>
>
--------------090705080209090403040404
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: 7bit
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=UTF-8" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
Henrik,<br>
<br>
I think build data gets across the notion that it's information about a
build better than does build material, which again seems more to imply
the actual material results of a build.<br>
<br>
<br>
Henrik Lindberg wrote:
<blockquote
cite="mid:1387245646289480598.815361henrik.lindberg-cloudsmith.com@news.eclipse.org"
type="cite">
<pre wrap="">I had not read all of the responses before my last reply...
I am actually not so hot on BuildBag, prefer BuildData or BuildMaterial.
- henrik
Henrik Lindberg <a class="moz-txt-link-rfc2396E" href="mailto:henrik.lindberg@cloudsmith.com"><henrik.lindberg@cloudsmith.com></a> wrote:
</pre>
<blockquote type="cite">
<pre wrap="">Ed, Assume you had an allergic reaction to 'BuildBag' :)
'BuildDescriptor' could work, but to me it sounds like it describes an
action, rather than the input and output of such an action.
How about "BuildMaterial" ?
</pre>
</blockquote>
<pre wrap=""><!---->
</pre>
</blockquote>
</body>
</html>
--------------090705080209090403040404--
Ed Merks
Professional Support: https://www.macromodeling.com/
|
|
|
| Re: In search of a good name... [message #602592 is a reply to message #518894] |
Fri, 05 March 2010 12:05 |
|
Ed,
It *is* the actual material results.
That's why BuildBag is my favorite. A builder produces something, puts in in a bag for another builder to pick up.
- thomas
On 03/05/2010 12:35 PM, Ed Merks wrote:
> Henrik,
>
> I think build data gets across the notion that it's information about a
> build better than does build material, which again seems more to imply
> the actual material results of a build.
>
>
> Henrik Lindberg wrote:
>> I had not read all of the responses before my last reply...
>> I am actually not so hot on BuildBag, prefer BuildData or BuildMaterial.
>>
>> - henrik
>> Henrik Lindberg<henrik.lindberg@cloudsmith.com> wrote:
>>
>>> Ed, Assume you had an allergic reaction to 'BuildBag' :)
>>> 'BuildDescriptor' could work, but to me it sounds like it describes an
>>> action, rather than the input and output of such an action.
>>>
>>> How about "BuildMaterial" ?
>>>
>>>
>>
>>
>>
|
|
| |
| Re: In search of a good name... [message #602602 is a reply to message #519456] |
Mon, 08 March 2010 22:24 |
Henrik Lindberg
Messages: 2509
Registered: July 2009 |
Senior Member |
|
|
Hi,
I was thinking about that when I suggested "Bag" (a 'multiset').
Thinking a bit more about this, what it contains is really not a
multiset/bag, as each URI would only be represented once (not meaningful
to say that a particular source file, or output file is included more
than once (and the same with annotations/properties)).
So, it is really a Set rather than a Bag, with the logical consequence
of naming the thing "BuildSet". Which I think is the best name so far -
it is a set of things, it is about build data/material/resources, and it
is similar to a corresponding FileSet structure found in other build
technologies.
The only problem with the name BuildSet, is that it probably does not
implement Java Set interface :) because it is a set of two disjunct
types of things (URIs and "variables") - but I can live with that.
- henrik
On 3/8/10 10:15 PM, Erdal Karaca wrote:
> You may also want to consider the mathematical definition of a 'bag'
> used as a data structure: http://en.wikipedia.org/wiki/Multiset
>
|
|
| | |
Goto Forum:
Current Time: Fri Oct 11 23:59:31 GMT 2024
Powered by FUDForum. Page generated in 0.04870 seconds |
] 
Search
Help
Register
Login
Home
