W3CTAG Issues List

Individual view

Other views: issues | types | states | concerning | open actions


This list received comments from 10 groups and 20 individuals.

Comments from groups

  1. I18N WG [1 issue ]
    1. charmodReview-17 : Request to review "Character Model for the Web" Last Call document [closed]
  2. Semantic Web CG [1 issue ]
    1. rdfURIMeaning-39 : Meaning of URIs in RDF documents [open]
  3. TAG [22 issues ]
    1. whenToUseGet-7 : (1) GET should be encouraged, not deprecated, in XForms (2) How to handle safe queries (New POST-like method? GET plus a body?) [open]
    2. namespaceDocument-8 : What should a "namespace document" look like? [open]
    3. xmlSW-10 : Should next version of XML be XML 1.0 - DTDs + namespaces + xml:base + the infoset? [closed]
    4. mixedNamespaceMeaning-13 : What is the meaning of a document composed of content in mixed namespaces? [closed]
    5. httpRange-14 : What is the range of the HTTP dereference function? [open]
    6. augmentedInfoset-22 : Infoset augmentation outside of PSVI? [closed]
    7. xlinkScope-23 : What is the scope of using XLink? [open]
    8. contentTypeOverride-24 : Can a specification include rules for overriding HTTP content type parameters? [closed]
    9. deepLinking-25 : What to say in defense of principle that deep linking is not an illegal act? [closed]
    10. contentPresentation-26 : Separation of semantic and presentational markup, to the extent possible, is architecturally sound. [open]
    11. fragmentInXML-28 : Use of fragment identifiers in XML [open]
    12. xmlIDSemantics-32 : How should the problem of identifying ID semantics in XML languages be addressed in the absence of a DTD? [open]
    13. mixedUIXMLNamespace-33 : Composability for user interface-oriented XML namespaces [open]
    14. xmlFunctions-34 : XML Transformation and composability (e.g., XSLT, XInclude, Encryption) [open]
    15. RDFinXHTML-35 : Syntax and semantics for embedding RDF in XHTML [open]
    16. siteData-36 : Web site metadata improving on robots.txt, w3c/p3p and favicon etc. [open]
    17. URIGoodPractice-40 : What are good practices for URI construction? [open]
    18. XMLVersioning-41 : What are good practices for designing extensible XML languages and for handling versioning? [open]
    19. ultimateQuestion-42 : What is the answer to life, the universe, and everything. [open]
    20. DerivedResources-43 : How are secondary resources derived? [open]
    21. xmlChunk-44 : Chunk of XML - Canonicalization and equality [closed]
    22. mediaTypeManagement-45 : What is the appropriate level of granularity of the media type mechanism? [open]
  4. UN/CEFACT ebTWG Architecture Group [1 issue ]
    1. uncefactLiaison-5 : Invitation to create liaison with UN/CEFACT ebTWG Architecture Group [closed]
  5. WSD WG [1 issue ]
    1. abstractComponentRefs-37 : Definition of abstract components with namespace names and frag ids [open]
  6. XForms WG [1 issue ]
    1. xformsReview-4 : Request to review XForms Last Call document [closed]
  7. XKMS WG [1 issue ]
    1. qnameAsId-18 : Is it ok to use Qnames as Identifiers? [closed]
  8. XML Core WG [2 issues ]
    1. IRIEverywhere-27 : Should W3C specifications start promoting IRIs? [open]
    2. nameSpaceState-48 : Adding terms to a namespace [closed]
  9. XML Protocol WG [4 issues ]
    1. w3cMediaType-1 : Should W3C WGs define their own media types? [open]
    2. customMediaType-2 : What commonality should there be among W3C media types? [closed]
    3. nsMediaType-3 : Relationship between media types and namespaces? [closed]
    4. RFC3023Charset-21 : Do all "shoulds" of RFC 3023 section 7.1 apply? [closed]
  10. XML Protocol WG [1 issue ]
    1. xml11Names-46 : Impact of changes to XML 1.1 on other XML Specifications [open]

