hashless?

mm one could be to return HTML + RDFa describing yourself. add a triple saying http://iandavis.com/id/me containstriplesonlyabouttheresourceandnoneaboutitselfasinformationresource

its up to clients to really care about the distinction, i personally know of no useful clients for the web of data that will visibly misbehave if a person is mistaken for a page.. so your you can certify to your customer your solution works well with "any" client

if one will come up which operates usefully on both people and pages and would benefit from making your distinction than those coding that client will definitely learn about your containstriplesonlyabouttheresourceandnoneaboutitselfasinformationresource and support it.

how about this ? :-)

as an alternative the post i pointed you earlier (the one about 203 406) did actually contain an answer i believe.  406 is perfect IMO .. I'd say a client which will care to make the distinction would learn to support it as in my previous example.