TAG Issues List

w3cMediaType-1: Should W3C WGs define their own media types? [link to this issue]

What are the general guidelines or policies (if any) for W3C working groups in defining their own media types? Should they be defining them at all?

Request concerning

W3C Data Formats

Discussion history

22 Apr 2002, 29 Apr 2002, 20 May 2002, 17 Jun 2002, 8 Jul 2002, 25 Jul 2006

Categories

Transition history

raised on 9 Jan 2002 by Mark Baker , on behalf of XML Protocol WG

accepted on 21 Jan 2002

Background, proposals, threads, notes

• Tim Bray comments on the architecture doc about namespaces and media types.
• Message from Joseph Reagle about three bits on MediaTypes and IANA .
• Comments from Mark Baker on XSLT and namespace dispatch .
• Forward from Simon St. Laurent about ID: MediaFeature xmlns .
• Heads-up from Mark Nottingham about XForms document in last call and relation to media types issues.
• How to Register an IANA Media Type , Joseph Reagle
• 18 Dec 2004: IETF approves new media type registration process .
• 25 Feb 2004: New registration process description from Martin Duerst

namespaceDocument-8: What should a "namespace document" look like? [link to this issue]

The section on namespaces in Web Architecture from 50,000 feet states: "The namespace document (with the namespace URI) is a place for the language publisher to keep definitive material about a namespace. Schema languages are ideal for this." Tim Bray disagrees.

Request concerning

Web Architecture from 50,000 feet

Discussion history

25 Mar 2002, 1 Apr 2002, 8 Apr 2002, 5 May 2002, 24 Sep 2002, 25 Sep 2002, 18 Nov 2002, 9 Dec 2002, 16 Dec 2002, 6 Jan 2003, 13 Jan 2003, 6 Feb 2003, 17 Feb 2003, 24 Feb 2003, 24 Mar 2003, 7 Apr 2003, 14 Apr 2003, 23 Jun 2003, 8 Sep 2003, 15 Sep 2003, 5 Dec 2002, 26 Jan 2004, 2 Mar 2004, 14 May 2004, 5 Apr 2005, 16 Jun 2005, 12 Jul 2005, 30 Aug 2005, 22 Sep 2005, 11 Oct 2005, 1 Nov 2005, 8 Nov 2005, 6 Dec 2005, 10 Jan 2006, 21 Feb 2006, 2 May 2006, 14 Jun 2006, 5 Oct 2006, 14 Nov 2006, 13 Dec 2006, 6 Mar 2007

Transition history

raised on 14 Jan 2002 by Tim Bray , on behalf of TAG

accepted on 4 Feb 2002

Background, proposals, threads, notes

• XML Schema Part 1: Structures
• See comments from Patrick Stickler that "namespaces are strictly punctuation." and reply from Larry Masinter .
• See 14 Theses from Tim Bray
• See thread on RDF and RDDL from Stuart Williams.
• See RDF in HTML from Tim Berners-Lee
• Emails ( 1 , 2 ) from James Clark to xml-dev about schemas, as suggested by Tim Bray . See also Email from James about Relax NG and W3C XML Schema
• Guidelines for the Use of XML within IETF Protocols , section 4.9. See also ietf-xml-use mailing list in case the document disappears.
• RDDL Challenge
• RDDL Proposal from Tim Bray
• RDDL Proposal from Chris Wilper
• RDDL Proposal from Jonathan Borden
• Examples of RDDL in RDF from TBL
• RDDL Proposal from Micah Dubinko
• RDDL proposal from Sandro Hawke
• Summary by Norm of RDDL Proposals.
• RDDL Proposal from Garrett Wilson
• 1 Jun 2003 draft of RDDL
• Namespace URIs should be dereferencable (to find useful explanatory material) ( 12 Feb ftf meeting )
• Refer to draft TAG opinion from Tim Bray on the use of URNs for namespace names.
• RDDL2 Background from Tim Bray.
• grokRDDL.xsl mapping to RDF from Dan Connolly.
• namespaceDocument-8 Notes from Norm Walsh (24 June 2005)
• Associating Resources with Namespaces from Norm Walsh
• Gleaning Resource Descriptions from Dialects of Languages (GRDDL)

Action history

HTTPSubstrate-16: Should HTTP be used as a substrate protocol? Does W3C agree with RFC 3205? [link to this issue]

From Mark Nottingham:

The IETF has recently published RFC3205, "On the use of HTTP as a Substrate" [1] as Best Current Practice.

