PLAYERS TASKS PRAXIS TEAMS EVENTS
Username:Password:
New player? Sign Up Here
Salty Pete
Level 1: 10 points
Alltime Score: 1589 points
Last Logged In: September 7th, 2010

View Salty Pete's:



retired

40 points

Develop And Submit A Protocol by Salty Pete

July 22nd, 2006 7:48 PM

INSTRUCTIONS: Develop a protocol and attempt to have it validated (more on the cagey wording in a moment). The word is derived from protos "first" + kolla "glue". Its current usage, referring to agreed-upon rules for the transmission and format of data, came into widespread usage in the 1980s. But the historical usage of the word ranges widely*, and since IP over Carrier Pigeon is already taken, we strongly suggest that you create a protocol that is not intended for the transmission of data.


In preparation for a later task, I've decided to create the following protocol. Since I've never done this before, I stole Gadget's Protocol format verbatim.



Personal Identity Management Protocol (PIMP)



  • The object of the Personal Identity Managemnt Protocol is to quickly and reliably allow the contextual identification of entity.


  • The Player Identification Protocol consists of two parts: The Personal Identity Management Protocol Identifier (PIMP ID) and the communication protocol. The PIMP ID is a simple least to most speficic identifier containing contexual identification information, this means that a PIMP ID is both uniquely identifying but also informative. The communications protocol is a generic query-response that can be adapted for many diffent means of communication.

  • The PIMP ID - This section describes the compostion of the PIMP ID:



    • A PIMP ID is composed of a context idetifier and a number of sub-identifiers in order from least to most specific in terms of the context.

    • The Context Identifier always comes first in a PIMP. The key is a Simple Name for the context of the description. The key is followed by "::"
      • For example, your sf0 identifier would start with: sf0::


    • The Sub-Identifier is composed of a key-value pair. The key is a descriptor of the information, the value is, of course, the value. These values are seperated by "="
      • For example: sfo::Name=gxp


    • Individual Sub-Identifiers are to be seperated by commas.
      • For example: sfo::team=existenz,name=gxp

    • When using a PIMP ID in spoken or other auditory communication, note the folowing pronounciations:

      • The Context Identifier may be unvoiced, since the PIMP ID is contextual it is implied.
      • = is pronounced "is"
      • , is pronounced "and"

    • An entity might have several PIMP IDs depending on the number of contexts in which they seek identification.







  • The Personal Identification Protocol is a felixible protocol useful on many different networks. In this protocol, an entity sends periodically (or continuously) sends out a signal that advertises it's presence. Entities interested in identifying other entities listen for such signals and open receipt send out a query and wait for a response. The query contains the Context in question. The advertising entity will send out it's context related identification until it receieves an acknowledgement that the identification has been received. Once the querying entity has the identification, it will reply with an acknowledgement and then go back to passive listening mode, ignoring further signals from the advertiser until a certain amount of time has passed. For example:

    PirateyMonkey: Here I am! Here I am! Here I am!!!!
    Gadget: Hi, do you play sf0?
    PirateyMonkey: Yes, my team is (that artsy team) and my name is PirateyMonkey.
    Gadget: Oh.
    PirateyMonkey: Here I am! Here I am! Here I am!!!!

    or

    PirateyMonkey (wearing an sf0 button)
    Gadget: (Notices the button) Hi, do you play sf0?
    PirateyMonkey: Yes, my team is (that artsy team) and my name is PirateyMonkey.
    Gadget: Oh.
    PirateyMonkey: (goes about her business.)

    or

    There are other more serious examples but they really just involve machines following example one, but doing it wirelessly and with ones and zeroes. I guess it would look something like this:
    Machine 1: 1! 1! 1!
    Machine 2: 101?
    Machine 1: 1001111100011111000011101001110.
    Machine 2: 11101110
    Machine 1: 1! 1! 1!



For specialized communications, organizations may wish to create PIMP ID Document Definition Templates. These are document that describe the identifiers used in certiain contexts. For example, the sf0 game might decide that for PIMP IDs in the sf0 context the first subidentifier would always be the name of the team the player is on and the second is the name of the player. So the DTD would look like sfo::team,name and the PIMP ID for that context would be sfo::existenz,gxp.

0 vote(s)

Terms

(none yet)

1 comment(s)

1! 1! 1!
posted by mock piratey turtle on July 23rd, 2006 12:56 AM

i dont really understand this task since i'm on (that artsy team). but you used me in an example and thats neat!

Here i am! here i am! here i am!