[INFOD-WG] Wild naming changes

[Dieter Gawlick]

Ronny,

I really don't know what term people prefer in this context. We could 
ask the UTK people in the upcoming conference call; at least we have 
opinions from people who not as much tainted by the history.

Dieter

Ronny Fehling wrote:
>
> Sorry to be such a pain...
>
> Personally, I am not too happy with the 'Entry' word in general. I 
> have never heard that before in such a context either. I would much 
> rather lean towards something like 'Object'. Reason being that the 
> Registry after receiving those call will actually 'create' some sort 
> of an object in the DB. Even if the registry doesn't use an actual DB, 
> I would rather take an expression from either the DB vocabulary or the 
> XML vocabulary. Dieter -- what do you think?
>
>  
>
> R
>
>
>
> Dieter Gawlick wrote:
>> Steve,
>>
>> I think I can go along with this except for the name DataEntry. The 
>> word implies for me that we actaully talk about the entries. However, 
>> we like to reference a collection of data or a data source. So maybe, 
>> DataSource or DataCollection would be a better name.
>>
>> Dieter
>>
>> Fisher, SM (Steve) wrote:
>>>
>>> Hi,
>>>
>>> I am still struggling with names.
>>>
>>> Many of the arguments of the messages are things which exist in the 
>>> outside world, so if we change to for example RegisterPublisher this 
>>> does not really help as we still need the name for the Publisher 
>>> record in the registry as it is is used elsewhere.
>>>
>>> I think I like to use the names:
>>>
>>> PublisherEntry
>>> ConsumerEntry
>>> SubscriberEntry
>>> Subscription
>>> PropertyVocabulary
>>> PropertyVocabularyInstance
>>> DataVocabulary
>>> DataEntry
>>>
>>> where these are the names of entries in the registry
>>>
>>> The first 3 need the word entry to distinguish them from the things 
>>> in the real world
>>>
>>> DataEntry corresponds to a data source - and is what we have so far 
>>> called an association.
>>>
>>> We can then use the verbs create, replace and drop for everything.
>>>
>>> I will then avoid the term entity altogether
>>>
>>> Note that subscription, propertyVocabulary, 
>>> PropertyVocabularyInstance and DataVocabulary only exist in the registry
>>>
>>> DataEntry is a bit special as it somehow relates to something outside
>>>
>>> Unregister vocabulary used to work with either data or property 
>>> vocabularies. I have avoided this special case
>>>
>>> I have included a few extra replace operations which we may not want 
>>> - however I think the names make sense
>>>
>>> Please see the attached spreadsheet for the new and old names
>>>
>>> Making these changes to the UseCases and spec and spec will be very 
>>> tedious - so we should not do anything too hasty. For the moment 
>>> this is the best I can come up with. On the other hand I can't make 
>>> progress on chapter 1 until we do decide.
>>>
>>> Steve
>>>
>>>  
>>>
>>>  
>>>
>>>  
>>>
>>>  
>>>
>>>  
>>>
>>>  
>>>
>>>  
>>>
>>>  
>>>
>>>  
>>>
>>> ------------------------------------------------------------------------
>>>
>>> --
>>>   infod-wg mailing list
>>>   infod-wg at ogf.org
>>>   http://www.ogf.org/mailman/listinfo/infod-wg
>> ------------------------------------------------------------------------
>>
>> --
>>   infod-wg mailing list
>>   infod-wg at ogf.org
>>   http://www.ogf.org/mailman/listinfo/infod-wg
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://www.ogf.org/pipermail/infod-wg/attachments/20070312/ce957c1c/attachment.html