Re: Container: was Re: Semantic Bleachers: was Re: Afghanistan War Diary as topic map in Maiana
"Andrew S. Townley" <[email protected]>
| Newsgroups | gmane.text.xml.xtm.general |
|---|---|
| Message-ID | <[email protected]> |
Hi Patrick, No worries on breaking things out. My fault for wandering, I guess... ;) On 2 Nov 2010, at 8:22 PM, Patrick Durusau wrote: > Andrew, > > Before our messages get too long to be easy reading I am splitting this > one up a bit. > > On Tue, 2010-11-02 at 19:59 +0000, Andrew S. Townley wrote: >> On 1 Nov 2010, at 6:55 PM, Patrick Durusau wrote: >> >>> Andrew, >>> > > <snip> >>> >>> Actually whether the properties and their values are the "same," is a >>> decision I would leave up to the legend designer. >>> >>> That is there could be a rule that says: >>> >>> If fullname = "Patrick Durusau" and SSN = "***-**-****", same subject, >>> so that merging would happen even if those properties were in separate >>> containers. >>> >> >> I think I agree, but what do you mean by "container" here? Is it a property? Is it a proxy? Is it an alias for a property across proxy instances? >> >> Basically, this type of merging is what I've done in my implementation so far. It also does a "same type" & "same property" & "same value" check that will determine whether merging can happen or not. >> > > I was trying to be implementation neutral but you could use the term > "proxy." Containment being in the sense of properties of a particular > subject and not necessarily a set, list, bag, or some other particular > data structure. How your application tracks those properties as grouped > for a particular subject being entirely application-dependent. > > Yes? Yes. That's fine, and I don't particularly care what we label the container for this part of the conversation, but I wanted to make sure we were talking about the same subject of property/attribute containment. :) I like/use "proxy" and "property" because that's how I think at this stage, but I wasn't trying to be snobbish one way or another. :) Naturally, the implementation will define the particular representations. Cheers, ast -- Andrew S. Townley <[email protected]> http://atownley.org