2007/5/1, Evgeny Egorochkin <<a href="mailto:phreedom.stdin@gmail.com">phreedom.stdin@gmail.com</a>>:<div><span class="gmail_quote"></span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
On Tuesday 01 May 2007 21:47:42 Mikkel Kamstrup Erlandsen wrote:<br>> 2007/5/1, Evgeny Egorochkin <<a href="mailto:phreedom.stdin@gmail.com">phreedom.stdin@gmail.com</a>>:<br>> > On Tuesday 01 May 2007 17:55:26 Mikkel Kamstrup Erlandsen wrote:
<br>> > > > > $MIN_CARDINALITY<br>> > > > ><br>> > > > > > Minimum cardinality. Minimum number of properties of this type<br>> ><br>> > you<br>> ><br>> > > > must
<br>> > > ><br>> > > > > > set<br>> > > > > > for a given file.<br>> > > > > > Lets specify mandatory properties. Default is 0.<br>> > > > >
<br>> > > > > Is there any example of a mandatory property? Does it even make<br>> ><br>> > sense?<br>> ><br>> > > > File name or URI?<br>> > ><br>> > > I don't see why they have to be mandatory. Not everything comes from a
<br>> > > file.<br>> > ><br>> > > In the search API it is specifically avoided to use global identifiers<br>> ><br>> > for<br>> ><br>> > > objects - as fx a mandatory uri would be. My opinion is that we
<br>> ><br>> > shouldn't<br>> ><br>> > > *force* URIs or any mandatory property onto any object.<br>> ><br>> > The intent of this was to make life easier for apps by guaranteeing
<br>> > existence<br>> > of some basic properties, however I do agree that the list would be<br>> > extremely<br>> > short if not non-existent.<br>><br>> Also taking URI as an example, you would need to enforce that it actually
<br>> contains a valid uri or else it would be useless anyway. We could add<br>> another type called "uri" which guarantees that the values form a valid<br>> uri. I don't think we should guarantee that any fields are indeed set
<br>> though.<br><br>At this moment it makes sense to drop minCardinality. It can be added later if<br>needed. Another issue worth considering in the perspective is units.</blockquote><div><br>Units... I stumbled across that a while ago, but haven't given it much thought. I think that it might be just as confusing as it useful - also it is a new requirement to meet the standard (that might or might not be trivial to add).
<br></div><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">IMHO We should finalize the first edition of the standard and extend it if the
<br>need arises.</blockquote><div><br>Yes, but we shouldn't paint our selves into a corner :-) <br></div><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
I find it strange that nobody else comments on this. Perhaps everybody<br>agree :)</blockquote><div><br>Hehe, I can bet you that not everybody agrees :-) Most of the other involved persons are core maintainers of search engines so are pretty stressed out already...
<br></div><br>Cheers,<br>Mikkel<br></div>