This document makes a number of recommendations regarding the use of HTTP. Some are reasonable, such as guidelines about what kinds of scenarios the HTTP is most useful in, how to use media types and methods to extend the HTTP, etc. However, it also bases a number of recommendations on a fuzzily-defined concept of 'traditional use' of the HTTP. These directives may seriously limit the future potential of the Web, effectively freezing its capability to common practice in 2001."

Request concerning

RFC3205

Discussion history

30 Jun 2003, 12 May 2004, 7 Feb 2005, 21 Sep 2005

Transition history

raised on 24 Mar 2002 by Mark Nottingham

accepted on 1 Apr 2002

Background, proposals, threads, notes

• Response from Randy Hall to IETF
• Message from Roy Fielding
• Propoposed criticsm of RFC3205 from TBL.
• Email from Mark Baker on tunneling as a property of the application.
• See message from Larry Masinter w.r.t. Web services.

deferred on 12 May 2004

The TAG decided to defer this issue pending any attempt to enforce RFC3205.

Action history

IRIEverywhere-27: Should W3C specifications start promoting IRIs? [link to this issue]

The XML Core WG would like TAG input on whether the desirability of adopting IRIs into the web infrastructure early outweighs the anticipated disruption of legacy systems.

The XML Core WG would also like TAG input on the wisdom of early adoption given the "Internet Draft" status of the IRI draft . So far adoption has relied on "copy and paste", but there is potential for these definitions to get out of sync.

Request concerning

• XML
• XML 1.1
• [Internet Draft] IRI draft

Discussion history

28 Oct 2002, 11 Nov 2002, 18 Nov 2002, 27 Jan 2003, 6 Feb 2003, 31 Mar 2003, 7 Apr 2003, 14 Apr 2003, 28 Apr 2003, 14 May 2004, 21 Sep 2005, 13 Dec 2005, 23 Jan 2007, 12 Feb 2007, 26 Mar 2007

Transition history

raised on 9 Oct 2002 by Jonathan Marsh , on behalf of XML Core WG

accepted on 28 Oct 2002

Background, proposals, threads, notes

