Creating well known files

Creating a file using TKI just means running the "cr" command on the appropriate directory and providing a file name. But when using the web interface, we may want to do something different.

Directories are really just a type designation, so we might not want to have a user create command tied to the directory. Instead, it seems more appropriate to have it on a DataSet file. Indeed, we may want to require that all WellKnown files are members of one or more DataSets.

But now a circularity issue--if DataSet files are also WellKnown, how do we create DataSets? Hmm. If a DataSet can hold other DataSet files, then we have a partial answer. Now we only need to have a top-level DataSet file. And we could create the top-level DataSet file using TKI.

(Remember, we want to support TKI operations on WellKnown files.)

OK then! We put the create command for WellKnown files on DataSets. (Oh. Guess we haven't defined how we will define web commands on files. More blogging yet to do.) This new create command would require the WellKnownName (preferably unique within the dataset, but not required to be) and the type (a directory of WellKnown files).

Now, do we want to constrain the types of files a DataSet can hold? Possibly. But that can be difficult to enforce with shared data, unless we put that constraint on a dataset descriptor. And that is basicly a "logic" change that requires changes to metadata and would be harder to share than ordinary user data. So I'm inclined to avoid having this kind of constraint.