Hi,
Okay - so there's at least some consensus for keeping the subobject hash as
it is. That means that, for subobjects to be sortable by entry order, I
think there would have to be a separate special property, called "Has
index" or "Has number" or something, that would store the index of each
subo
On 20 June 2013 20:32, Yaron Koren wrote:
> As for whether storing the index, whether it's part of the subobject name or
> in a "Has index" property, changes the data model - I don't think it does.
I think that could work as long as you do not change the identity of
the subobject. I.e. these addi
Hi Stephan,
For the duplicate data thing: you're right that duplicate data is never a
good idea; I was wrong about that. Still, in practical terms I really don't
think it matters whether the duplicate data gets stored or not. Duplicate
data just doesn't happen very much, if at all; and even when i
Hi Yaron,
I did not propose a general 'has index' property. In fact, I would strongly
advise against it. Your recipe example is a good one for a case where an
index does not make sense and implying one would be wrong.
For the students example: If your data model identifies students by their
name
Hi,
Alexey - as Stephan notes, the hash is based on the set of parameters to
#subobject, which means that if you even change one value the hash will (I
think) change. Which means that linking/referencing a specific subobject
based on its hash is not that good of a long-term strategy, I don't think
Hi Yaron,
I do not think that your approach will work.
At a first glance it seems to be an easy way out to provide sorting.
But from a software engineering point of view it loads the identifier with
information that just does not belong there. From a practical point of view
it falls short if any
I often will put "Has label" or "Has name" as well as a "Has subobject type"
properties on my subobjects along with a "Has parent". Pretty common to then
filter on "Has subobject type" and "Has parent" and sort by "Has name".
As far as the visual clutter in browse, I usually use something about
We are using anonymous (name=hash) subobjects in our system. In semantic
queries and from code, we linking them using their hash. Subobjects not
changing from every page save or edit. Only one way we discovered they
change their hash - when page has renamed/moved. So, subobjects have a good
consist
Hi Alexey,
Yes, that's a good point - I actually thought about an approach like that,
but forgot to include it in the email. A property called "Sort" (a name
like "Has index" might be a little clearer) would solve this problem - and
it would be a more "semantic" solution. On the other hand, it wou
Hi, Yaron!
I think subobjects sorting is good task, but i suggest not to use subobjects
name for this because of big problem with that:
imagine we have 3 subobjects on page:
Page name#001_4bd1f1b74a76de5322dd74956a71f089
Page name#002_03163dfd1d2502668b00c1f521688984
Page name#003_02dwa3j349j8d3
10 matches
Mail list logo
