#28615: Additional @type annotation
-----------------------------+------------------------------
Reporter: atagar | Owner: metrics-team
Type: enhancement | Status: new
Priority: Medium | Milestone:
Component: Metrics/Library | Version:
Severity: Normal | Resolution:
Keywords: | Actual Points:
Parent ID: | Points:
Reviewer: | Sponsor:
-----------------------------+------------------------------
Comment (by irl):
One thing that comes to mind is NASA's ontology of units. They have a
number of units defined that wouldn't make any sense on their own, but
they are found in intermediate steps of solving equations. If we begin
moving to big data stream/batch processing with databases and object
stores then we are likely to find ourselves with individual entries that
are stored on disk as objects or in databases independently of the network
status document they came from.
I believe for bandwidth files they should be "bandwidth-list" to use the
same terminology as the spec. The spec filename is "bandwidth file" but
the actual content of it calls them "lists".
--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/28615#comment:6>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online
_______________________________________________
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs
