polyglot to rec? the term "normative"

<Noah> LM: There was formal objection to moving the polyglot doc to REC, with the objection that it shouldn't be normative

<Noah> LM: Suggestion was Note rather than REC. I think the WG has the scope to decide that if they can come to consensus.

<Noah> LM: That said, the nature of the arguments raised some broader issues the TAG might clarify:

<Noah> LM: E.g. whether doc has had sufficient review? What if docs might conflict with other docs? What it means for a document to be normative and make normative reqts?

<Noah> LM: Might SHOULD/MUST/MAY apply outside scope of document.

<Noah> LM: Could send my thoughts to TAG list. I'm suggesting we focus not primarily on the decision directly, but on clarifying the criteria, in part to help inform the Director should the issue come to him.

<Noah> "The following sections discuss the management of errors and the process for making normative changes to a Recommendation."

<Noah> A correction is first "proposed" by the Working Group. A correction becomes normative -- of equal status as the text in the published Recommendation -- through one of the processes described below.

lm: i'll take an action to come up with a summary of topics in the next couple of days, if people want to discuss this next week

(Tim joins)

moving Jan TAG meeting

<Noah> RESOLUTION: The TAG will meet in Cambridge, MA 14-16 (Mon-Wed) January 2013.

<ht> March is still blocked for me

<ht> Let me check earliest date I could make

RESOLUTION: The TAG will tenatively move its March 2013 meeting to Adobe in San Jose

<Noah> Rumor is 19-21 March.

<ht> Right, I can't make it until 9 April

The term Normative

<Noah> TBL: What are the concerns?

<ht> +1 to talking about this after prep. material from Larry

<Noah> LM: What does it mean for a document or reference to be normative.

<Noah> LM: ...missed some other details..

<Noah> LM: There are details I'd like thijs

<Noah> TBL: To me, it's a relationship between specs. If you conform to a spec, then you also must conform to what it references normatively

<Noah> LM: One case that concerns me is overlap. What are the rules for normative specs overlapping.

<Noah> LM: Recommendations are from W3C, that happen to be prepared by WGs.

<Noah> LM: ...scribe is missing some points about community review...

<Noah> LM: Questions like that.

<Noah> TBL: That's a longer term thing, vs. dealing with this particular one.

<Noah> LM: I think the WG has scope to take next steps on this one. If a formal objection were to be lodged, we (and you as director) should (have good basis for responding)

<Zakim> Noah, you wanted to say we have a precedent on overlap

<ht> Meant as an endorsement

nm: there's a precedent with the authoring spec

lm: we have the precedent, we just don't have the policy

<Noah> NM: Right, agreement was reached that both HTML5 and Authoring spec are normative RECs, though overlapping. Disagreement is evidence of bug. I think that until bug is resolved, the rules say HTML5 wins.

<Noah> NM: TAG has standing request from Jeff to highlight technical/arch issues that should concern him

<Noah> NM: Larry has drafted an initial list for discussion

<Noah> LM: Five issues:

<Noah> LM 1) We did some work relating to Publishing and Linking that may be more general. Quoting Larry's note, which he is reading:

<Noah> "The TAG has been discussing areas where governance - the desire of legal, regulatory, administrative, or contractual relationships to regulate communication - affects web architecture. While W3C has ongoing efforts in privacy, security, accessibility and internationalization are oriented toward insuring that standards specified by W3C specifications can accommodate at least some of the

<Noah> governance requirements, there is a need to do more. For example, the "publishing and linking" FPWD from the TAG addresses some of the issues of linking vs. copying vs. embedding that have been at the center of some controversies with regard to the application of governance around copyright, censorship of unwanted material, identity, logging, and many other issues. While the TAG discussed a

ashok: at TPAC, we had lunch with the AB, and this question came up, and Steve Zilles (Either speaking for himself or the AB), thought it would be a good idea if we went further in this direction.
... the question was: should we be doing more work on web/governance was?

<Noah> Noah: What is it we need to alert Jeff about?

nm: this may be good work for the TAG, but what do we need to alert jeff about?

LM: the one i have this time for issue 1 is censorship

<Noah> LM 2. Security is an arms race, and the bad guys are winning. (and we aren't doing security reviews early enough or thoroughly enough before RECs are baked)

<Noah> NM: Don't you think the right way to look at this is that the Security Activity "owns" this, with whatever help from the TAG

<Noah> LM: There are resource issues

<Noah> Web Application Security Working Group

<Noah> Web Cryptography Working Group

this is more a matter of publishing documents which open security exploits

<Noah> AM: Do these cover the ground?

<Noah> LM: The issue is, it's easy to publish a spec that opens unanticipated security problems. Working groups chartered to produce "new locks for new doors", while not checking that we're unlocking the old doors.

<Noah> NM: Are we telling Jeff "There's a problem that specifications may be have or be causing security problems not covered by existing WGs, and that are not being suitably considered before the recs come out"

we recommend more security training? more security staff?

before WDs are implemented and deployed

<Noah> NM: Are there other TAG members who think we should put it on the list for Jeff?

<Noah> "As web capabilities expand, the boundary between "Web" and "not web" continues to blur, and the overlap between W3C and IETF also becomes more problematic. The definition of what the "Web" is compared to other internet applications requires a more principled discussion and coordination. This applies in general to a wide variety of areas (WebRTC RTCWeb) but specifically for two technologies

<Noah> fundamental to the web but work in the IETF without significant W3C involvement:"

<Noah> NM: Reads items 4-9 and invites expressions of interest from TAG members