Re: Revised MIME and Web product page

Thanks this is terrific. I'm particularly grateful for several reasons 
including: 1) very timely as input to F2F planning and agenda munging and 
2) a good yardstick against which to measure your recent draft document(s).

I also appreciate your taking the trouble to do the checkins in CVS. 
Mostly, it all looked good, with just a couple of glitches that I am in the 
process of taking care of:

* The box at the bottom with links to dated versions needed updating. I've 
done that.

* The dated version at 
http://www.w3.org/2001/tag/products/mimeweb-2011-12-21.html is not 
world-readable. I've but a request in on the #sysreq IRC channel to have 
that fixed, but it's after hours and I'm not sure whether it will be 
noticed tonight. If not, I'm sure Yves can fix it when he has a chance.

Thank you again.

Noah

On 12/21/2011 6:06 PM, Larry Masinter wrote:
> www.w3.org/2001/tag/products/mimeweb.html  updated to be more realistic ...
>
> I am more confident of an achievable milestone now that I have a better sense of where the MIME discussions belong in the broader context of extensibility mechanisms, evolution, reference to unstable or contested specifications, etc.
>
> My hopes are that the MIME discussions can proceed independently of the work on registries (and "Happy Iana") in generally, so  that we can stabilize and publish our MIME recommendations to meet our published goals, even if some of the other work proves difficult and is delayed.
>
> Larry
>
>
> -----Original Message-----
> From: Noah Mendelsohn [mailto:nrm@arcanedomain.com]
> Sent: Tuesday, December 20, 2011 7:21 PM
> To: Larry Masinter
> Cc: Jonathan A Rees; www-tag@w3.org
> Subject: Re: evolution, mime, registration document posted
>
> Larry,
>
> Thank you for the hard work on this. My impression is that there's enough here that we shouldn't expect TAG members to have read it in the few days since you've posted it, so my inclination is not to schedule formal review on this week's teleconference.  Also, the fact that ACTION-531 is not marked PENDING REVIEW, and that you've indicated that edits are happening daily, suggests that there is not a stable base for discussion just yet anyway. If we have some time at the end of tomorrow's agenda, we can always discuss this informally.
>
> Suggestion: please set a target date of around the end of this week for freezing a version that we can discuss during the F2F. Especially with the holidays coming, I feel we need to give people more than a few days for reviewing something of this length and scope.
>
> The other concern, which I've note elsewhere, is that I'm somewhat reluctant to have detailed discussion of this draft until we've done a bit to refocus the product page [1]. The product page should outline the scope of our work on MIME, and set out success criteria for the draft; we should review the draft in that context, I think.
>
> Thank you again for hard work this represents, and also for checking it in with CVS (which is at best an acquired taste).
>
> Noah
>
> [1] http://www.w3.org/2001/tag/products/mimeweb.html
>
>
>
> On 12/19/2011 7:16 PM, Larry Masinter wrote:
>> I put the document I've been working on (evolution, registries and MIME), into TAG space.
>>
>>
>> http://www.w3.org/2001/tag/2011/12/evolution/evolution-mime-registries
>> .html
>>
>> the document isn't stable (I'm editing it every day).
>>
>>
>> Looking at
>> http://www.w3.org/2001/tag/2011/12/uddp/
>>
>>
>> I would align the two documents with this formulation (which won't make sense if you haven't read 'evolution'):
>>
>> RDF is an extensible (abstract) language for making assertions, and for which there are several concrete languages which encode and use the abstract framework.
>>
>>    RDF chose "use URI" as the extensibility method for identifiers in
>> RDF's subject, predicate, and object protocol elements (when those are not blank or literals.) The protocol element is called 'uriRef' in RDF, and I'll refer to it as the "RDF#uriRef" protocol element.
>>
>> UDDP supplies  methods  for supplying additional information can be associated with (some) RDF#uriRefs, and for accessing that information, in the form of a document.
>>
>> (The methods in the document posted are available for RDF#uriRefs
>> which use a scheme that is based on HTTP and thus has status codes, or
>> those that have a fragment identifier and a stem which can be used to
>> retrieve a representation for which the fragment identifier is
>> meaningful.)
>>
>> Other languages and protocols (besides the RDF based ones above) may choose to use the RDF#uriRef protocol element in a compatible way.
>>
>> RDF#uriRef as a protocol element shares many of the concerns discussed within the section labeled "Web Evolution: References between Specifications".
>> Since the reference associated with a uriRef may change over time, and as to the decision as to the applicability of the document obtained using UDDP at a later date is left to the implementation.
>>
>> Larry
>>
>>
>>
>

Received on Thursday, 22 December 2011 00:03:37 UTC