• URIEquivalence-15
• Email from Larry Masinter about URI BOF minutes from IETF56
• Summary email from Tim Bray
• Comments from Ray Whitmer about IRIs in the DOM (see same email with inclusion . See 1.3.2 DOM URIs in 7 May 2003 DOM 3 Core draft
• RFC3490: Internationalizing Domain Names in Applications (IDNA)
• See TB's proposed step forward on IRI 27.
• RFC 3987 is a Proposed Standard

Action history

binaryXML-30: Standardize a "binary XML" format? [link to this issue]

Given that binary infosets (currently, binary PSVIs ) is what I work on daily and that I am currently investigating ways in which they could fit naturally into the web (content-coding registration for instance), I would be very interested in knowing what -- if anything at this point -- the TAG thinks of them and of how they could best fit in.

Request concerning

XML

Discussion history

2 Dec 2002, 13 Jan 2003, 27 Jan 2003, 6 Feb 2003, 17 Feb 2003, 12 May 2004, 7 Feb 2005, 28 Feb 2005, 15 Mar 2005, 5 Apr 2005, 12 Apr 2005, 26 Apr 2005, 3 May 2005, 10 May 2005

Transition history

raised on 9 Oct 2002 by Robin Berjon

accepted on 2 Dec 2002

Background, proposals, threads, notes

• See explanation scenario from DC ; a typical conversation about binary XML.
• Rationale from Robin Berjon
• XML binary compression progress: X3D, XFSP project from Don Brutzman.
• OGC is another customer for binary XML.
• Binary XML Workshop Minutes
• Summary from Chris .
• XML Binary Characterization Use Cases .
• TAG opinion on XML Binary Format , 24 May 2005.

deferred on 12 May 2004

W3C has chartered the XML Binary Characterization Working Group to address this issue. The TAG anticipates reviewing the WG's deliverables in this area.

Action history

mixedUIXMLNamespace-33: Composability for user interface-oriented XML namespaces [link to this issue]

Raised by the TAG as an offshoot of mixedNamespaceMeaning-13 .

Request concerning

• XHTML
• MathML
• SVG
• XForms
• SMIL
• other user interface-oriented applications

Discussion history

6 Feb 2003, 2 Mar 2004, 7 Feb 2005, 21 Sep 2005, 1 Nov 2005, 10 Jan 2006

Transition history

raised on 6 Feb 2003 by TAG, on behalf of TAG

accepted on 6 Feb 2003

Background, proposals, threads, notes

• Offshoot of mixedNamespaceMeaning-13
• An XHTML + MathML + SVG Profile
• W3C Workshop on Web Applications and Compound Documents
• W3C Compound Document Formats Working Group

deferred on 1 Nov 2005

Pend this issue until significant progress is made by the W3C Compound Document Formats Working Group in a public working draft.

Action history

xmlFunctions-34: XML Transformation and composability (e.g., XSLT, XInclude, Encryption) [link to this issue]

Raised by the TAG as an offshoot of mixedNamespaceMeaning-13 .

Request concerning

• XSLT
• XInclude
• Encryption
• other specifications that involve transformations of XML content

Discussion history

6 Feb 2003, 21 Sep 2005, 31 Jan 2006, 7 Feb 2006, 18 Apr 2006, 25 Apr 2006, 11 Dec 2006, 30 Jan 2007, 11 Jun 2007

Transition history

raised on 6 Feb 2003 by TAG, on behalf of TAG

accepted on 6 Feb 2003

Background, proposals, threads, notes

• Offshoot of mixedNamespaceMeaning-13
• The Interpretation of XML documents from TBL.
• The elaborated infoset: A proposal

Action history

RDFinXHTML-35: Syntax and semantics for embedding RDF in XHTML [link to this issue]

Raised by the TAG as an offshoot of mixedNamespaceMeaning-13 .

Request concerning

• RDF
• XHTML

Discussion history

6 Feb 2003, 14 May 2004, 22 Feb 2005, 28 Feb 2005, 13 Dec 2005, 14 Jun 2006, 13 Dec 2006, 12 Feb 2007

Transition history

raised on 6 Feb 2003 by TAG, on behalf of TAG

accepted on 6 Feb 2003

Background, proposals, threads, notes

• Offshoot of mixedNamespaceMeaning-13
• namespaceDocument-8
• Using RDF/XML with HTML and XHTML
• Some discussion about approaches
• "Crisp" statement of the problem from Dan Connolly
• Email from M. Ishikawa on using modular namespaces (MNS)
• RDF in XHTML summary by TBL.
• GRDDL: Gleaning Resource Descriptions from Dialects of Languages by Dan Connolly and Dominique Hazael-Massieux.

deferred on 13 Dec 2006

The TAG decided to defer this issue pending work by the GRDDL WG and/or the RDFa/HTML/SemWeb-deployment WGs.

Action history

siteData-36: Web site metadata improving on robots.txt, w3c/p3p and favicon etc. [link to this issue]

The architecture of the web is that the space of identifiers on an http web site is owned by the owner of the domain name. The owner, "publisher", is free to allocate identifiers and define how they are served.

Any variation from this breaks the web. The problem is that there are some conventions for the identifies on websites, that

• /robots.txt is a file controlling robot access
• /w3c/p3p is where you put a privacy policy
• /favico is an icon representative of the web site

and who knows what others. There is of course no list available of the assumptions different groups and manufacturers have used.

More in the original message from TBL .

Request concerning

URI space

Discussion history

24 Feb 2003, 8 Oct 2003, 5 Jan 2004, 12 Jan 2004, 22 Feb 2005, 13 Dec 2005, 2 May 2006, 9 Jan 2007

Transition history

raised on 10 Feb 2003 by Tim Berners-Lee , on behalf of TAG

accepted on 24 Feb 2003

Background, proposals, threads, notes

• Note: Defining a Web Site .
• Sitemap protocol .

Action history

abstractComponentRefs-37: Definition of abstract components with namespace names and frag ids [link to this issue]

Is it wise to use fragment IDs for identifying abstract components within a namespace, even though it is the most natural and convenient mechanism? Is there another mechanism that would be preferable?

Request concerning

• Namespaces in XML
• WSDL

Discussion history

24 Mar 2003, 14 Apr 2003, 5 May 2003, 23 Jun 2003, 8 Oct 2003, 20 Oct 2003, 2 Mar 2004, 22 Feb 2005, 3 May 2005, 16 Jun 2005, 21 Sep 2005, 25 Oct 2005, 1 Nov 2005, 16 May 2006, 14 Jun 2006

Transition history

raised on 3 Feb 2003 by Jonathan Marsh , on behalf of WSD WG

accepted on 24 Mar 2003

Background, proposals, threads, notes

• rdfmsQnameUriMapping-6 , namespaceDocument-8
• Email from Tim Bray about relation to RDDL.
• Email from Paul Cotton about Schema WG response to the WSD WG questions about Schema Component Designators
• Email from Noah Mendelsohn about distinction between schema components and schema documents.
• Email from Larry Masinter on relation to WebDAV to providing access to metadata.
• Summary of options from David Orchard
• Draft summary
• Comments from MSM on behalf of Schema WG
• "XML Schema: Component Designators" specification published by the W3C XML Schema WG.
• Draft finding Abstract Component References

Action history

rdfURIMeaning-39: Meaning of URIs in RDF documents [link to this issue]

TBL: "The community needs:

1. A concise statement of the above architectural elements from different specs in one place, written in terms which the ontology community will understand, with pointers to the relevant specifications.
2. Some outline guidance on specific questions brought up in email questions.

This includes:

• Is a given inference engine expected to take into account a given document under given circumstances?
• how does one avoid having to commit to things one does not trust?

There may be some need to clarify frequent misunderstandings by making some things clear."

Request concerning

• URI
• RDF
• OWL
• HTTP

Discussion history

18 Aug 2003, 15 Sep 2003, 22 Feb 2003, 21 Sep 2005, 13 Dec 2005

Transition history

raised on 13 Jul 2003 by Tim Berners-Lee , on behalf of Semantic Web CG

accepted on 18 Aug 2003

Background, proposals, threads, notes

• Some background summarized by DanC
• Mailing list for discussions on this issue: public-sw-meaning ( archive )

Action history

URIGoodPractice-40: What are good practices for URI construction? [link to this issue]

Some issues:

• Fragment identifier syntax
• Related issue: URI Squatting?

Request concerning

URI

Discussion history

20 Oct 2003, 14 May 2004, 22 Feb 2005, 21 Sep 2005, 13 Dec 2005

Transition history

raised on 16 Oct 2003 by David Orchard , on behalf of TAG

accepted on 20 Oct 2003

Background, proposals, threads, notes

• abstractComponentRefs-37
• Well Designed URLs are Beautiful!

Action history

XMLVersioning-41: What are good practices for designing extensible XML languages and for handling versioning? [link to this issue]

What are good practices for designing extensible XML languages and for handling versioning?

Request concerning

XML

Discussion history

3 Nov 2003, 10 Nov 2003, 15 Nov 2003, 2 Mar 2003, 14 May 2004, 14 Feb 2005, 21 Sep 2005, 22 Sep 2005, 8 Nov 2005, 5 Dec 2005, 14 Feb 2006, 27 Feb 2006, 3 Mar 2006, 12 Jun 2006, 18 Jul 2006, 25 Jul 2006, 8 Aug 2006, 29 Aug 2006, 5 Sep 2006, 4 Oct 2006, 5 Oct 2006, 5 Oct 2006, 12 Dec 2006, 12 Dec 2006, 16 Apr 2007, 23 Apr 2007, 30 Apr 2007, 14 May 2007, 30 May 2007, 30 May 2007, 31 May 2007, 25 Jun 2007

Transition history

raised on 27 Jun 2003 by David Orchard , on behalf of TAG

accepted on 3 Nov 2003

Background, proposals, threads, notes

• Draft finding from DO and NW part 1 , part 2
• Text proposed by DO and NW for Arch Doc
• Instance diagram

Action history

ultimateQuestion-42: What is the answer to life, the universe, and everything. [link to this issue]

This "issue" collects all discussions relevant to Web architecture that are not directly related to any other issue.

Request concerning

The Hitch Hiker's Guide to the Galaxy

Discussion history

15 Nov 2003

Transition history

raised on 15 Nov 2003 by Tim Berners-Lee , on behalf of TAG

accepted on 15 Nov 2003

Background, proposals, threads, notes

• Wikipedia entry on issue 42
• Google Calculator; cf 6*9
• - - - - - - - - - -
• Semantic Web Architecture: 16 Jun 2005 , 22 Sep 2005 , 13 Dec 2006
• Self-describing Web: 06 Dec 2005 , 27 Feb 2006 , 6 Mar 2007 , 1 Jun 2007 .
• State in Web application design : 21 Feb 2006 , 28 Mar 2006 , 25 Apr 2006 , 9 May 2006 , 6 June 2006 , 13 June 2006 , 26 Sep 2006
• Security/Authentication: 15 Jun 2005 , 5 Jul 2005 , 20 Sep 2005 , 8 Nov 2005 , 24 Jan 2006 , 21 Mar 2006 , 11 Apr 2006 , 25 Apr 2006 , 13 Jun 2006
• CURIEs: 30 May 2006 , 13 Jun 2006 , 27 Jun 2006 , 26 Feb 2007 , 19 Mar 2007 , 2 Apr 2007 . See abbreviatedURIs-56 for continuing discussion.
• Device description repositories: 6 Jun 2006 , 27 Jun 2006
• New and changing media types: 18 Jul 2006 , 25 Jul 2006 .
• Naming and Virtual Worlds 18 June 2007

Action history