<trackbot> Date: 30 November 2012

<bblfish> hi

<scribe> scribenick: deiu

<bblfish> Agenda: Cleaning up the arguments for Hash http://www.w3.org/2005/Incubator/webid/wiki/WebID_Definition/hash

http://www.w3.org/2005/Incubator/webid/wiki/WebID_Definition/hash

Alex said that we should have requirements, not use-cases.

<scor> deiu: we're trying to move on with the spec so we can switch a WG

<scor> ... and we should not waste time

<scor> ... re Apple KeyChain: we cannot change the spec because one application. not how it should work. applications should follow the spec

<scor> bblfish: can we convince ALex and deiu to go with the SHOULD

http://www.w3.org/2005/Incubator/webid/wiki/WebID_Definition/Requirements

<scor> bblfish: Alex had his own requirements. I asked if he was able to accept the SHOULD. I argued all his requirements can match with SHOULD

<scor> bblfish: would have been nice if Alex was here on the call

<scor> STRAW POLL: 1. MUST be a an HTTP(s) hash (#) URI

<bblfish> STRAW POLL: 1. MUST be a an HTTP(s) hash (#) URI

<bblfish> -1

<MacTed> -1

<scor> -1

0

<bergi> -1

<scor> STRAW POLL: 2. MUST be HTTP(S) uri and SHOULD be an HTTP(s) hash (#) URI

<bblfish> +1

+1

<bergi> +1

<scor> +0.5

<MacTed> -0.5

<melvster> +1

<melvster> why does it say HTTP first then HTTP(S) 2nd?

<scor> STRAW POLL: 3. MUST be an HTTP(s) URI

<MacTed> melvster - typo.

-1

<MacTed> +1

<bblfish> +0.2

<scor> +1

<bergi> +1

<scor> melvster: want to vote?

<melvster> 0

<melvster> sorry was thinking :)

<MacTed> 3. MUST be HTTP uri and MAY be an HTTP(s) hash (#) URI

<scor> melvster: want to give your vote for option 1. MUST be a an HTTP(s) hash (#) URI ?

<melvster> scor: 0 on that one

<scor> melvster: thanks

<bblfish> I'll come right back just continue...

<scor> Straw poll totals: MUST = -3 SHOULD = +6 Open = +5.2

<MacTed> it sounds like deiu's theory is that "MUST hash" equates to "303s don't happen" and I don't agree with that by any stretch

Hash URIs make it easy to explain the difference between the Profile document ( a Information Resource from WebArch ) where the description of the agent resides and the user identifier as in the picture in the spec.

Which opens the door to redirects that must be well documented in the spec.

<bblfish> foaf:knows#it

<bblfish> http://sdkfjslkdfsdfsdf/sdfsdfsd.ttl

<bblfish> http://sdkfjslkdfsdfsdf.onion/sdfsdfsd.ttl

<scor> http://www.w3.org/2005/Incubator/webid/wiki/WebID_Definition/hash#Poll_results

Actually, I am changing my vote for 3) from -1 to -0.5

<bblfish> see you next week

<bblfish> where we resolve this issue

it's not an issue

it's just a straw poll

<bblfish> sorry I wrote that out on 2 lines

<scor> deiu: bblfish said next week

<bblfish> the two lines toegther say: next week we can resolve this issue

<bblfish> :-)

ah

trackbot, end meeting

This is scribe.perl Revision: 1.137  of Date: 2012/09/20 20:19:01  
Check for newer version at http://dev.w3.org/cvsweb/~checkout~/2002/scribe/

Guessing input format: RRSAgent_Text_Format (score 1.00)

Succeeded: s/SHOUDL/SHOULD/
Succeeded: s/PROPOSAL/STRAW POLL/
Succeeded: s/MUST be HTTP uri/MUST be HTTP(S) uri/
Found ScribeNick: deiu
Inferring Scribes: deiu

WARNING: No "Topic:" lines found.

Default Present: Bob_Powers, bblfish, MacTed, deiu, scor, bergi
Present: Bob_Powers bblfish MacTed deiu scor bergi
Found Date: 30 Nov 2012
Guessing minutes URL: http://www.w3.org/2012/11/30-webid-minutes.html
People with action items: 

WARNING: Input appears to use implicit continuation lines.
You may need the "-implicitContinuations" option.


WARNING: No "Topic: ..." lines found!  
Resulting HTML may have an empty (invalid) <ol>...</ol>.

Explanation: "Topic: ..." lines are used to indicate the start of 
new discussion topics or agenda items, such as:
<dbooth> Topic: Review of Amy's report