here is - as announced when I sent out the design doc - the detailed API
spec for ChannelFinder, the EPICS Directory Service.
Please cross-check it, think about how your installation would be using
it, and comment if you find things unclear, missing, or wrong.
The ChannelFinder properties are intended to be used for structural,
location, and any kind of functional data (see the example data in the
document), tags will allow to create channel groups of all sorts and can
be used for name aliases.
While this service is being developed for NSLS-II, I would really like
it to be as generic and simple as possible. Ideally, it could be used
for any installation that wants to use channel-by-function queries for
their applications. RDB systems like IRMIS are naturally a good source
of directory data, but the ChannelFinder does not require them.
(Nor EPICS, actually ... nor a control system. It could be used to find
songs in your mp3 collection by artist, year, and album.)
Thanks a lot,