> > No possible namespace collisions between metadata properties and data > > properties. If you combine them then you have assume that the authors of > > metadata schemas and the authors of special Freenet file schemas will > > never pick the same name for a field. > *What* are you *talking about*? This has nothing at all to do with > freenet-special data. Freenet-special messages are a rigorously defined > few messages for very very very necessary things like redirects. Anything > outside of what we spec isn't freenet-special, and should be treated as > normal data.
Previously in this thread, the list of Freenet-special files was said (by somebody other than me) to be something along the lines of redirects, multipart headers, indices, and Freenet news messages. So that's what I'm talking about. Can you enumerate the total list of things which you think freenet-special would be used for? I think that would clarify the discussion considerably. Even if you're just talking about redirects, that doesn't solve the namespace collision problem. If redirects can have normal normal metadata (i.e. any fields that the author feels like including) then the metadata needs to be separated from the data. Earlier you posted this example: > Redirect > Redirect-to=freenet:CHK at klasdfadsfldsfdfjsdf > > or > > Multipart > Part-count=10 > Part-1=freenet:CHK at asdlfldsfhsadfraewf > Part-2=freenet:CHK at alsdfhjsdfadfkdsfj Which assumes that the fields Redirect-to, Part-count, Part-1, and Part-2 are not present in the metadata. If metadata can include any fields then someone might come up with a novel and unexpected reason to include Part-count in his metadata schema. So it would be better to move this information into the data section to leave room for the metadata in the control section. In your next post you say your fine with putting the URI in the data section, so maybe we agree on that part then. _______________________________________________ Freenet-dev mailing list Freenet-dev at lists.sourceforge.net http://lists.sourceforge.net/mailman/listinfo/freenet-dev