Comments from individuals

  1. Aaron Swartz [1 issue ]
    1. uriMediaType-9 : Why does the Web use mime types and not URIs? [closed]
  2. Dan Connolly [2 issues ]
    1. standardizedFieldValues-51 : Squatting on link relationship names, x-tokens, registries, and URI-based extensibility [open]
    2. passwordsInTheClear-52 : Sending passwords in the clear [open]
  3. Henry Thompson [1 issue ]
    1. URNsAndRegistries-50 : URIs, URNs, "location independent" naming systems and associated registries for naming on the Web [open]
  4. Jonathan Borden [1 issue ]
    1. rdfmsQnameUriMapping-6 : Algorithm for creating a URI from a QName? [closed]
  5. Joseph Reagle [2 issues ]
    1. URIEquivalence-15 : When are two URI variants considered equivalent? [closed]
    2. qnameAsId-18 : Is it ok to use Qnames as Identifiers? [closed]
  6. Julian Reschke [1 issue ]
    1. putMediaType-38 : Relation of HTTP PUT to GET, and whether client headers to server are authoritative [closed]
  7. Mark Baker [5 issues ]
    1. w3cMediaType-1 : Should W3C WGs define their own media types? [open]
    2. customMediaType-2 : What commonality should there be among W3C media types? [closed]
    3. nsMediaType-3 : Relationship between media types and namespaces? [closed]
    4. RFC3023Charset-21 : Do all "shoulds" of RFC 3023 section 7.1 apply? [closed]
    5. endPointRefs-47 : WS-Addressing SOAP binding & app protocols [open]
  8. Mark Nottingham [2 issues ]
    1. HTTPSubstrate-16 : Should HTTP be used as a substrate protocol? Does W3C agree with RFC 3205? [open]
    2. xml11Names-46 : Impact of changes to XML 1.1 on other XML Specifications [open]
  9. Noah Mendelsohn [1 issue ]
    1. schemeProtocols-49 : Relationship of URI schemes to protocols and operations [open]
  10. Ossi Nykänen [1 issue ]
    1. metadataInURI-31 : Should metadata (e.g., versioning information) be encoded in URIs? [closed]
  11. Paul Grosso [1 issue ]
    1. xmlProfiles-29 : When, whither and how to profile W3C specifications in the XML Family [closed]
  12. Paul Prescod [1 issue ]
    1. soapRPCURI-11 : What is the appropriate relationship between SOAP RPC and the Web's reliance on URIs? [closed]
  13. Rick Jelliffe [1 issue ]
    1. xmlAsText-12 : Do proposed changes to XML 1.1 ignore Unicode constraints? [closed]
  14. Rob Lanphier [1 issue ]
    1. errorHandling-20 : What should specifications say about error handling? [closed]
  15. Robin Berjon [1 issue ]
    1. binaryXML-30 : Standardize a "binary XML" format? [open]
  16. Roy Fielding [1 issue ]
    1. utf7Encoding-55 : Security issues with incorrect metadata [open]
  17. Steve Zilles [1 issue ]
    1. formattingProperties-19 : Reuse existing formatting properties/names, coordinate new ones [closed]
  18. T. V. Raman [1 issue ]
    1. genericResources-53 : Generic resources [closed]
  19. TAG [2 issues ]
    1. whenToUseGet-7 : (1) GET should be encouraged, not deprecated, in XForms (2) How to handle safe queries (New POST-like method? GET plus a body?) [open]
    2. abbreviatedURIs-56 : Abbreviating URIs in Web Languages [open]
  20. TAG [3 issues ]
    1. xmlFunctions-34 : XML Transformation and composability (e.g., XSLT, XInclude, Encryption) [open]
    2. RDFinXHTML-35 : Syntax and semantics for embedding RDF in XHTML [open]
    3. TagSoupIntegration-54 : Tag soup integration [open]

Maintained by W3C Technical Architecture Group.

Last update: $Date: 2008/10/10 09:52:43 $


This page was generated as part of the Extensible Issue Tracking System (ExIT)