TAG Issues List for Last Call of 9 December 2003 Webarch
Concerning view
- booth1 :
Definition of "Web Agent" [open]
- manola1 :
Use of "agent" as people+software is flaky throughout document. [open]
- manola2 :
Clarify nature of resource in example [open]
- i18nwg3 :
Please show charset in Content-type. [open]
- rosenberg1 :
Introductory para on Web overly broad? [open]
- parsia16 :
No conformance section? Guidance on usage then? [open]
- rosenberg2 :
RFC2119 terms meant for protocols [open]
- manola4 :
Sentence about refs ends abruptly [open]
- dhm1 :
1.1.3. Principles, constraints and good practices [open]
- msm2 :
WD-webarch-20031209, 1.1.3: Self-descriptive markup considered improbable [open]
- manola5 :
Sentence on understanding REST model unclear [open]
- gilman2 :
orthogonality is not the answer [open]
- msm3 :
WD-webarch-20031209, 1.2.1 para 1: Assigning identifiers without knowing about representations [closed]
- msm4 :
WD-webarch-20031209, 1.2.1, final bulleted list, final item.: Authoritative metadata and the principle of decentralization [open]
- parsia1 :
LC Comments: 1.2.1, editorial [open]
- nottingham1 :
Second bullet doesn't make sense. [open]
- i18nwg4 :
Please refer to "issues" rather than "limitations" [open]
- i18nwg5 :
Discussion of content-type header hint [open]
- dhm3 :
"Language extension" definition [open]
- msm5 :
WD-webarch-20031209, 1.2.2 para 5: Extensibility is a not a property of languages in isolation [open]
- msm6 :
WD-webarch-20031209, 1.2.2 para 5: Ignoring the unknown as a default action [open]
- msm7 :
WD-webarch-20031209, 1.2.2 para 6: Ignoring elements and ignoring tags [open]
- parsia2 :
LC Comment 1.3.1, editorial [open]
- dhm2 :
"Silent recovery from error is harmful" [open]
- clark5 :
Silent Error Recovery Always Harmful? [open]
- schema1 :
[1.2.3] "Silent recovery from error is harmful." [closed]
- parsia3 :
LC Comment, 1.2.3: Principle: Error recovery [open]
- manola6 :
User agent any kind of agent or just software? What does "on
behalf of" include? [open]
- manola7 :
"Agent" or "user agent" meant? [open]
- i18nwg6 :
Say something
about character encoding/labeling errors. [open]
- hawke1 :
Proposed good practice note on looking inside protocol interactions [closed]
- dhm4 :
1.2.4 Protocol based interoperability [open]
- parsia4 :
LC Comments, 1.2.4, editorial [open]
- klyne1 :
Proposed to drop para on view source or clarify role in webarch [open]
- hawke2 :
Section 2: Full agreement not required for communication [closed]
- schema2 :
[Section 2] Unwise confluence of identification and retrievability [open]
- msm8 :
WD-webarch-20031209, Section 2, introductory paragraphs: The term 'resource' needs to be defined [open]
- msm9 :
WD-webarch-20031209, Section 2 para 3: The vastness of URI space [closed]
- msm10 :
WD-webarch-20031209, Section 2: Assigning URIs to resources others will expect to refer to [closed]
- parsia5 :
LC Comment, Section 2: Agreement on identifiers [closed]
- parsia6 :
LC Comment, Section 2: Identification mechanism of the Web [closed]
- parsia7 :
LC Comment, Section 2: On requirement to assign a URI to a resource [closed]
- parsia8 :
LC Comment, Section 2: On resources existing before URIs [open]
- parsia9 :
LC Comment, Section 2: On resources being able to have zero URIs [closed]
- parsia10 :
LC Comment, Section 2: On URI assignment [closed]
- klyne2 :
Change "other operations" to "refer to in another way" [open]
- klyne3 :
Proposal to improve text about "network effect" [open]
- klyne4 :
Proposed rewrite of overlapping paras [open]
- klyne5 :
Proposed to use "global across the Web" rather than "global" [open]
- manola8 :
Add "(names for things)" after "identifiers"? [open]
- manola9 :
Why use "third party"? Who are other two? [open]
- manola10 :
Who are "designers"? Any diff between URI owner/producer?
Relationship to resource owner? [open]
- manola11 :
Proposed improvement to GPN on URI assignment [open]
- i18nwg7 :
Mention language negotiation [open]
- dubinko1 :
Document different interpretations around httpRange-14 [open]
- harold1 :
Title of URI uniqueness constraint [open]
- karr1 :
What does "authority component" mean? [open]
- diwg2 :
Don't communicate language info in URIs (in example) [open]
- clark3 :
Willy-Nilly Resource Change [open]
- laskey2 :
What determines URI uniqueness? [open]
- klyne6 :
Clarification about point on agents detecting equivalence relationships [open]
- manola12 :
URI producers or owners? Relationship to opacity principle?
Evidence of confusion about "agent" including "people"? [open]
- i18nwg8 :
Sentences seem contradictory [closed]
- i18nwg9 :
Case example unclear. [open]
- i18nwg10 :
Don't recommend organizing information by language. [open]
- i18nwg11 :
Mention IRIs? [open]
- i18nwg12 :
Clarification on reference to "character" [open]
- booth2 :
What rights does "URI ownership" confer? [closed]
- stickler7 :
Section 3.4, para 2: URI ownership questions [open]
- pps1 :
Ownership and authority [open]
- hawke3 :
2.2 UUID/MD5 not registered URI schemes [open]
- msm11 :
WD-webarch-20031209, Section 2.2, bulleted list, first item: Delegation of authority in hierarchical URIs [closed]
- parsia11 :
URI assignment v. use. Who are URI producers? [open]
- parsia14 :
Various types of ownership [open]
- parsia15 :
Social implications of URI ownership. [open]
- klyne7 :
Use other schema than mailto as example [open]
- manola13 :
Can agents assign URIs? Or should this be "use"? [open]
- manola14 :
Clarify relationship between resource / URI ownership [open]
- hawke4 :
2.3: Propose "URI overloading" not "URI ambiguity" [open]
- clark2 :
What kinds of ambiguity are there? [open]
- schema3 :
[Section 2.3] Clarity required on nature of "resource" [open]
- parsia12 :
Ambiguous use of URIs v. URI Ambiguity? [closed]
- parsia13 :
Use of term "URI Space" [open]
- klyne8 :
Unclear point about ambiguity in natural language; is the point
about machine processing? [open]
- manola15 :
Does example *also* illustrate ambiguous URI usage? [open]
- i18nwg13 :
URI ambiguity ambiguous [open]
- i18nwg14 :
Show examples of good and bad ambiguity [open]
- manola16 :
Paragraph on other uses of URIs is confusing [open]
- i18nwg15 :
Missing word [open]
- i18nwg16 :
Good practice on URI opacity impossible to follow for humans. [closed]
- klyne9 :
Add stronger language on not permitting unregistered URI schemes. [open]
- baker1 :
Independence between identifier and resource, or representations? [closed]
- parsia17 :
Do you mean resource or representation? [open]
- parsia18 :
Temporal URL ambiguity useful for Web robustness? [open]
- parsia19 :
Ok to infer properties of retrieved representations? [open]
- klyne10 :
Add cross-ref to section on orthogonality [open]
- manola12 :
URI producers or owners? Relationship to opacity principle?
Evidence of confusion about "agent" including "people"? [open]
- manola17 :
"Agent" that includes "people" source of confusion [closed]
- hawke6 :
2.6. Fragment Identifiers: "Stem resource" [open]
- clark1a :
Fragment Identifier Semantics [open]
- clark1b :
Conflicting secondary resources [open]
- hawke7 :
2.7.2. Assertion that Two URIs Identify the Same Resource [closed]
- baker2 :
More info on non-browser Web [closed]
- parsia20 :
Drop definition of "on the Web" [closed]
- kopecky2 :
3.1 Reference or Identify? [open]
- klyne11 :
Change "will result" to "will necessarily result" [open]
- i18nwg17 :
Add mention of IRIs [open]
- hawke8 :
3.2. Messages and Representations: Use of "state" [open]
- klyne12 :
Proposal to drop paragraph on inconsistent frag ids [closed]
- falstrom2 :
SOAP as a different thing than the other protocols [open]
- schema4 :
[3.3 Good practice: Fragment Identifier Consistency] [closed]
- stickler8 :
Section 3.3.1, last para, last sentence: Nature of secondary resource not known through URI [open]
- stickler9 :
Good practice note on URIs without fragids? [closed]
- schema5 :
[3.3.1] Inconsistency with RFC2396bis about frag id meaning? [open]
- schema6 :
[3.3.1] Do fragment identifiers
work only with media-typed representations? [open]
- msm12 :
WD-webarch-20031209, Section 3.3.1, para 1: Are there constraints on the interpretation of fragment identifiers? [open]
- manola19 :
Please provide qualifying context about the nature of the Web [open]
- msm13 :
WD-webarch-20031209, Section 3.3.2, para 3: Consistency of fragment identifiers [open]
- klyne12b :
Drop "by design" or replace with "by intent" [open]
- manola20 :
Have text after a story answer the question in the story. [open]
- falstrom3 :
Separate Media Types and Frag Id discussion [open]
- stickler7 :
Section 3.4, para 2: URI ownership questions [open]
- pps1 :
Ownership and authority [open]
- parsia21 :
Drop sentence on successful communication [closed]
- parsia22 :
What does "in general" mean? Would the case be different "in specific"? [open]
- klyne13 :
Text on communication between two parties misses mark about
global names [open]
- manola21 :
Owner of resource v. owner of URI [open]
- dhm6 :
Use of "server" in "...authoritative server metadata..." [open]
- schema7 :
[3.4.1] What is scope of metadata? [open]
- schema8 :
[3.4.1] Authority and trust [closed]
- schema9 :
[3.4.1] Are peer-to-peer interactions covered? [closed]
- manola22 :
"Agent" or "user agent" meant? [open]
- i18nwg18 :
Mention that editing tools may be more strict than simple
user agents [open]
- i18nwg19 :
text/foo+xml considered useless? [closed]
- i18nwg20 :
text/foo+xml considered useless? [open]
- hawke10 :
3.5. Safe Interactions [open]
- schema10 :
[3.5] Breadth of "safe" interactions [open]
- manola23 :
Can software agents incur obligations? ("agent" or "user agent") [open]
- manola24 :
What meaning(s) of "order" is meant? [open]
- stickler6 :
Section 3.5.1: POST requests and URIs [open]
- schema11 :
[3.5.1] Best practice that content-location SHOULD be used? [open]
- falstrom4 :
Show only good practice re: Content-Location [open]
- falstrom5 :
Add discussion about SSL/TLS? Is title correct? [open]
- stickler5 :
Section 3.6, para 1: Fix "resource is unreliable" [open]
- klyne14 :
Managers of resource, not Oaxaca [open]
- manola26 :
What does last sentence of story have to do with story? [open]
- stickler4 :
Section 3.6.1 Proposed removal of good practice note [open]
- schema12 :
[3.6.1]
[3.6.1] Good practice: Available representation. Too preferential to dereferencable URIs [open]
- diwg1 :
Add scenario(s) with dynamically generated URI [open]
- klyne15 :
Lack of separation between owner of a resource
and authority for a part of URI space used to identify a resource? [open]
- klyne15b :
Propose "rationally" instead of "predictably" [open]
- klyne16 :
Proposed improved example about using content negotiation [open]
- klyne17 :
Worth pointing out value of RDF descriptions depends
on URI persistence? [open]
- manola27 :
Provide examples of mistaken attempts to restrict URI usage [open]
- rosenberg4 :
Use SIP for voice-over-ip, RTSP for streaming media [open]
- kopecky3 :
4 application/xml [open]
- klyne18 :
Use one of "data format", "format". And "language"? [open]
- dhm5 :
4.1 Prevalence of Unicode [open]
- falstrom6 :
List overall diffs between binary and text formats [open]
- schema13 :
[4.2] Overly simplifies a complex problem [open]
- diwg4 :
Suggest discussion of the limitations of Internet media types as the prime mechanism for selecting between different representations of a resource. [open]
- manola28 :
Another case of "agent includes people?" doubt [open]
- manola29 :
What are "language instances"? [open]
- msm14 :
WD-webarch-20031209, Section 4.2.2, Story: Allowing extra attributes does change the conformance of existing data [open]
- schema14 :
[4.2.3] Must * rules in instance v. documentation [open]
- manola30 :
Difference between "setting expectations" and "specifying"? [open]
- schema15 :
[4.2.4] SOAP message cannot include JPEG [closed]
- klyne19 :
Unclear statement about mixing RDF vocabularies [open]
- klyne20 :
Say something about relationship between
Hypertext Web and Semantic Web? [closed]
- manola31 :
Questions about RDF, text, XML mixing [open]
- clark6 :
Separating Presentation From Content [open]
- gilman1 :
'legal requirement' as justification for 'particular presentation' misses 'leading Web to highest' mark [open]
- klyne21 :
Add statement about scalability concerns [open]
- clark4a :
Hypertext Good Practice Redundancies [open]
- clark4b :
"Expected UI Paradigm"? [open]
- klyne22 :
Clarify what is meant by context having influence
on use of hyperlinks [open]
- falstrom7 :
Indicate when to use different link types [open]
- klyne23 :
Clarify section (see TBL text on identifier v. reference?) [open]
- klyne24 :
Is Web apart from Internet? [open]
- schema16 :
[4.5.1] Section on when to use XML formats underdeveloped [open]
- klyne25 :
Add reference to RFC3117, section 5.1? [open]
- baker4 :
4.5.2: Preference for RDF linking over XLink linking [open]
- kopecky4 :
4.5.3 use of "understand" [open]
- schema17 :
[4.5.3] Statement about XMLNS and unique names false [open]
- schema18 :
[4.5.3] Clarification on "type" in XML Schema [open]
- schema19 :
[4.5.3] Element type/instance confusion [open]
- manola32 :
Reword to avoid rhetorical question [open]
- rosenberg5 :
Proposed reference to IANA registry for namespaces and RFC 3688 [open]
- booth3 :
4.5.4: NS document as definitive source of info on namespace [closed]
- stickler1 :
Editorial suggestions [open]
- kopecky5 :
4.5.5 More info on qnames, fragids, ns docs [closed]
- kopecky6 :
4.5.6 What's the conclusion? [closed]
- schema20 :
[4.5.6] Flavors of ID not discussed [open]
- klyne26 :
Transcoding allowing by some or all intermediaries? [open]
- klyne27 :
Clarify para on "text/" and US-ASCII encoding. How does
it relate to following GPN? [open]
- stickler3 :
Section 5: Dereference a URI [open]
- stickler10 :
Section 5: Secondary resource [open]
- hammond1 :
Distinguish normative/informative references? [open]
- nottingham2 :
Include reference to IANA Registry of HTTP headers? [open]
- manola18 :
Update references to RDF, OWL specs [open]
- falstrom1 :
Editorial comments [open]
- parsia16 :
No conformance section? Guidance on usage then? [open]
- rosenberg2 :
RFC2119 terms meant for protocols [open]
- booth1 :
Definition of "Web Agent" [open]
- manola1 :
Use of "agent" as people+software is flaky throughout document. [open]
- manola2 :
Clarify nature of resource in example [open]
- i18nwg3 :
Please show charset in Content-type. [open]
- rosenberg1 :
Introductory para on Web overly broad? [open]
- rosenberg3 :
Reuse appropriate URI schemes (and protocols) [closed]
Maintained by W3C Technical Architecture Group.Last update: $Date: 2004/08/10 13:11:54 $
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.