[foaf-protocols] what if
kidehen at openlinksw.com
Mon Jul 19 02:43:41 CEST 2010
> Bruno Harbulot wrote:
>> On 18/07/2010 22:59, Seth Russell wrote:
>>> On Sun, Jul 18, 2010 at 2:17 PM, Bruno Harbulot
>>> <Bruno.Harbulot at manchester.ac.uk
>>> <mailto:Bruno.Harbulot at manchester.ac.uk>> wrote:
>>> As an uploader of the document, you might not be able to control the
>>> I think "the document" would need to be created by a server process and
>>> not just uploaded or FTPd. It then is served by a process like PHP
>>> which knows that it must transmit the key in the header.
>> Why not? What produces the representation is not the business of the
>> client. Whether a representation was uploaded via FTP or if it's
>> generated on-demand by a script shouldn't change anything about the
>> architecture of the web, as far as I know.
>> When we looked at signing RDF, it could have been possible to sign parts
>> of an XML/RDF document locally with my private key and then upload it.
>> Nothing wrong with that (apart from the fact XML Sig and XML/RDF don't
>> work well together, but that's a different topic).
>> The problem is that if we start putting things that belong to what's
>> within the document into custom HTTP headers, where do we stop? Why not
>> put the whole RDF/XML within a custom header, leaving the entity be in
>> whichever format it wants... Sure that would solve the problem, that's
>> just not what HTTP headers are for.
> another very valid point - well said Bruno
Yes, but do note, there is a vocabulary for HTTP . All worth
revisiting at the right time :-)
> foaf-protocols mailing list
> foaf-protocols at lists.foaf-project.org
President & CEO
More information about the foaf-protocols