TAG Issues List
Individual view
This list received comments from 10 groups and 20 individuals.
Comments from groups
-
I18N WG
[1 issue ]
- charmodReview-17 :
Request to review "Character Model for the
Web" Last Call document
[closed]
-
Semantic Web CG
[1 issue ]
- rdfURIMeaning-39 :
Meaning of URIs in RDF documents [open]
-
TAG
[22 issues ]
- 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]
- namespaceDocument-8 :
What should a "namespace document" look like?
[open]
- xmlSW-10 :
Should next version of XML be XML 1.0 - DTDs +
namespaces + xml:base + the infoset?
[closed]
- mixedNamespaceMeaning-13 :
What is the meaning of a document composed of content in
mixed namespaces?
[closed]
- httpRange-14 :
What is the range of the HTTP dereference function?
[open]
- augmentedInfoset-22 :
Infoset augmentation outside of PSVI? [closed]
- xlinkScope-23 :
What is the scope of using XLink? [open]
- contentTypeOverride-24 :
Can a specification include rules for overriding HTTP
content type parameters?
[closed]
- deepLinking-25 :
What to say in defense of principle that deep linking is
not an illegal act?
[closed]
- contentPresentation-26 :
Separation of semantic and presentational markup, to the
extent possible, is architecturally sound.
[open]
- fragmentInXML-28 :
Use of fragment identifiers in XML [open]
- xmlIDSemantics-32 :
How should the problem of identifying ID semantics in
XML languages be addressed in the absence of a DTD?
[open]
- mixedUIXMLNamespace-33 :
Composability for user interface-oriented XML namespaces
[open]
- xmlFunctions-34 :
XML Transformation and composability (e.g., XSLT,
XInclude, Encryption)
[open]
- RDFinXHTML-35 :
Syntax and semantics for embedding RDF in XHTML
[open]
- siteData-36 :
Web site metadata improving on robots.txt, w3c/p3p and
favicon etc.
[open]
- URIGoodPractice-40 :
What are good practices for URI construction? [open]
- XMLVersioning-41 :
What are good practices for designing extensible XML
languages and for handling versioning?
[open]
- ultimateQuestion-42 :
What is the answer to life, the universe, and
everything.
[open]
- DerivedResources-43 :
How are secondary resources derived? [open]
- xmlChunk-44 :
Chunk of XML - Canonicalization and equality [closed]
- mediaTypeManagement-45 :
What is the appropriate level of granularity of the
media type mechanism?
[open]
-
UN/CEFACT ebTWG Architecture Group
[1 issue ]
- uncefactLiaison-5 :
Invitation to create liaison with UN/CEFACT ebTWG
Architecture Group
[closed]
-
WSD WG
[1 issue ]
- abstractComponentRefs-37 :
Definition of abstract components with namespace names
and frag ids
[open]
-
XForms WG
[1 issue ]
- xformsReview-4 :
Request to review XForms Last Call document [closed]
-
XKMS WG
[1 issue ]
- qnameAsId-18 :
Is it ok to use Qnames as Identifiers? [closed]
-
XML Core WG
[2 issues ]
- IRIEverywhere-27 :
Should W3C specifications start promoting IRIs?
[open]
- nameSpaceState-48 :
Adding terms to a namespace [closed]
-
XML Protocol WG
[4 issues ]
- w3cMediaType-1 :
Should W3C WGs define their own media types? [open]
- customMediaType-2 :
What commonality should there be among W3C media types?
[closed]
- nsMediaType-3 :
Relationship between media types and namespaces?
[closed]
- RFC3023Charset-21 :
Do all "shoulds" of RFC 3023 section 7.1
apply?
[closed]
-
XML Protocol WG
[1 issue ]
- xml11Names-46 :
Impact of changes to XML 1.1 on other XML Specifications
[open]
Comments from individuals
-
Aaron Swartz
[1 issue ]
- uriMediaType-9 :
Why does the Web use mime types and not URIs? [closed]
-
Dan Connolly
[2 issues ]
- standardizedFieldValues-51 :
Squatting on link relationship names, x-tokens,
registries, and URI-based extensibility
[open]
- passwordsInTheClear-52 :
Sending passwords in the clear [open]
-
Henry Thompson
[1 issue ]
- URNsAndRegistries-50 :
URIs, URNs, "location independent" naming systems and associated registries for naming on the Web [open]
-
Jonathan Borden
[1 issue ]
- rdfmsQnameUriMapping-6 :
Algorithm for creating a URI from a QName? [closed]
-
Joseph Reagle
[2 issues ]
- URIEquivalence-15 :
When are two URI variants considered equivalent?
[closed]
- qnameAsId-18 :
Is it ok to use Qnames as Identifiers? [closed]
-
Julian Reschke
[1 issue ]
- putMediaType-38 :
Relation of HTTP PUT to GET, and whether client headers
to server are authoritative
[closed]
-
Mark Baker
[5 issues ]
- w3cMediaType-1 :
Should W3C WGs define their own media types? [open]
- customMediaType-2 :
What commonality should there be among W3C media types?
[closed]
- nsMediaType-3 :
Relationship between media types and namespaces?
[closed]
- RFC3023Charset-21 :
Do all "shoulds" of RFC 3023 section 7.1
apply?
[closed]
- endPointRefs-47 :
WS-Addressing SOAP binding & app protocols
[open]
-
Mark Nottingham
[2 issues ]
- HTTPSubstrate-16 :
Should HTTP be used as a substrate protocol? Does W3C
agree with RFC 3205?
[open]
- xml11Names-46 :
Impact of changes to XML 1.1 on other XML Specifications
[open]
-
Noah Mendelsohn
[1 issue ]
- schemeProtocols-49 :
Relationship of URI schemes to protocols and operations
[open]
-
Ossi Nykänen
[1 issue ]
- metadataInURI-31 :
Should metadata (e.g., versioning information) be
encoded in URIs?
[closed]
-
Paul Grosso
[1 issue ]
- xmlProfiles-29 :
When, whither and how to profile W3C specifications in
the XML Family
[closed]
-
Paul Prescod
[1 issue ]
- soapRPCURI-11 :
What is the appropriate relationship between SOAP RPC
and the Web's reliance on URIs?
[closed]
-
Rick Jelliffe
[1 issue ]
- xmlAsText-12 :
Do proposed changes to XML 1.1 ignore Unicode
constraints?
[closed]
-
Rob Lanphier
[1 issue ]
- errorHandling-20 :
What should specifications say about error handling?
[closed]
-
Robin Berjon
[1 issue ]
- binaryXML-30 :
Standardize a "binary XML" format? [open]
-
Roy Fielding
[1 issue ]
- utf7Encoding-55 :
Security issues with incorrect metadata [open]
-
Steve Zilles
[1 issue ]
- formattingProperties-19 :
Reuse existing formatting properties/names, coordinate
new ones
[closed]
-
T. V. Raman
[1 issue ]
- genericResources-53 :
Generic resources [closed]
-
TAG
[2 issues ]
- 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]
- abbreviatedURIs-56 :
Abbreviating URIs in Web Languages [open]
- TAG
[3 issues ]
- xmlFunctions-34 :
XML Transformation and composability (e.g., XSLT,
XInclude, Encryption)
[open]
- RDFinXHTML-35 :
Syntax and semantics for embedding RDF in XHTML
[open]
- 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)
Copyright ©
2003, 2004
W3C® (MIT, ERCIM,
Keio), All Rights Reserved. W3C liability, trademark, document
use and software licensing
rules apply. Your interactions with this site are in accordance with
our public and
Member
privacy statements.