isn't it nessesary to adding some prefix standard to prevent content validating by parsing?
this number could be an account/transaction/block or even an phone/zip number or encoded gps location.
how could a jumpcenter find out what entity is behind this content without a declaration prefix?
entity parsing and validating doesn't work reliable this way or do i miss something here?
any takers here?
Is it about URIs?
alias is much more powerfull then just an uri/account/mails/phonenumbers shortener or stuff like this.
aliases could be also used as an mighty automation entity, e.g. to launch complete phonecalls,
sending a fax with an order confirmation, printing and sending invoices for goods bought
online, trigger db-events or even directing to gps location on interactive maps, if...we add
additional identifier fields to aliases. similar to http content-type. a content-type field could
be used for this. even if many of these examples could be done with other tools, why not
giving alias these functionality also if desired by developers.
