WhiteflagProtocol/whiteflag-standard

Issues

• Add functionality for naming objects

  #19 opened a year ago by ts5746
  0

• Ambiguous specification of the Verification Data field in Authentication Messages

  #18 opened 3 years ago by ts5746
  0

• DID architecture compliance

  #17 opened 4 years ago by ts5746
  0

• Clarify the encoding of the sign bit in coordinates

  #16 opened 4 years ago by ts5746
  0

• Review of potential negative implications

  #15 opened 5 years ago by ts5746
  1

• Add vectors to describe routes

  #14 opened 5 years ago by ts5746
  0

• Add polygon object area type

  #13 opened 5 years ago by ts5746
  0

• Confirm Protective Signs for Cultural Heritrage Sites

  #9 opened 5 years ago by ts5746
  0

• Add Protective Sign for Schools

  #8 opened 5 years ago by ts5746
  1

• General clarifications and improvements

  #4 opened 5 years ago by ts5746
  0

• Clarify usage of test messages

  #5 opened 5 years ago by ts5746
  0

• More efficient DateTime field

  #2 opened 5 years ago by ts5746
  0

• Free Text messages encoding

  #3 opened 5 years ago by ts5746
  0

• Add (in)complete indicator to original message when additional information may follow

  #6 opened 5 years ago by ts5746
  0

• Verify referenced internet resource

  #7 opened 5 years ago by ts5746
  0

• Add indicator for duplicate information

  #10 opened 5 years ago by ts5746
  1

• Add reference type for unclear messages

  #11 opened 5 years ago by ts5746
  0

• Blockchain network migration protocol

  #12 opened 5 years ago by ts5746
  1

• Do not use captital case for properties in message schema

  #1 opened 5 years ago by ts5746
  1