Brian, this may seem like a strange time to be asking this question, but is there a specific hierarchy for tags? If so it would be helpful to me to have a clearer understanding of it.
In several discussions it would seem to me that if the hierarchy was in place then some of the discussion would go away. As a for instance, should there be a VAVAHU tag? If the hierarchy directed that the AHU tag ahead of the VAV then to me we would be discussing about an air handler of the type VAV and much of my expectations of how that unit would function and the types of points I should expect to find. The hierarchy would also tell me that the AHU was a peace of equipment and which building/ site it was located in. These later two being in reverse order to the previous discussion. The question about whether it is HVAC would not be significant as would the type of fluid it was handling.
In the list of TAGs the hierarchy does not reveal itself to me.
I have one other question which goes way back to why Haystack. For years, the beginning of DDC systems point identification has been a major problem of inconsistency. Is there in this approach any place for the user to see the text of the installers work to associate tags too a specific temperature sensor for the "Director Generals office" versus his secretary?
Please help me understand this. Thanks
Brian FrankThu 27 Jun 2013
I am not sure what you mean by hierarchy. We identify primary functions of equipment such as ahu, vav, chiller (essentially the chapters in the docs). And then we build a library of fact/attributes about those equipment types using tags. So the "primary tags" would be those that map to top level chapters.
Winston HetheringtonThu 27 Jun 2013
Brian, I apologize for not having looked at the main document for the Hierarchy question. It is clearly outlined in it.
I am wondering if at times some discussion hs strayed from things that seemed to have been agreed on.
I do see some minor tweaks to that document. What method would you propose to make comment without causing excessive editing on the part of those tracking changes.
I can copy the full document edit it and return the revised doc. Does Fandoc track changes? I have looked but not found.
Thanks.
Brian FrankThu 27 Jun 2013
I can copy the full document edit it and return the revised doc.
If you want I can email you the fandoc and you can send me the revised doc with your changeset. I am planning to put the source for the site up on BitBucket to make it easier. Or you can just email me / post typos and tweaks, etc
Winston HetheringtonThu 27 Jun 2013
Brian, I would appreciate if you would send a copy or post it on Google. Thanks.
Winston Hetherington Thu 27 Jun 2013
Brian, this may seem like a strange time to be asking this question, but is there a specific hierarchy for tags? If so it would be helpful to me to have a clearer understanding of it.
In several discussions it would seem to me that if the hierarchy was in place then some of the discussion would go away. As a for instance, should there be a VAVAHU tag? If the hierarchy directed that the AHU tag ahead of the VAV then to me we would be discussing about an air handler of the type VAV and much of my expectations of how that unit would function and the types of points I should expect to find. The hierarchy would also tell me that the AHU was a peace of equipment and which building/ site it was located in. These later two being in reverse order to the previous discussion. The question about whether it is HVAC would not be significant as would the type of fluid it was handling.
In the list of TAGs the hierarchy does not reveal itself to me.
I have one other question which goes way back to why Haystack. For years, the beginning of DDC systems point identification has been a major problem of inconsistency. Is there in this approach any place for the user to see the text of the installers work to associate tags too a specific temperature sensor for the "Director Generals office" versus his secretary?
Please help me understand this. Thanks
Brian Frank Thu 27 Jun 2013
I am not sure what you mean by hierarchy. We identify primary functions of equipment such as ahu, vav, chiller (essentially the chapters in the docs). And then we build a library of fact/attributes about those equipment types using tags. So the "primary tags" would be those that map to top level chapters.
Winston Hetherington Thu 27 Jun 2013
Brian, I apologize for not having looked at the main document for the Hierarchy question. It is clearly outlined in it.
I am wondering if at times some discussion hs strayed from things that seemed to have been agreed on.
I do see some minor tweaks to that document. What method would you propose to make comment without causing excessive editing on the part of those tracking changes.
I can copy the full document edit it and return the revised doc. Does Fandoc track changes? I have looked but not found.
Thanks.
Brian Frank Thu 27 Jun 2013
If you want I can email you the fandoc and you can send me the revised doc with your changeset. I am planning to put the source for the site up on BitBucket to make it easier. Or you can just email me / post typos and tweaks, etc
Winston Hetherington Thu 27 Jun 2013
Brian, I would appreciate if you would send a copy or post it on Google. Thanks.
Brian Frank Fri 28 Jun 2013
I've stuck a zip of the text files which get compiled into the docs and tag database: https://dl.dropboxusercontent.com/u/2919598/haystackws.zip