[ticker-dev] new revision of ticker v3 spec

[David Arnold]

-->"Ian" == Ian Lister <ilister at dstc.edu.au> writes:

  >> i'm happy to collate and publish submissions, if you like.

  Ian> I am also happy to do it, and I probably should do it given
  Ian> that I'm the one keen on it and you're the sceptic :-)

so, thinking last night, i started by trying to name the elements of a
tickertape notification as standalone entities.

this is reasonably involved, so let me start with just one:

From

    this attribute is a tag by which the entity sending the message
    wishes to identify itself to receivers.

    in common usage that semantics is often split into two components:
    an informal entity identifier, and an informal location
    identifier.

    the intention behind the two parts is also two-fold: firstly to
    promote distinctiveness between the entity identifiers, and
    secondly to provide awareness of the current location of the
    sending entity.  i'd note that these two intentions cannot, in
    general, co-exist (ie. "david at home" loses distinctiveness).

    in light of this combination of semantics, i see two options:

    - clarify the semantics to specify that this attribute is a
      presentation name for the sending entity, which could be named
      something like "Presentation-Name" or perhaps 
      "Entity-Presentation-Name"

    - define a Tickertape-specific combined semantics, effectively
      "Entity-Presentation-Name-and-Locality-Presentation-Name"


does this seem like a reasonable thought-process?

i'm kinda interested in this particular attribute, because i think it
is a good example of the issues involved in attempting to specify
naming and semantics independent of their application.

any comments on the semantics?




d