-simply because it needs to be representable on clients.
-Moreover, \glspl{SDS} behave a little different in an \gls{mTask} device
-compared to in the \gls{iTasks} system. In an \gls{iTasks} system, when the
-\gls{SDS} is updated, a broadcast to all watching \glspl{Task} in the system
-is made to notify them of the update. \glspl{SDS} can update often and the
-update might not be the final value it will get. Implementing the same
-functionality on the \gls{mTask} client would result in a lot of expensive
-unneeded bandwidth usage. Therefore a device must publish the \gls{SDS}
-explicitly to save bandwidth.
+simply because it needs to be representable on clients. Moreover, \glspl{SDS}
+behave a little different in an \gls{mTask} device compared to in the
+\gls{iTasks} system. In an \gls{iTasks} system, when the \gls{SDS} is updated,
+a broadcast to all watching \glspl{Task} in the system is made to notify them
+of the update. \glspl{SDS} can update often and the update might not be the
+final value it will get. Implementing the same functionality on the \gls{mTask}
+client would result in a lot of expensive unneeded bandwidth usage. Therefore
+a device must publish the \gls{SDS} explicitly to save bandwidth.