recurring action: starttime and subsequent frequency formatting convention
recurring action: starttime and subsequent frequency formatting convention I am building a service where users will be able to register a payment-plan that initiates at any given date and recurs at any given frequency. For the sake of generalisation, I consider this to be a recurrent action with a starting time. Since the date and frequency are determined by third parties, I want to define a format for a string that describes both starting-time and frequency for storing in a database in a way that ensures maximum compatibilty with parties and interpreting functions, yet is simple and concise in its expression. Since the granularity only needs to be on a day-to-day-basis, I am thinking of the following format: YYYY/MM/DD%F with a concrete example being: 2018/01/01%1M, signifying an initial payment at the first of January 2018 with a recurring payment every 1 month. Are there any convetions for doing this, ISO standards, best practices, etc.? And do you foresee any caveats in my proposed...