This page is for maintaining a record of changes between each revision of "Architectural Principles of the World Wide Web, produced by the TAG. If you find the list is incomplete or inaccurate please send email to the TAG at www-tag@w3.org.
Last modified: $Date: 2004/12/15 01:48:53 $
Changes between 5 November 2004 Proposed Recommendation and the 15 December 2004 Recommendation (diff).
---------------------------- revision 1.809 date: 2004/12/14 20:18:36; author: ijacobs; state: Exp; lines: +4 -4 some minor tweaks based on DC suggestions ---------------------------- revision 1.808 date: 2004/12/13 22:45:40; author: ijacobs; state: Exp; lines: +2 -2 tweak ---------------------------- revision 1.807 date: 2004/12/13 22:45:26; author: ijacobs; state: Exp; lines: +3 -3 editorial ---------------------------- revision 1.806 date: 2004/12/13 22:44:58; author: ijacobs; state: Exp; lines: +2 -2 editorial tweak (missing comma) ---------------------------- revision 1.805 date: 2004/12/13 22:40:15; author: ijacobs; state: Exp; lines: +5 -2 added stuff missing from status section: - link to changes - mailing lists for comments, discussion ---------------------------- revision 1.804 date: 2004/12/13 22:37:40; author: ijacobs; state: Exp; lines: +9 -2 added info about two mailing lists. ---------------------------- revision 1.803 date: 2004/12/13 22:27:14; author: ijacobs; state: Exp; lines: +2 -2 link fix ---------------------------- revision 1.802 date: 2004/12/13 22:06:04; author: NormanWalsh; state: Exp; lines: +2 -2 Fixed a typo ---------------------------- revision 1.801 date: 2004/12/13 21:56:50; author: NormanWalsh; state: Exp; lines: +9 -7 Updated definition of link per Nokia comment, discussed with TimBL/DanC on 13 Dec. ---------------------------- revision 1.800 date: 2004/12/13 21:12:12; author: NormanWalsh; state: Exp; lines: +6 -4 Updated namespace document per Stickler, decided at 13 Dec telcon. ---------------------------- revision 1.799 date: 2004/12/13 20:54:32; author: NormanWalsh; state: Exp; lines: +4 -9 Change for Stickler per 13 Dec telcon ---------------------------- revision 1.798 date: 2004/12/12 19:38:32; author: ijacobs; state: Exp; lines: +2 -2 updated errata link ---------------------------- revision 1.797 date: 2004/12/12 19:35:55; author: ijacobs; state: Exp; lines: +8 -1 added tentative links for errata, translations ---------------------------- revision 1.796 date: 2004/12/12 19:33:30; author: ijacobs; state: Exp; lines: +2 -2 tweak ---------------------------- revision 1.795 date: 2004/12/12 19:33:14; author: ijacobs; state: Exp; lines: +2 -2 dated update ---------------------------- revision 1.794 date: 2004/12/12 19:32:42; author: ijacobs; state: Exp; lines: +21 -35 updated status ---------------------------- revision 1.793 date: 2004/12/09 18:44:21; author: ijacobs; state: Exp; lines: +5 -27 updated status section ---------------------------- revision 1.792 date: 2004/12/09 18:40:49; author: ijacobs; state: Exp; lines: +2 -2 added missing period ---------------------------- revision 1.791 date: 2004/12/09 18:40:06; author: ijacobs; state: Exp; lines: +2 -2 made xml-id cap and consistent with other keys ---------------------------- revision 1.790 date: 2004/12/09 18:31:25; author: ijacobs; state: Exp; lines: +7 -7 updated for 9 Dec 2004 editor's draft, also added link to my people page ---------------------------- revision 1.789 date: 2004/12/09 18:24:27; author: ijacobs; state: Exp; lines: +11 -10 editorial fixes based on NM comments: http://lists.w3.org/Archives/Public/www-tag/2004Dec/0006.html ---------------------------- revision 1.788 date: 2004/12/09 18:20:57; author: ijacobs; state: Exp; lines: +15 -10 editorial fixes in story about representation reuse based on http://lists.w3.org/Archives/Public/www-tag/2004Dec/0001.html ---------------------------- revision 1.787 date: 2004/12/09 18:02:35; author: ijacobs; state: Exp; lines: +2 -2 editorial tweak ---------------------------- revision 1.786 date: 2004/12/09 17:59:14; author: ijacobs; state: Exp; lines: +5 -5 attempt to incorporate comment from HT (number 3 in the exec summary) http://lists.w3.org/Archives/Public/public-webarch-comments/2004OctDec/0171.html ---------------------------- revision 1.785 date: 2004/12/09 17:56:00; author: ijacobs; state: Exp; lines: +4 -3 attempt to incorporate comment from HT (number 2) http://lists.w3.org/Archives/Public/public-webarch-comments/2004OctDec/0171.html ---------------------------- revision 1.784 date: 2004/12/09 17:51:29; author: ijacobs; state: Exp; lines: +2 -2 s/Representation/representation per HT: http://lists.w3.org/Archives/Public/public-webarch-comments/2004OctDec/0171.html ---------------------------- revision 1.783 date: 2004/12/09 17:43:28; author: ijacobs; state: Exp; lines: +4 -4 adopted NM's editorial rewrite: http://lists.w3.org/Archives/Member/tag/2004Dec/0039.html ---------------------------- revision 1.782 date: 2004/12/09 17:42:40; author: ijacobs; state: Exp; lines: +8 -7 based on Patrick Stickler comment: http://lists.w3.org/Archives/Public/public-webarch-comments/2004OctDec/0169.html And discussion on tag@w3.org: http://lists.w3.org/Archives/Member/tag/2004Dec/0033.html Adopted PS's first sentence as the new definition text. ---------------------------- revision 1.781 date: 2004/12/09 17:34:39; author: ijacobs; state: Exp; lines: +34 -37 more edits to CL/HWL's text (use of active voice, e.g.) http://lists.w3.org/Archives/Public/public-webarch-comments/2004OctDec/0165.html ---------------------------- revision 1.780 date: 2004/12/09 17:20:44; author: ijacobs; state: Exp; lines: +14 -5 some edits to section on separation of presentation/content based on HWL comments: http://lists.w3.org/Archives/Public/public-webarch-comments/2004OctDec/0159.html In particular these changes make his point: "As discussed above, the "size" argument is false, but the "computation" is correct." ---------------------------- revision 1.779 date: 2004/12/07 03:14:26; author: ijacobs; state: Exp; lines: +7 -7 changed edition to volume per 6 Dec TAG teleconf
Changes between 5 November 2004 Proposed Recommendation and the 3 December 2004 Editor's Draft (diff).
----------------------- revision 1.778 date: 2004/12/03 19:57:43; author: NormanWalsh; state: Exp; lines: +4 -4 Updated metadata ---------------------------- revision 1.777 date: 2004/12/03 19:51:46; author: NormanWalsh; state: Exp; lines: +8 -4 Changes per mail from Yuxiao Zhao discussed at 29 Nov 2004 f2f. Updated Acknowledgements. ---------------------------- revision 1.776 date: 2004/12/03 19:44:01; author: NormanWalsh; state: Exp; lines: +27 -15 Change definition of namespace; change presentation/content text per CL proposal
Changes between 2 November 2004 Editor's Draft and the 5 November 2004 Proposed Recommendation (diff since 2 November; diff since Last Call, 16 Aug, with deletes and without).
----------------------------
revision 1.773
date: 2004/11/05 00:35:29; author: ijacobs; state: Exp; lines: +2 -2
added rel="disclosure"
----------------------------
revision 1.772
date: 2004/11/05 00:34:02; author: ijacobs; state: Exp; lines: +2 -2
made one link a mailto: link for comments
----------------------------
revision 1.771
date: 2004/11/05 00:33:09; author: ijacobs; state: Exp; lines: +3 -3
updated status, removed @@s
----------------------------
revision 1.770
date: 2004/11/05 00:31:49; author: ijacobs; state: Exp; lines: +2 -2
uri fix
----------------------------
revision 1.769
date: 2004/11/05 00:31:14; author: ijacobs; state: Exp; lines: +2 -2
fixed link to changes
----------------------------
revision 1.768
date: 2004/11/05 00:31:01; author: ijacobs; state: Exp; lines: +1 -3
removed:
A list of current W3C Recommendations and other technical documents can be found at the W3C Web site.
---------------------------- revision 1.755 date: 2004/11/04 18:01:08; author: ijacobs; state: Exp; lines: +7 -7 moved a para ---------------------------- revision 1.754 date: 2004/11/04 18:00:41; author: ijacobs; state: Exp; lines: +17 -12 italicized boilerplate ---------------------------- revision 1.753 date: 2004/11/04 17:56:54; author: ijacobs; state: Exp; lines: +6 -7 updated ipr policy ---------------------------- revision 1.752 date: 2004/11/04 17:51:03; author: ijacobs; state: Exp; lines: +2 -0 added $Id: changes.html,v 1.71 2004/12/15 01:48:53 ijacobs Exp $ ---------------------------- revision 1.751 date: 2004/11/04 17:24:43; author: NormanWalsh; state: Exp; lines: +2 -1 Checkpoint; still fiddling with the status section ---------------------------- revision 1.750 date: 2004/11/04 17:23:51; author: NormanWalsh; state: Exp; lines: +6 -2 Checkpoint; still fiddling with the status section ---------------------------- revision 1.749 date: 2004/11/04 17:21:41; author: NormanWalsh; state: Exp; lines: +4 -4 Checkpoint; still fiddling with the status section ---------------------------- revision 1.748 date: 2004/11/04 17:17:42; author: NormanWalsh; state: Exp; lines: +3 -2 Checkpoint; still fiddling with the status section ---------------------------- revision 1.747 date: 2004/11/04 17:15:14; author: NormanWalsh; state: Exp; lines: +14 -5 Checkpoint; still fiddling with the status section ---------------------------- revision 1.746 date: 2004/11/04 17:09:06; author: NormanWalsh; state: Exp; lines: +9 -7 Checkpoint; still fiddling with the status section ---------------------------- revision 1.745 date: 2004/11/04 17:05:24; author: NormanWalsh; state: Exp; lines: +17 -14 Checkpoint ---------------------------- revision 1.744 date: 2004/11/04 16:54:52; author: NormanWalsh; state: Exp; lines: +9 -4 Checkpoint ---------------------------- revision 1.743 date: 2004/11/04 16:45:15; author: NormanWalsh; state: Exp; lines: +3 -2 Snapshot ---------------------------- revision 1.742 date: 2004/11/04 16:44:09; author: NormanWalsh; state: Exp; lines: +7 -7 Snapshot ---------------------------- revision 1.741 date: 2004/11/04 16:14:19; author: NormanWalsh; state: Exp; lines: +14 -9 Added information resource to the glossary; fixed apostrophesChanges between 1 November 2004 Editor's Draft and the 2 November 2004 Editor’s Draft (diff since 1 November).
---------------------------- revision 1.740 date: 2004/11/02 20:16:39; author: NormanWalsh; state: Exp; lines: +172 -147 Updated status; editorial changes, mostly suggested by IanJ
Changes between 28 October 2004 Editor's Draft and the 1 November 2004 Editor’s Draft (diff since 28 October).
---------------------------- revision 1.739 date: 2004/11/01 22:13:02; author: NormanWalsh; state: Exp; lines: +3 -2 Change negotiated at PR request telcon, XLink 'should' to 'may' ---------------------------- revision 1.738 date: 2004/11/01 21:42:21; author: NormanWalsh; state: Exp; lines: +3 -4 Change negotiated at PR request telcon, XLink 'should' to 'may' ---------------------------- revision 1.737 date: 2004/11/01 19:14:32; author: NormanWalsh; state: Exp; lines: +3 -3 Tweaked pubdate ---------------------------- revision 1.736 date: 2004/11/01 19:12:45; author: NormanWalsh; state: Exp; lines: +10 -9 Small editorial changes to 2.2 in response to IanJ
Changes between 26 October 2004 Editor's Draft and the 28 October 2004 Editor’s Draft (diff since 26 October).
---------------------------- revision 1.735 date: 2004/10/28 18:20:54; author: NormanWalsh; state: Exp; lines: +45 -50 Editorial tweaks
Changes between 21 October 2004 Editor's Draft and the 26 October 2004 Editor’s Draft (diff since 21 October).
---------------------------- revision 1.734 date: 2004/10/26 16:01:30; author: NormanWalsh; state: Exp; lines: +50 -119 Editor's attempt at edits from 2004-10-25 telcon
Changes between 19 October 2004 Editor's Draft and the 21 October 2004 Editor’s Draft (diff since 19 October).
---------------------------- revision 1.733 date: 2004/10/21 19:55:08; author: NormanWalsh; state: Exp; lines: +114 -48 Fixed typo in abstract; integrated Noah's suggested changes to generalize 'octet streams'
Changes between 14 October 2004 Editor's Draft and the 19 October 2004 Editor’s Draft (diff since 14 October).
---------------------------- revision 1.731 date: 2004/10/19 16:42:40; author: NormanWalsh; state: Exp; lines: +23 -11 Editorial changes from 18 Oct telcon
Changes between 28 September 2004 Editor's Draft and the 14 October 2004 Editor’s Draft (diff since 28 September).
---------------------------- revision 1.730 date: 2004/10/14 20:47:11; author: NormanWalsh; state: Exp; lines: +9 -5 Tweak metadata; publish new draft ---------------------------- revision 1.729 date: 2004/10/14 17:28:01; author: NormanWalsh; state: Exp; lines: +32 -3 Tweaked acknowledgements ---------------------------- revision 1.728 date: 2004/10/14 17:07:59; author: NormanWalsh; state: Exp; lines: +9 -10 Pubrules tweaks ---------------------------- revision 1.727 date: 2004/10/14 16:48:06; author: NormanWalsh; state: Exp; lines: +86 -150 Norm's end-to-end editorial pass ---------------------------- revision 1.726 date: 2004/10/14 14:13:03; author: NormanWalsh; state: Exp; lines: +83 -59 Changes from the f2f meeting record ---------------------------- revision 1.725 date: 2004/10/13 18:31:43; author: NormanWalsh; state: Exp; lines: +111 -103 Editorial suggestions from Ian Jacobs; thanks Ian ---------------------------- revision 1.724 date: 2004/10/12 21:27:01; author: NormanWalsh; state: Exp; lines: +2 -2 Whitespace ---------------------------- revision 1.723 date: 2004/10/12 20:36:56; author: NormanWalsh; state: Exp; lines: +3 -3 Completed: ACTION NDW: to fix cross references to 'uri allocation' that read 'uri assignment' ---------------------------- revision 1.722 date: 2004/10/09 13:33:34; author: NormanWalsh; state: Exp; lines: +11 -164 Checkpoint ---------------------------- revision 1.721 date: 2004/10/07 14:45:52; author: NormanWalsh; state: Exp; lines: +227 -41 Minor editorial changes and significant revamping of information resource text
Changes between 16 August 2004 Working Draft and the 28 September 2004 Editor’s Draft (diff since 16 August).
---------------------------- revision 1.720 date: 2004/09/29 13:08:12; author: NormanWalsh; state: Exp; lines: +1 -1 Updated pubdate ---------------------------- revision 1.719 date: 2004/09/29 12:57:15; author: NormanWalsh; state: Exp; lines: +39 -6 Worked on the extensibility section per the 27 Sep TAG telcon minutes ---------------------------- revision 1.718 date: 2004/09/28 19:57:20; author: NormanWalsh; state: Exp; lines: +55 -37 Editorial changes based on Graham Klyne's comments ---------------------------- revision 1.717 date: 2004/09/24 18:09:10; author: NormanWalsh; state: Exp; lines: +1 -1 Fix pubdate ---------------------------- revision 1.716 date: 2004/09/24 18:08:26; author: NormanWalsh; state: Exp; lines: +118 -91 More drafting; mostly in response to Tim Bray's comments ---------------------------- revision 1.715 date: 2004/09/23 20:57:35; author: NormanWalsh; state: Exp; lines: +55 -46 Integrate SKW's text on URI ownership ---------------------------- revision 1.714 date: 2004/09/23 20:45:06; author: NormanWalsh; state: Exp; lines: +3 -1 Added reference to CHIPS ---------------------------- revision 1.713 date: 2004/09/03 16:23:12; author: NormanWalsh; state: Exp; lines: +19 -16 Editorial fixes from public comments
The pervasive nature of the changes in this draft make generating a colorized "diff" version impractical.
----------------------------
revision 1.708
date: 2004/08/17 18:01:35; author: NormanWalsh; state: Exp; lines: +41 -109
Editorial changes from IJ
----------------------------
revision 1.707
date: 2004/08/17 17:31:58; author: NormanWalsh; state: Exp; lines: +43 -41
Another slug of editorial changes suggested by SW (mid:41218F7C.5000704@hp.com)
----------------------------
revision 1.706
date: 2004/08/17 14:43:47; author: NormanWalsh; state: Exp; lines: +29 -26
Editorial suggestions from SW (mid:E864E95CB35C1C46B72FEA0626A2E80803E3BC2E@0-mail-br1.hpl.hp.com) except ToC reorg
----------------------------
revision 1.705
date: 2004/08/16 19:29:22; author: ijacobs; state: Exp; lines: +1 -1
one more fix
----------------------------
revision 1.704
date: 2004/08/16 19:26:59; author: ijacobs; state: Exp; lines: +3 -3
tweaks to make a 16 Aug editor's copy
----------------------------
revision 1.703
date: 2004/08/16 19:21:32; author: ijacobs; state: Exp; lines: +23 -23
converted two-byte chars back to ascii
----------------------------
revision 1.702
date: 2004/08/13 17:15:41; author: NormanWalsh; state: Exp; lines: +1 -1
Fixed typo in URI
----------------------------
revision 1.701
date: 2004/08/13 15:37:28; author: NormanWalsh; state: Exp; lines: +4 -4
Fixed copyright, per pubrules
----------------------------
revision 1.700
date: 2004/08/13 15:32:30; author: NormanWalsh; state: Exp; lines: +141 -141
TOC reorg
----------------------------
revision 1.699
date: 2004/08/13 15:19:08; author: NormanWalsh; state: Exp; lines: +15 -108
Minor editorial tweaks
----------------------------
revision 1.698
date: 2004/08/13 12:17:40; author: NormanWalsh; state: Exp; lines: +2 -0
Snapshot
----------------------------
revision 1.697
date: 2004/08/12 19:44:06; author: NormanWalsh; state: Exp; lines: +17 -16
Pubrules tweaks to copyright and last version
----------------------------
revision 1.696
date: 2004/08/12 19:36:29; author: NormanWalsh; state: Exp; lines: +40 -23
Begin the pubrules dance
----------------------------
revision 1.695
date: 2004/08/11 17:18:33; author: NormanWalsh; state: Exp; lines: +103 -65
More f2f fiddling
----------------------------
revision 1.694
date: 2004/08/11 12:59:25; author: NormanWalsh; state: Exp; lines: +313 -112
Updated with 10 Aug changes:
I couldn’t check these in individually because of connectivity problems.
I fixed:
MSM5 -- editorial; provide an antecedent for "this property"; note that
there are multiple kinds of processing; make it clear that the subset
is extensible
MSM6, 5.2, make it clear that there should be a default action;
default depends on context (country code on a phone number in a
purchase order)
---
diwg1
New section in 3.6: Supporting Navigation
Add examples of URIs:
http://www.w3.org/TR/
http://maps.example.com/?lat=xxx,long=yyy,town=Cambridge,state=MA,country=US
http://maps.example.com/?sessnid=12345;userid=abcde
Inability to link to sub-pages of financial information
http://my.example.com/
---
diwg2
Chris to write text; will address content negotiated language selection
---
diwg3
Incorporate text from 2.2.3 of http://www.w3.org/TR/di-princ/
into our 4.3 and add a reference to di-princ.
---
manola27
Add to 3.6.2 that "that doesn't mean everyone has to know every URI"
or words to that effect. "Security considerations may require you
to keep some URIs secret"
change "but it is unreasonable to prohibit others from merely
identifying the resource" to "but merely identifying the resource is
like referring to a book by title. Except when people have agreed to
keep titles or URIs confidential, they are free to exchange them.
---
http://www.w3.org/2001/tag/webarch/July7-Aug10-diff.html
---
In 2.2, suggest changing "We use the term information resource to
refer to those resources for which you can retrieve a representation
over the network." to "A special class of resources, information
resources, is discussed in section 3.1. Information Resources and
Representations"
In 3.1, Information Resources are resources
that convey information. If a resource has a representation
then it is an information resource.
---
Although there are benefits (such as naming flexibility) to URI
aliases, there are also costs. Deployment of URI aliases raises the
cost or may even make it impossible for software to determine that
the URIs identify the same resource. URI owners should thus be
conservative about the number of different URIs they associate with
the same resource.
---
[URI aliases, 2.3.1]
URI aliases are harmful when they cause bifurcation in the web
of related resources. A corollary of Metcalfe's Principle
(the "Network Effect") is that the value of a given resource
can be measured by the number and value of other resources
that link to it (the network neighborhood of the measured resource).
This type of valuation is commonly used to rank the relative
value of search results (e.g., Google) because people tend to
create links relating a given topic to those resources that
they feel best reflect that topic, and hence the number of
inbound references are a reflection of the degree to which
the community values a resource. The problem with aliases is
that if half of the neighborhood points to one URI for a given
resource, and the other half points to a second, different URI
for that same resource, the neighborhood graph splits (bifurcates).
The aliased resource is not the only one undervalued because
of this split: the entire neighborhood of resources become
undervalued due to the missing second-order relationships that
should have existed among the referring resources by virtue of
their references to the aliased resource.
[note, aliases are also in 2.2 for some reason unknown]
---
In 2.3.2, change the story to to say that Dirk asks Nadia if
it matters which one she bookmarks.
---
In 2.5, remove (i.e., sequence of characters)
---
Rename, 2.5 URI Allocation
The URI spec[RFC2717,RFC2396] is an agreement about how the internet
community allocates names and associates them with protocols by
which they take on meaning; for example, the HTTP URI
scheme[RFC2616*] uses DNS in such a way that the names such as
http://somedomain/somepath#someFrag take on meaning by way of
messages from the domain holder (or somebody they delegate to).
While other communications (documents, messages, ...) may suggest
meanings for such names, it's a local policy decision whether those
suggestions should be heeded, while the meaning obtained thru HTTP
GET is, by internet-wide agreement, authoritative.
2.5.1 URI Ownership
A widely deployed technique to avoid URI overloading is delegated
ownership.
2.5.2 Other Allocation Schemes
UUID/MID; news:comp.text.xml has a social process for creating
them...
---
2.4 URI Collision
As discussed above, a URI identifies one resource. To use the same
URI to identify different resources produces a collision.
Suppose, for example, that one organization makes use of a URI to
refer to the movie "The Sting", and another organization uses the
same URI to refer to a discussion forum about "The Sting." This
collision creates confusion about what the URI identifies,
undermining the value of the URI. If one wanted to talk about the
creation date of the resource identified by the URI, for instance,
it would not be clear whether this meant "when the movie created" or
"when the discussion forum about the movie was created."
Principle: URIs identify a single resource
Assign distinct URIs to distinct resources.
---
3.3.1
In one of his XHTML pages, Dirk creates a hypertext link to an image
that Nadia has published on the Web. He creates a hypertext link
with Nadia's
hat. Emma views Dirk's XHTML page in her Web browser and follows
the link. The HTML implementation in her browser removes the
fragment from the URI and requests the image
"http://www.example.com/images/nadia" Nadia serves an SVG
representation of the image (with Internet media type
"image/svg+xml"). Emma's Web browser starts up an SVG implementation
to view the image. It passes it the original URI including the
fragment, "http://www.example.com/images/nadia#hat" to this
implementation, causing a view of the hat to be displayed rather
than the complete image.
Xref orthogonality from the following paragraph.
---
3.4
Incorporate Tim's text. Remove "documents" from expiry date.
Add pointers to relevant sections of http: and Apache docs.
---
3.5
reasons: document might be confidential, uri might be impractically
large
---
3.6
Delete "There are applications where it may be impossible or
impractical to provide a representation for every resource
(consider, for example, a system that used URIs to identify memory
locations in a running program). The fact that such applications
cannot provide representations should not discourage designers from
developing applications that treat them as web resources."
Change:
Principle: Reference does not imply dereference
An application developer or specification author SHOULD not require
networked retrieval to representations each time they are referenced.
Dereferencing a URI has a cost, potentially a significant cost,
perhaps in terms of security, network latency, or other factors.
Attempting to retrieve representations of resources when such
retrieval is not necessary should be avoided.
---
4.3
Change:
For instance digital signature technology, access control, and other
technologies are appropriate for controlling access to content.
to:
Designers should consider appropriate technologies, such as encryption
and access control, for limiting the audience
---
4.5.1
Salt again: The data's usefulness should outlive the tools currently
used to process it (though obviously XML can be used for short-term
needs as well)
Chris proposes: Need for data that can outlinve the applicatins that
produced it
---
Principle: Orthogonality
Orthogonal abstractions benefit from orthogonal specifications.
Experience demonstrates that problems arise where orthogonal
concepts occur in a single specification. Consider, for example, the
HTML specification which includes the orthogonal x-www-form-urlencoded
specification. Software developers (for example, of [CGI]
applications) might have an easier time finding the specification if
it were published separately and then cited from the HTTP, URI, and
HTML specifications.
Problems also arise when specifications attempt to modify orthogonal
abstractions described elsewhere. An historical version of the HTML
specification specified an HTTP header field ("Refresh"). The
authors of the HTTP specification ultimately decided not to provide
this header and that made the two specifications awkwardly at odds
with each other. HTML eventually removed the header.
(The problem here is the use of http-equiv with the value "refresh"
which *has no equivalent* in the http spec!)
---
Glossary:
Resource
[delete: A general term for ]Anything that might be identified by a URI.
----------------------------
revision 1.693
date: 2004/08/10 11:30:24; author: NormanWalsh; state: Exp; lines: +1 -1
Bumped date
----------------------------
revision 1.692
date: 2004/08/10 11:27:19; author: NormanWalsh; state: Exp; lines: +6 -6
Tweaked definition of information resource
----------------------------
revision 1.691
date: 2004/08/10 11:03:07; author: NormanWalsh; state: Exp; lines: +14 -5
Rearranged the definitional use of the word 'resource'; added text from 2396bis
----------------------------
revision 1.690
date: 2004/08/10 10:52:34; author: NormanWalsh; state: Exp; lines: +6 -0
Added an explicit note about using POST for safe operations
----------------------------
revision 1.689
date: 2004/08/10 10:47:26; author: NormanWalsh; state: Exp; lines: +8 -4
Added note about using URIs even when representations cannot be provided
----------------------------
revision 1.688
date: 2004/08/10 10:34:33; author: NormanWalsh; state: Exp; lines: +12 -33
Updated 5.1 to address nottingham1
----------------------------
revision 1.687
date: 2004/08/10 10:21:52; author: NormanWalsh; state: Exp; lines: +1 -1
Changed 'unknown elements' to 'unknown tags' to address msm7
----------------------------
revision 1.686
date: 2004/08/10 10:20:17; author: NormanWalsh; state: Exp; lines: +16 -0
Added good practice about server managers allowing users control of metadata to address msm4
----------------------------
revision 1.685
date: 2004/08/10 10:09:43; author: NormanWalsh; state: Exp; lines: +13 -0
Added good practice about unneccessary network access to address schema12
----------------------------
revision 1.684
date: 2004/08/10 10:00:35; author: NormanWalsh; state: Exp; lines: +27 -1
Added 2.3.2 Representation reuse to address schema3
----------------------------
revision 1.683
date: 2004/08/10 09:33:26; author: NormanWalsh; state: Exp; lines: +6 -0
Address klyne21
----------------------------
revision 1.682
date: 2004/08/08 18:54:59; author: NormanWalsh; state: Exp; lines: +36 -22
Addressed schema16, parsia11, klyne7, and klyne9. Integrated CL's updates to Section 3.3.1
----------------------------
revision 1.681
date: 2004/07/07 16:58:28; author: ijacobs; state: Exp; lines: +2 -1
tweak
----------------------------
revision 1.680
date: 2004/07/05 17:09:26; author: ijacobs; state: Exp; lines: +21 -21
link fixes
----------------------------
revision 1.679
date: 2004/07/05 16:51:50; author: ijacobs; state: Exp; lines: +1 -1
link fix
----------------------------
revision 1.678
date: 2004/07/05 16:50:03; author: ijacobs; state: Exp; lines: +2 -2
editorial
----------------------------
revision 1.677
date: 2004/07/05 16:49:37; author: ijacobs; state: Exp; lines: +2 -1
added statement that doc expected to become a rec
----------------------------
revision 1.676
date: 2004/07/05 16:47:55; author: ijacobs; state: Exp; lines: +2 -0
added statement that not covered by any w3c patent policy.
----------------------------
revision 1.675
date: 2004/07/05 16:31:42; author: ijacobs; state: Exp; lines: +1 -1
removed some nbsp
----------------------------
revision 1.674
date: 2004/07/05 15:48:51; author: ijacobs; state: Exp; lines: +1 -1
spell fix
Changes between 8 June 2004 Editor's Draft and the 5 July 2004 Working Draft (diff since 8 June).
---------------------------- revision 1.673 date: 2004/07/05 15:45:47; author: ijacobs; state: Exp; lines: +12 -9 updated status; attempt at 5 July publication ---------------------------- revision 1.672 date: 2004/07/05 15:36:57; author: ijacobs; state: Exp; lines: +11 -10 per skw comments, changed some instances of license to allow or specify ---------------------------- revision 1.671 date: 2004/07/05 15:32:17; author: ijacobs; state: Exp; lines: +6 -4 moved a Note per http://lists.w3.org/Archives/Public/www-archive/2004Jun/att-0037/webarch-ann-skw-f.html#_msocom_47 ---------------------------- revision 1.670 date: 2004/07/05 15:31:26; author: ijacobs; state: Exp; lines: +5 -4 http://lists.w3.org/Archives/Public/www-archive/2004Jun/att-0037/webarch-ann-skw-f.html#_msocom_46 Turned from negative to positive ---------------------------- revision 1.669 date: 2004/07/05 15:28:22; author: ijacobs; state: Exp; lines: +2 -2 http://lists.w3.org/Archives/Public/www-archive/2004Jun/att-0037/webarch-ann-skw-f.html#_msoanchor_40 s/create/use ---------------------------- revision 1.668 date: 2004/07/05 15:25:18; author: ijacobs; state: Exp; lines: +2 -1 http://lists.w3.org/Archives/Public/www-archive/2004Jun/att-0037/webarch-ann-skw-f.html#_msocom_37 Sentence changed to "Globally adopted assignment policies make some URIs appealing as general-purpose identifiers." ---------------------------- revision 1.667 date: 2004/07/05 15:23:36; author: ijacobs; state: Exp; lines: +2 -1 Attempted to improve a GPN based on: http://lists.w3.org/Archives/Public/www-archive/2004Jun/att-0037/webarch-ann-skw-f.html#_msocom_36 However, I agree with SKW that this GPN requires more review. ---------------------------- revision 1.666 date: 2004/07/05 15:18:24; author: ijacobs; state: Exp; lines: +3 -2 Change to GPN language per http://lists.w3.org/Archives/Public/www-archive/2004Jun/att-0037/webarch-ann-skw-f.html#_msoanchor_34 ---------------------------- revision 1.665 date: 2004/07/05 15:15:26; author: ijacobs; state: Exp; lines: +2 -2 Per http://lists.w3.org/Archives/Public/www-archive/2004Jun/att-0037/webarch-ann-skw-f.html#_msocom_32 Changed GPN: A URI owner SHOULD NOT create arbitrarily different URIs for the same resource. to: A URI owner SHOULD NOT associate arbitrarily different URIs with the same resource. ---------------------------- revision 1.664 date: 2004/07/05 15:13:55; author: ijacobs; state: Exp; lines: +0 -7 Per skw30, http://lists.w3.org/Archives/Public/www-archive/2004Jun/att-0037/webarch-ann-skw-f.html#_msoanchor_30 deleted: "Are there resources that are not identified by any URI? In a system where the only resource identification system is the URI, the question is only of philosophical interest. The advent of other resource identification systems may change the nature of this question and answer. ---------------------------- revision 1.663 date: 2004/07/05 15:12:05; author: ijacobs; state: Exp; lines: +13 -13 Per skw http://lists.w3.org/Archives/Public/www-archive/2004Jun/att-0037/webarch-ann-skw-f.html#_msoanchor_29: 1) s/assign/associate in many instances I found an instance of "associate" in RFC2396bis (1.2.2) and thus felt comfortable making this change. ---------------------------- revision 1.662 date: 2004/07/04 20:46:58; author: ijacobs; state: Exp; lines: +20 -15 Based on http://lists.w3.org/Archives/Public/www-archive/2004Jun/att-0037/webarch-ann-skw-f.html#_msoanchor_25 Global examination of the usage of link. In many situations, s/link/hypertext link where it made sense. Also added a note next to the definition of "link": Note: In this document, the term "link" generally means "relationship", not "physical connection". ---------------------------- revision 1.661 date: 2004/07/04 20:40:34; author: ijacobs; state: Exp; lines: +1 -1 one more instance of s/identification mechanism/identification system per skw ---------------------------- revision 1.660 date: 2004/07/04 20:39:17; author: ijacobs; state: Exp; lines: +16 -16 Per comments from swk, reduced use of word "mechanism" In particular: s/identification mechanism/identification system/ ---------------------------- revision 1.659 date: 2004/07/04 20:35:40; author: ijacobs; state: Exp; lines: +1 -1 Per http://lists.w3.org/Archives/Public/www-archive/2004Jun/att-0037/webarch-ann-skw-f.html#_msocom_24 d/mechanism ---------------------------- revision 1.658 date: 2004/07/04 20:34:51; author: ijacobs; state: Exp; lines: +1 -1 Per http://lists.w3.org/Archives/Public/www-archive/2004Jun/att-0037/webarch-ann-skw-f.html#_msocom_23 s/used/used consistently/ ---------------------------- revision 1.657 date: 2004/07/04 20:31:10; author: ijacobs; state: Exp; lines: +1 -1 Per http://lists.w3.org/Archives/Public/www-archive/2004Jun/att-0037/webarch-ann-skw-f.html#_msoanchor_19 s/sequence/sequencing constraints ---------------------------- revision 1.656 date: 2004/07/04 20:30:41; author: ijacobs; state: Exp; lines: +1 -1 For HTTP 404, s/message/status code ---------------------------- revision 1.655 date: 2004/07/04 20:27:48; author: ijacobs; state: Exp; lines: +1 -1 Inspired by http://lists.w3.org/Archives/Public/www-archive/2004Jun/att-0037/webarch-ann-skw-f.html#_msocom_16 s/transparent/evident ---------------------------- revision 1.654 date: 2004/07/04 20:27:00; author: ijacobs; state: Exp; lines: +1 -1 Per http://lists.w3.org/Archives/Public/www-archive/2004Jun/att-0037/webarch-ann-skw-f.html#_msocom_15 Added to end of para: "by addressing the fact that the error has occurred." ---------------------------- revision 1.653 date: 2004/07/04 20:24:17; author: ijacobs; state: Exp; lines: +1 -1 Per http://lists.w3.org/Archives/Public/www-archive/2004Jun/att-0037/webarch-ann-skw-f.html#_msoanchor_13 Added HTTPEXT ---------------------------- revision 1.652 date: 2004/07/04 20:14:47; author: ijacobs; state: Exp; lines: +8 -9 http://lists.w3.org/Archives/Public/www-archive/2004Jun/att-0037/webarch-ann-skw-f.html#_msocom_12 - Dissolved paragraph in question. - Moved first sentence to first sentence of following para. - Rewrote second paragraph and moved to after bulleted list. ---------------------------- revision 1.651 date: 2004/07/04 20:08:58; author: ijacobs; state: Exp; lines: +2 -1 Per http://lists.w3.org/Archives/Public/www-archive/2004Jun/att-0037/webarch-ann-skw-f.html#_msocom_11 Added xref to coneg ---------------------------- revision 1.650 date: 2004/07/04 19:57:48; author: ijacobs; state: Exp; lines: +21 -13 Some edits to the introduction based on http://lists.w3.org/Archives/Public/www-archive/2004Jun/att-0037/webarch-ann-skw-f.html#_msocom_8 In particular, added this note: Note: In this document, the noun "representation" means "octets that encode resource state information". These octets do not necessarily describe the resource, or portray a likeness of the resource, or represent the resource in other senses of the word "represent". ---------------------------- revision 1.649 date: 2004/07/04 19:29:28; author: ijacobs; state: Exp; lines: +4 -4 Minor editorial changes based on this comment: http://lists.w3.org/Archives/Public/www-archive/2004Jun/att-0037/webarch-ann-skw-f.html#_msocom_5 ---------------------------- revision 1.648 date: 2004/07/04 19:27:08; author: ijacobs; state: Exp; lines: +2 -1 Took into account http://lists.w3.org/Archives/Public/www-archive/2004Jun/att-0037/webarch-ann-skw-f.html#_msocom_4 s/a travel scenario/ Examples such as the following travel scenario/ ---------------------------- revision 1.647 date: 2004/07/04 19:23:55; author: ijacobs; state: Exp; lines: +3 -3 In an attempt to satisfy an swk comment: http://lists.w3.org/Archives/Public/www-archive/2004Jun/att-0037/webarch-ann-skw-f.html#_msocom_1 Changed first para of abstract to avoid the word "link": "The World Wide Web is a network-spanning information space of interrelated resources. This information space is the basis of, and is shared by, a number of information systems. Within each of these systems, people and software retrieve, create, display, analyze, relate, and reason about resources." Also, checked for other uses of "connect" in the document; replaced one instance with "relate" ---------------------------- revision 1.646 date: 2004/07/04 18:45:41; author: ijacobs; state: Exp; lines: +10 -9 Per 28 June teleconf, http://www.w3.org/2004/06/28-tag-summary.html Made these changes: 1) moved note before 4.2 to third para of 4.1 2) Added this sentence for following para: In practice, some types of content (e.g., audio and video) are generally represented using binary formats. ---------------------------- revision 1.645 date: 2004/07/04 18:42:55; author: ijacobs; state: Exp; lines: +16 -0 Per 28 June teleconf, http://www.w3.org/2004/06/28-tag-summary.html adopted text from NW http://lists.w3.org/Archives/Public/www-tag/2004Jun/0024.html With some edits for readability and length. ---------------------------- revision 1.644 date: 2004/07/04 17:54:54; author: ijacobs; state: Exp; lines: +47 -29 Per DC observation, http://lists.w3.org/Archives/Public/www-archive/2004Jun/0033.html To address this comment: - See TAG issues abstractComponentRefs-37 and DerivedResources-43. - Made these changes: 1) Globally added more context to these refs. See also previous comments from Martin Duerst about clearer idea why tag issues referenced. Still more probably needs to be done here. 2) In the specific place DC identified, removed ref to issue 43 since current TAG state is "we don't know what this issue is about." ---------------------------- revision 1.643 date: 2004/07/04 17:39:41; author: ijacobs; state: Exp; lines: +4 -1 Per DC observation, http://lists.w3.org/Archives/Public/www-archive/2004Jun/0033.html To address this comment: - Overly brief: For example, the assignment of more than one URI for a resource undermines the network effect. how so? no suggestion handy yet. - Made these changes: Instead of adding an example, added an xref to error handling section. ---------------------------- revision 1.642 date: 2004/07/04 17:35:12; author: ijacobs; state: Exp; lines: +3 -3 Per DC observation, http://lists.w3.org/Archives/Public/www-archive/2004Jun/0033.html To address this comment: - Unclear: Thus, the "http" URI specification licenses applications to conclude that authority components in two "http" URIs are equivalent you haven't made the connection between "are equivalent" and "identify the same resource". no suggestion handy just yet. - Changed "are equivalent" to "identify the same resource" ---------------------------- revision 1.641 date: 2004/07/04 17:30:08; author: ijacobs; state: Exp; lines: +8 -9 s/character-for-character/character-by-character (so that only one phrase is used) Also, per DC: Wordy: "Software developers should expect that it will prove useful to be able to share a URI across applications, even if that utility is not initially evident." suggest: "Software developers should expect that sharing a URI across applications will be useful, even if that utility is not initially evident." Also, per DC: "The most straightforward way of establishing that two parties are referring to the same resource is to compare, character-by-character, the URIs they are using. Two URIs that are identical (character for character)" suggest striking the 2nd "(character for character)" Instead: changed "(character for character)" to "in this way" since I'm not sure that syntactic identity is the only kind. ---------------------------- revision 1.640 date: 2004/07/04 17:25:58; author: ijacobs; state: Exp; lines: +4 -4 add some classes so that destination sections numbered automatically. ---------------------------- revision 1.639 date: 2004/07/04 17:25:16; author: ijacobs; state: Exp; lines: +4 -4 add some classes so that destination sections numbered automatically. ---------------------------- revision 1.638 date: 2004/07/04 16:49:53; author: ijacobs; state: Exp; lines: +3 -3 editorial: changed one e.g., to a for example ---------------------------- revision 1.637 date: 2004/07/04 16:47:12; author: ijacobs; state: Exp; lines: +1 -1 Per suggestions from DC and NW, s/MUST NOT/SHOULD NOT in: Agents making use of URIs SHOULD NOT attempt to infer properties of the referenced resource except as licensed by relevant specifications. Furthermore, this is more consistent with the text in the penultimate paragraph of 3.3.1 ---------------------------- revision 1.636 date: 2004/07/04 16:46:23; author: ijacobs; state: Exp; lines: +4 -2 per suggestions from DC and NW, added forward ref from 2.2 to 2.4 ---------------------------- revision 1.635 date: 2004/07/04 16:42:48; author: ijacobs; state: Exp; lines: +1 -1 Per DC suggestion, removed "agents" from abstract and left "people and software" (though it could also be hardware). Agents is defined later. ---------------------------- revision 1.634 date: 2004/07/04 16:41:44; author: ijacobs; state: Exp; lines: +536 -534 moved section on general arch principles to back per DC suggestion ---------------------------- revision 1.633 date: 2004/07/04 16:00:30; author: ijacobs; state: Exp; lines: +6 -6 ensure utf; prepare for 7 July publication =============================================================================
Changes between 10 May 2004 Editor's Draft and the 8 June 2004 Editor's Draft (diff since 10 May).
----------------------------
revision 1.624
date: 2004/06/08 23:08:33; author: ijacobs; state: Exp; lines: +12 -7
some changes in how we discuss authoritative representations
----------------------------
revision 1.623
date: 2004/06/08 23:05:48; author: ijacobs; state: Exp; lines: +20 -20
state in section on URI ownership that representations from URI owners
are authoritative for those URIs.
----------------------------
revision 1.622
date: 2004/06/08 22:59:49; author: ijacobs; state: Exp; lines: +34 -64
put back some missing info on derference details
----------------------------
revision 1.621
date: 2004/06/08 21:24:53; author: ijacobs; state: Exp; lines: +9 -8
editorial, some based on comments from Jacek Kopecky:
http://lists.w3.org/Archives/Public/www-tag/2004May/0026.html
----------------------------
revision 1.618
date: 2004/06/08 18:35:48; author: ijacobs; state: Exp; lines: +2 -3
editorial tweak regarding URI overloading based on comments
from Kendall Clark
http://lists.w3.org/Archives/Public/public-webarch-comments/2004AprJun/0019.html
----------------------------
revision 1.617
date: 2004/06/08 18:24:21; author: ijacobs; state: Exp; lines: +20 -22
edits to section on XML namespaces basd on comments from MSM:
http://lists.w3.org/Archives/Public/public-webarch-comments/2004AprJun/0025.html
----------------------------
revision 1.616
date: 2004/06/08 18:10:54; author: ijacobs; state: Exp; lines: +20 -16
Took into account the following editorial suggestions from Mario Jeckle
http://lists.w3.org/Archives/Public/public-webarch-comments/2004AprJun/0004.html
The order of the techniques mentioned in brackets in the first sentence
of section 4 should be changed to "XHTML, RDF/XML, XMIL, XLink, CSS, and
PNG" to be consistent with the following section.
After the first paragraph of section 4 insertion of an additional
comment recommending the re-use of at least the meta-format (such as
XML) is helpful even if a concrete instance format (e.g, myFunnyML) is
not possible or intended.
The sentence "textual formats also have the considerable advantage that
they can be directly read and understood by human beings" should be
formulated more restrictive. Proposed addition: "? can be understood if
sufficient knowledge about the underlying semantics is present or
available".
Section 4.5.3 sketches the "p" element as an example of a XML element
which is "defined in two or more XML formats". Who did we not refer to
the "set" element which is already present in both MathML and SVG? This
would make the statement more precise and also give a useful example.
Below the good practice "Namespace adoption" there is the term "fully
qualified" introduced. Why isn't "qualified" sufficient here also?
In section 4.5.4 there is a bullet-point list collecting reasons for
provide information about a namespace. Should we add "wish to retrieve
the namespace policy" here?
Sect. 4.5.6: It could be helpful to expand "ID" to "unique
identification" the first time it is being used.
Sect. 4.5.6 a type named "xs:ID" is used there. Should this not read "ID
within the namespace assigned to XML Schema" here?
[This one subsumed]
----------------------------
revision 1.615
date: 2004/06/07 22:47:18; author: ijacobs; state: Exp; lines: +7 -18
Per 7 June 2004 tag teleconf,
http://www.w3.org/2001/tag/2003/lc1209/issues.html#hawke3
- Edits to section to 2.2 to remove large number discussion.
- Left in mid/cid as examples where there is hierarchical delegation.
- Note rationale for establishing uri/social entity relationship:
"It is useful for a URI scheme to...". Not sure if that'
sufficient.
----------------------------
revision 1.614
date: 2004/06/07 22:38:29; author: ijacobs; state: Exp; lines: +17 -8
Per 7 June 2004 teleconf,
and
http://lists.w3.org/Archives/Public/public-webarch-comments/2004JanMar/1071.html
http://www.w3.org/2001/tag/2003/lc1209/issues.html#kopecky5
- Some rewrites regarding mappings in section on xml namespaces
- link from qname mappings to this section.
----------------------------
revision 1.613
date: 2004/06/07 19:02:21; author: ijacobs; state: Exp; lines: +108 -109
Per http://www.w3.org/2004/05/14-tag-summary.html,
- s/namespace representation/namespace document.
- Based on discussion with TBL, a number of changes about the
definitions and relations among:
xml namespace
namespace document
namespace uri
----------------------------
revision 1.612
date: 2004/06/07 03:59:03; author: ijacobs; state: Exp; lines: +11 -7
Per http://www.w3.org/2004/05/14-tag-summary.html,
for issue
http://www.w3.org/2001/tag/2003/lc1209/issues.html#clark4b,
Some tweaks regarding links and net effect.
----------------------------
revision 1.611
date: 2004/06/07 03:50:34; author: ijacobs; state: Exp; lines: +4 -1
Per http://www.w3.org/2004/05/14-tag-summary.html,
for issue
http://www.w3.org/2001/tag/2003/lc1209/issues.html#clark1a
In section on with primary/secondary resource, included ref
to dfns in RFC2396bis.
----------------------------
revision 1.610
date: 2004/06/07 03:47:46; author: ijacobs; state: Exp; lines: +5 -2
Per http://www.w3.org/2004/05/14-tag-summary.html,
for issue
http://www.w3.org/2001/tag/2003/lc1209/issues.html#schema20:
In section 4.5.6, new fourth bullet:
<li>In practice, applications may have independent means (such as
those defined in the XPointer specification, [<a>
href="#XPTRFR">XPTRFR</a>] <a
href="http://www.w3.org/TR/2003/REC-xptr-framework-20030325/#shorthand">section
3.2</a>) of locating identifiers inside a document.
----------------------------
revision 1.609
date: 2004/06/07 03:43:10; author: ijacobs; state: Exp; lines: +2 -2
ediotrial
----------------------------
revision 1.608
date: 2004/06/07 03:41:12; author: ijacobs; state: Exp; lines: +11 -12
Per http://www.w3.org/2004/05/14-tag-summary.html,
for issue
http://www.w3.org/2001/tag/2003/lc1209/issues.html#schema18:
In section 4.5.3, changed para to start:
"The type attribute from the W3C XML Schema Instance
namespace "http://www.w3.org/2001/XMLSchema-instance"
([XMLSCHEMA], section 4.3.2) is an example of a
global attribute. It can be used by authors of any vocabulary to make
an assertion in instance data about the type of the element on which
it appears. As a global attribute, it must always be fully
qualified. "
----------------------------
revision 1.607
date: 2004/06/07 03:30:13; author: ijacobs; state: Exp; lines: +3 -2
Per http://www.w3.org/2004/05/14-tag-summary.html,
for issue
http://www.w3.org/2001/tag/2003/lc1209/issues.html#schema17
In section on xml namespaces (4.5.3),
- Modified last sentence of para after story to say: "Namespaces in xml
use URIs in order to obtain the properties of a global namespace."
- Included cross ref to section on URI ownership.
----------------------------
revision 1.606
date: 2004/06/07 03:23:43; author: ijacobs; state: Exp; lines: +25 -16
Per http://www.w3.org/2004/05/14-tag-summary.html,
for issue
http://www.w3.org/2001/tag/2003/lc1209/issues.html#klyne20,
Introduced new section 4.6.
----------------------------
revision 1.605
date: 2004/06/07 03:04:56; author: ijacobs; state: Exp; lines: +2 -3
Per http://www.w3.org/2004/05/14-tag-summary.html,
for issue
http://www.w3.org/2001/tag/2003/lc1209/issues.html#klyne19
Third bullet in section 4.2.4 changed to:
<li>The semantics of combining RDF documents containing multiple
vocabularies is well-defined.
----------------------------
revision 1.604
date: 2004/06/07 03:03:03; author: ijacobs; state: Exp; lines: +1 -1
Previous change should close
http://www.w3.org/2001/tag/2003/lc1209/issues.html#manola30
----------------------------
revision 1.603
date: 2004/06/07 03:02:38; author: ijacobs; state: Exp; lines: +1 -3
Per http://www.w3.org/2004/05/14-tag-summary.html,
- In section 4.2.3, deleted "As part of defining an extensibility
mechanism, specification designers should set expectations about agent
behavior in the face of unrecognized extensions."
----------------------------
revision 1.602
date: 2004/06/07 03:00:51; author: ijacobs; state: Exp; lines: +2 -3
Per http://www.w3.org/2004/05/14-tag-summary.html,
for issue http://www.w3.org/2001/tag/2003/lc1209/issues.html#manola29
GPN now reads:
A data format specification SHOULD provide for version information.
----------------------------
revision 1.601
date: 2004/06/07 02:58:01; author: ijacobs; state: Exp; lines: +12 -5
Per http://www.w3.org/2004/05/14-tag-summary.html,
for issue http://www.w3.org/2001/tag/2003/lc1209/issues.html#diwg4,
Added para to section 3.3:
"Internet media type mechanism does have its limitations. For
instance, media type strings do not support versioning
or other parameters. The TAG issue
mediaTypeManagement-45
concerns the appropriate level of granularity of the media type
mechanism."
----------------------------
revision 1.600
date: 2004/06/07 02:52:25; author: ijacobs; state: Exp; lines: +12 -6
Per http://www.w3.org/2004/05/14-tag-summary.html,
in section 4 tried to talk about protocol extensibility
in section 1.2
----------------------------
revision 1.599
date: 2004/06/07 02:38:50; author: ijacobs; state: Exp; lines: +3 -3
Per http://www.w3.org/2004/05/14-tag-summary.html,
for issue
http://www.w3.org/2001/tag/2003/lc1209/issues.html#schema13,
- Deleted "falling back to default behavior" in section
"Extensibility"
----------------------------
revision 1.598
date: 2004/06/07 02:36:23; author: ijacobs; state: Exp; lines: +2 -2
Per http://www.w3.org/2004/05/14-tag-summary.html,
In section 4, first sentence,
changed order to "XHTML, RDF/XML, SMIL, XLink, CSS and PNG" per
suggestion from MJ.
----------------------------
revision 1.597
date: 2004/06/07 02:35:11; author: ijacobs; state: Exp; lines: +1 -3
Per http://www.w3.org/2004/05/14-tag-summary.html,
change text in 2.7 to "peer-to-peer systems.
----------------------------
revision 1.596
date: 2004/06/07 02:32:32; author: ijacobs; state: Exp; lines: +3 -2
Per http://www.w3.org/2004/05/14-tag-summary.html,
In 2.2, changed sentence about delegation to read:
"This document does not address how the benefits and responsibilities
of URI ownership may be delegated to other parties, such as to a
server manager or to someone who has been delegated part of the URI
space on a given Web server."
----------------------------
revision 1.595
date: 2004/06/07 02:31:07; author: ijacobs; state: Exp; lines: +3 -2
Per http://www.w3.org/2004/05/14-tag-summary.html,
In 3.6.2:
s/authorities servicing URI/URI owner/
----------------------------
revision 1.594
date: 2004/06/07 02:29:58; author: ijacobs; state: Exp; lines: +2 -1
Per http://www.w3.org/2004/05/14-tag-summary.html,
added for 3.6.1:
"there is a benefit to the community in providing representations."
----------------------------
revision 1.593
date: 2004/06/07 02:27:38; author: ijacobs; state: Exp; lines: +1 -1
Per http://www.w3.org/2004/05/14-tag-summary.html,
s/unpredictable/unreliable or unpredictable/
----------------------------
revision 1.592
date: 2004/06/07 01:43:17; author: ijacobs; state: Exp; lines: +17 -27
Per http://www.w3.org/2004/05/14-tag-summary.html,
simplified discussion in 3.5.1 and distinguished transaction requests
from results.
----------------------------
revision 1.591
date: 2004/06/07 01:25:52; author: ijacobs; state: Exp; lines: +2 -4
Deleted:
Note that even though the response to an HTTP POST request may
contain a representation, the response to an HTTP POST request is not
necessarily a representation of the resource identified in the POST
request.
From earlier section since looks like it will fit in 3.5.1
----------------------------
revision 1.590
date: 2004/06/07 01:24:10; author: ijacobs; state: Exp; lines: +3 -2
Per http://www.w3.org/2004/05/14-tag-summary.html,
in 3.5:
added "necessarily" to "the word "unsafe" does not
necessarily mean "dangerous";
s/results/requests in "It is a breakdown of the Web architecture if
agents cannot use URIs to reconstruct a "paper trail" of transaction
requests,"
----------------------------
revision 1.589
date: 2004/06/07 01:22:23; author: ijacobs; state: Exp; lines: +1 -1
chnaged title of GPN in 3.4
----------------------------
revision 1.588
date: 2004/06/07 01:21:40; author: ijacobs; state: Exp; lines: +79 -80
Per http://www.w3.org/2004/05/14-tag-summary.html, significant
edits to 3.4 and 3.4.1:
- New title: Inconsistencies between Representation Data and Metadata
- New first para.
- No more discussion of "authoritative metadata"
- Added example of html + text/plain as not being an inconsistency.
----------------------------
revision 1.587
date: 2004/06/07 00:21:27; author: ijacobs; state: Exp; lines: +68 -59
Per http://www.w3.org/2004/05/14-tag-summary.html, significant
edits to 3.3.2. Fragment Identifiers and Multiple Representations:
- New title: Fragment Identifiers and Content Negotiation
- Defined coneg up front.
- Per ftf meeting, cited three possible outcomes (consistent,
inconsistent, defined in only one spec).
- Distinguish server management error from error on agent
side in case three.
- Refer to CUAP in case there.
- Removed story.
- Removed GPN.
- Removed reference to httpRange-14
----------------------------
revision 1.586
date: 2004/06/06 23:23:39; author: ijacobs; state: Exp; lines: +7 -15
Per http://www.w3.org/2004/05/14-tag-summary.html, edits
in 3.6.2. URI Persistence:
Removed bulleted list. Now talk about inconsistency, and that
defined from perspective of representation provider (or URI
owner).
----------------------------
revision 1.585
date: 2004/06/06 23:07:25; author: ijacobs; state: Exp; lines: +1 -1
Per http://www.w3.org/2004/05/14-tag-summary.html, in 3.3.2:
s/SHOULD NOT/MUST NOT in GPN
----------------------------
revision 1.584
date: 2004/06/06 23:00:44; author: ijacobs; state: Exp; lines: +6 -5
Per http://www.w3.org/2004/05/14-tag-summary.html, edits in 3.3.1:
- Edited the sentence "Parties that draw" to be about syntactic
analysis rather than representations.
- n story, section 3, deleted "by /satimage/oaxaca".
----------------------------
revision 1.583
date: 2004/06/06 22:53:38; author: ijacobs; state: Exp; lines: +10 -10
Per http://www.w3.org/2004/05/14-tag-summary.html, edits in 3.3.1:
- Remove "during a retrieval action" in penultimate para.
- Delete from "Note..." to end of same paragraph.
HOWEVER:
I think that the point made at the ftf meeting that a
resource can be both a primary and secondary resource is
worth making, so I made it at end of section.
----------------------------
revision 1.582
date: 2004/06/06 22:47:25; author: ijacobs; state: Exp; lines: +11 -6
Per http://www.w3.org/2004/05/14-tag-summary.html,
Added:
<li>One cannot carry out an HTTP POST operation
using a URI that identifies a secondary resource.
Combined it in OL in 3.3.1 with:
All Information Resources are primary resources.
----------------------------
revision 1.580
date: 2004/06/06 22:40:22; author: ijacobs; state: Exp; lines: +21 -23
Editorial: moved example of dereference (SVG) to own subsection.
----------------------------
revision 1.579
date: 2004/06/06 22:31:44; author: ijacobs; state: Exp; lines: +64 -85
more editing about info resources, some based on:
http://lists.w3.org/Archives/Member/tag/2004May/0049.html
----------------------------
revision 1.578
date: 2004/06/06 22:07:05; author: ijacobs; state: Exp; lines: +54 -28
starting to incorporate Information resource (new section near
beginning of 4) and also that all Info Resources are primary
resources.
----------------------------
revision 1.574
date: 2004/06/06 21:14:19; author: ijacobs; state: Exp; lines: +0 -11
Per http://www.w3.org/2004/05/14-tag-summary.html,
deleted third para.
----------------------------
revision 1.572
date: 2004/06/06 21:13:04; author: ijacobs; state: Exp; lines: +8 -7
Moved a para about multiple reprs. from different URI owners
form 2.7.2 to 2.3 since not specific to sem web technologies.
----------------------------
revision 1.571
date: 2004/06/06 21:08:15; author: ijacobs; state: Exp; lines: +5 -2
Some edits to sentence on delection of URI ownership authority.
----------------------------
revision 1.570
date: 2004/06/06 21:05:00; author: ijacobs; state: Exp; lines: +7 -6
Per http://www.w3.org/2004/05/14-tag-summary.html,
Section 2.3:
- Added "For example, " before ". When the HTTP protocol is used to
provide representations, the HTTP origin server (defined in
[RFC2616]) is the software agent acting on behalf of the URI
owner."
- Moved previous sentence to section on authoritative metadata.
Section 2.4:
- Removed "normative" in first para.
----------------------------
revision 1.569
date: 2004/06/05 01:18:24; author: ijacobs; state: Exp; lines: +28 -17
Per http://www.w3.org/2004/05/14-tag-summary.html, rewrite of 2.2.2
in terms of indirect identification. Included rhetorical analogy.
Also included this attempt at a definition, taken from RF comments:
"A URI acts as an indirect identifier when it is a component
in a string of references that, taken together, identify
something."
----------------------------
revision 1.568
date: 2004/06/05 00:34:46; author: ijacobs; state: Exp; lines: +32 -28
Per http://www.w3.org/2004/05/14-tag-summary.html,
recast GPN 2.2:
Avoiding URI Overloading: Agents SHOULD find out what resource a URI
identifies before using that URI.
removed from 2.2:
"In many contexts, inconsistent use may not lead to error or cause
harm. However, in some contexts such as the Semantic Web, much of the
value of a relies on consistent use of URIs."
The Semantic Web does not fail in the face of inconsistency, though its
value certainly increases with consistent usage.
----------------------------
revision 1.567
date: 2004/06/05 00:09:26; author: ijacobs; state: Exp; lines: +1 -1
RFC2396bis uses the term "percent-encode" instead of "escape"; that
change was made here as well.
----------------------------
revision 1.566
date: 2004/06/05 00:08:56; author: ijacobs; state: Exp; lines: +18 -26
Deleted this example from 2.1.1 since it is NOT about URI Aliases;
these URIs identify different resources.
-Publish a URI (such as "http://www.example.com/")
for a resource with multiple representations in
different human languages. Agents use content negotiation to select a
representation of this resource according to user preferences for
language.
- Publish one URI per available language of the previous resource,
such as "http://www.example.com/tempo" (the Italian resource)
and "http://www.example.com/tiempo" (the Spanish resource).
One may wish to refer to the language-independent resource or to a
language-specific resource; they are all different resources
identified by different URIs.
----------------------------
revision 1.565
date: 2004/06/04 23:49:34; author: ijacobs; state: Exp; lines: +2 -6
removed more oaxaca example from 2.1.1
----------------------------
revision 1.564
date: 2004/06/04 23:48:11; author: ijacobs; state: Exp; lines: +18 -28
Per http://www.w3.org/2004/05/14-tag-summary.html, in section 2.1,
removed two http URI examples, leaving instead a reference to
section 6 of [URI].
----------------------------
revision 1.563
date: 2004/06/04 23:44:00; author: ijacobs; state: Exp; lines: +2 -2
In 2.1:
s/false negative comparision/false negative
same for positive
----------------------------
revision 1.561
date: 2004/06/04 23:42:22; author: ijacobs; state: Exp; lines: +4 -9
Per http://www.w3.org/2004/05/14-tag-summary.html, deleted
the "URI multiplicity" constraint from the beginning of 2.1. This
text was moved (as an ordinary sentence) to the new subsection:
URI/Resource Relationships.
----------------------------
revision 1.560
date: 2004/06/04 23:40:10; author: ijacobs; state: Exp; lines: +1 -1
editorial: removed an instance of "people" where not necessarily people.
----------------------------
revision 1.559
date: 2004/06/04 23:39:11; author: ijacobs; state: Exp; lines: +120 -64
Per http://www.w3.org/2004/05/14-tag-summary.html, a number
of changes to the beginning of sections 2 and 2.1.
- Replaced initial constraint with a new principle and a new
GPN:
Principle:
Global Identifiers: Global naming leads to global network
effects.
GPN:
Identify with URIs: To benefit from and increase the value of
the World Wide Web, agents should provide URIs as identifiers for
resources.
- Created a new subsection specifically about the benefits
of the URI mechanism. Moved subsequent text up to that section.
- Introduced a little more text about "other mechanisms" for
identifying resources, with some forward links. Also about
the costs of new mechanisms that replicate URIs.
- Created a new subsection about URI/Resource Relationships that
states clearly:
- URI identifies one resource.
- More than one URI may identify same resource.
Also provided a little (new) rationale for each of those
constraints.
- In that subsection, asked some frequently asked questions with
forward pointers to sections with discussion about the
answers. In particular, tried to address the question of
whether resource can have zero identifiers by saying (a) in
world with only URIs, doesn't matter and (b) with advent
of other systems, might change.
- This simplified the initial discussion of 2.1; in second paragraph,
added last sentence about generally higher cost of determining
whether two different URIs identify the same resource.
- Also trying to introduce more 'pro and con' discussion per the
ftf meeting.
- Other text (e.g., on format network effects) was moved to
other sections.
----------------------------
revision 1.558
date: 2004/06/03 23:33:37; author: ijacobs; state: Exp; lines: +2 -2
tweak re: 404 (not found)
----------------------------
revision 1.557
date: 2004/06/03 23:32:55; author: ijacobs; state: Exp; lines: +39 -24
Per http://www.w3.org/2004/05/14-tag-summary.html, in section 1.2.3,
distinguish error correction from error recovery. Related issues:
http://www.w3.org/2001/tag/2003/lc1209/issues.html#clark5
http://www.w3.org/2001/tag/2003/lc1209/issues.html#schema1
http://www.w3.org/2001/tag/2003/lc1209/issues.html#parsia3
----------------------------
revision 1.556
date: 2004/06/03 22:17:19; author: ijacobs; state: Exp; lines: +6 -5
Per http://www.w3.org/2004/05/14-tag-summary.html, editorial:
- 1.1.1, bullet 1: deleted "i.e., " to end of bullet.
- 1.1.2, para 3: s/document involve human activity/document that involve human activity/
- 1.1.2, para 3: Added ref to voicexml2
----------------------------
revision 1.555
date: 2004/06/03 22:08:46; author: ijacobs; state: Exp; lines: +1 -1
editorial:
s/periodically-updated/periodically updated/
----------------------------
revision 1.554
date: 2004/06/03 22:07:59; author: ijacobs; state: Exp; lines: +32 -25
Per http://www.w3.org/2004/05/14-tag-summary.html, in 1.2.1:
- Changed "independent" back to "orthogonal" (globally)
- Deleted "loosely coupled"
- Expanded this paragraph after the first bulleted list:
When two specifications are orthogonal, one may change one without
requiring changes to the other, even if one has dependencies on the
other. For example, although the HTTP specification depends on the URI
specification, the two may evolve independently. This orthogonality
increases the flexibility and robustness of the Web. For example, one
may refer by URI to an image without knowing anything about the format
chosen to represent the image. This has facilitated the introduction
of image formats such as PNG and SVG without disrupting existing
references to image resources.
----------------------------
revision 1.553
date: 2004/06/03 21:28:12; author: ijacobs; state: Exp; lines: +8 -2
Issue http://www.w3.org/2001/tag/2003/lc1209/issues.html#dhm4
Per http://www.w3.org/2004/05/14-tag-summary.html,
In section 1.2.4, modified first paragraph to talk more about
large-scale protocols v. traditional software APIs.
----------------------------
revision 1.552
date: 2004/06/03 21:13:49; author: ijacobs; state: Exp; lines: +19 -12
Issue http://www.w3.org/2001/tag/2003/lc1209/issues.html#dhm3
Per http://www.w3.org/2004/05/14-tag-summary.html,
In section 1.2.2,
* Extended language: A+B
* Extension: B
----------------------------
revision 1.551
date: 2004/06/03 20:37:54; author: ijacobs; state: Exp; lines: +18 -6
Per http://www.w3.org/2004/05/14-tag-summary.html,
2.1.1: Expanded example to show N resources: one language-independent
and N-1 language-specific.
----------------------------
revision 1.550
date: 2004/06/03 20:18:10; author: ijacobs; state: Exp; lines: +0 -3
Per http://www.w3.org/2004/05/14-tag-summary.html,
1.1.3: Deleted
'This categorization is derived from Roy Fielding's work on
"Representational State Transfer" [REST].'
Changes between 7 May 2004 Editor's Draft and the 10 May 2004 Editor's Draft (diff since 7 May; diff since 9 Dec 2003).
Changes between 9 Dec 2003 Last Call Working Draft and the 7 May 2004 Editor's Draft (diff).
----------------------------
revision 1.547
date: 2004/05/10 21:32:07; author: ijacobs; state: Exp; lines: +16 -16
Per 9 Feb 2004 TAG teleconf:
http://www.w3.org/2004/02/09-tag-summary.html
s/namespace document/namespace representation/
----------------------------
revision 1.546
date: 2004/05/10 21:25:10; author: ijacobs; state: Exp; lines: +1 -1
Per TAG decision,
http://www.w3.org/2004/03/02-tag-summary.html#stickler5
s/unreliable/unpredictable
----------------------------
revision 1.531
date: 2004/05/07 23:22:42; author: ijacobs; state: Exp; lines: +4 -1
http://www.w3.org/2004/05/03-tag-summary.html
Per 3 May meeting, added :
Note also that since dereferencing a URI (e.g., using HTTP) does not
involve sending a fragment identifier to a server or other agent,
certain access methods (e.g., HTTP PUT, POST, and DELETE) cannot
be used to interact with secondary resources.
----------------------------
revision 1.530
date: 2004/05/07 23:12:06; author: ijacobs; state: Exp; lines: +2 -7
http://www.w3.org/2001/tag/2003/lc1209/issues.html#parsia20
Per 26 April teleconf, deleted:
Note: The Web Architecture does not require a
formal definition of the commonly used phrase "on the Web."
Informally, a resource is "on the Web" when it has a URI and an agent
can use the URI to retrieve a representation of it using network
protocols (given appropriate access privileges, network connectivity,
etc.).
----------------------------
revision 1.528
date: 2004/05/07 23:01:11; author: ijacobs; state: Exp; lines: +51 -50
moved a section around to try to tell a story of disambiguation
----------------------------
revision 1.507
date: 2004/05/07 20:22:52; author: ijacobs; state: Exp; lines: +13 -8
http://www.w3.org/2001/tag/2003/lc1209/issues.html#kopecky6
Maybe also
http://www.w3.org/2001/tag/2003/lc1209/issues.html#schema20
----------------------------
revision 1.506
date: 2004/05/07 20:10:03; author: ijacobs; state: Exp; lines: +0 -4
http://www.w3.org/2001/tag/2003/lc1209/issues.html#klyne12
Deleted:
"On the other hand, it is considered an error if the semantics of
the fragment identifiers used in two representations of a secondary
resource are inconsistent."
Added text from RFC2396 per
http://www.w3.org/2004/05/03-tag-summary#klyne12
----------------------------
revision 1.505
date: 2004/05/07 20:08:52; author: ijacobs; state: Exp; lines: +2 -1
http://www.w3.org/2001/tag/2003/lc1209/issues.html#klyne11
Added "necessarily" per
http://www.w3.org/2004/04/26-tag-summary#klyne1
----------------------------
revision 1.504
date: 2004/05/07 19:24:08; author: ijacobs; state: Exp; lines: +11 -5
Editorial clarification for
http://www.w3.org/2001/tag/2003/lc1209/issues.html#msm3
----------------------------
revision 1.503
date: 2004/05/07 19:18:13; author: ijacobs; state: Exp; lines: +22 -19
Editorial changes based on
http://www.w3.org/2001/tag/2003/lc1209/issues.html#msm1
NOT treated:
(a) Illustration
The shadows in this graphic convey no information; they are (in the
sense defined by Edward Tufte) chartjunk. Please remove them!
----------------------------
revision 1.502
date: 2004/05/07 18:59:13; author: ijacobs; state: Exp; lines: +9 -8
Editorial changes based on
http://www.w3.org/2001/tag/2003/lc1209/issues.html#schema21
However, did NOT address these:
[Section 1]
The initial part of section 1 is good, but section 1.1 is very jarring
following it. It doesn't flow well at all.
[3.5.1] We are surprised to not see a best practice recommendation here.
[4.5.3] (And elsewhere)
If namespace prefixes are used, there should be a table indicating their
bindings to URIs.
[4.5.6] and [4.5.8] highlight a lot of problems, but make no recommendations
about what to do about them.
----------------------------
revision 1.501
date: 2004/05/07 18:51:38; author: ijacobs; state: Exp; lines: +6 -7
http://www.w3.org/2001/tag/2003/lc1209/issues.html#schema19
Adopted proposed text:
An attribute that is "global," that is, one that might meaningfully appear
on elements of any type, including elements in other namespaces, should be
explicitly placed in a namespace. Local attributes, ones associated with
only a particular element type, need not be included in a namespace since
their meaning will always be clear from the context provided by that
element."
----------------------------
revision 1.500
date: 2004/05/07 18:50:12; author: ijacobs; state: Exp; lines: +3 -2
http://www.w3.org/2001/tag/2003/lc1209/issues.html#schema18
Adopted proposal:
"The xsi:type attribute, provided by W3C XML Schema for use in XML
instance documents, is an example of a global attribute."
----------------------------
revision 1.499
date: 2004/05/07 18:48:23; author: ijacobs; state: Exp; lines: +1 -2
http://www.w3.org/2001/tag/2003/lc1209/issues.html#schema17
s/ that can be understood in any context//
Per http://www.w3.org/2004/03/22-tag-summary.html#schema17
----------------------------
revision 1.498
date: 2004/05/07 18:46:24; author: ijacobs; state: Exp; lines: +1 -1
http://www.w3.org/2001/tag/2003/lc1209/issues.html#schema15
s/JPEG/SVG
[My understanding is: no binary in XML. The JPEG could
be encoded (base64), but happy to put svg instead]
----------------------------
revision 1.497
date: 2004/05/07 18:39:18; author: ijacobs; state: Exp; lines: +38 -17
http://www.w3.org/2001/tag/2003/lc1209/issues.html#schema4
Added some text from RFC2396 bis per 3 May teleconf. The new
text does NOT say "don't use content negotiation".
----------------------------
revision 1.496
date: 2004/05/07 18:22:58; author: ijacobs; state: Exp; lines: +23 -23
Editorial changes based on
http://www.w3.org/2001/tag/2003/lc1209/issues.html#lesch1
----------------------------
revision 1.495
date: 2004/05/07 18:15:56; author: ijacobs; state: Exp; lines: +4 -5
http://www.w3.org/2001/tag/2003/lc1209/issues.html#gilman1
- Removed legal case as example.
- changed "application context may required" to "favor"
----------------------------
revision 1.494
date: 2004/05/07 18:12:05; author: ijacobs; state: Exp; lines: +1 -1
This text satisfies
http://www.w3.org/2001/tag/2003/lc1209/issues.html#laskey1
----------------------------
revision 1.493
date: 2004/05/07 18:09:01; author: ijacobs; state: Exp; lines: +6 -0
added good practice for URI owners in response to:
http://www.w3.org/2001/tag/2003/lc1209/issues.html#clark12
----------------------------
revision 1.492
date: 2004/05/07 18:01:24; author: ijacobs; state: Exp; lines: +3 -6
http://www.w3.org/2001/tag/2003/lc1209/issues.html#clark11
Edited this sentence:
Formats that allow content authors to use URIs instead of local
identifiers foster the "network effect": the value of these formats
grows with the size of the deployed Web.
----------------------------
revision 1.491
date: 2004/05/07 17:54:02; author: ijacobs; state: Exp; lines: +1 -1
I think edited text in 3.4 might address
http://www.w3.org/2001/tag/2003/lc1209/issues.html#clark8
----------------------------
revision 1.490
date: 2004/05/07 17:52:02; author: ijacobs; state: Exp; lines: +1 -1
http://www.w3.org/2001/tag/2003/lc1209/issues.html#clark7
Attempt to soften claim about cost of overloading by adding "often"
----------------------------
revision 1.489
date: 2004/05/07 17:50:19; author: ijacobs; state: Exp; lines: +12 -4
http://www.w3.org/2001/tag/2003/lc1209/issues.html#clark5
No longer talks about silent recovery, but rather recovery
without user consent.
Some text taken from finding:
"Consent does not necessarily imply that the receiving agent must
interrupt the user and require selection of one option or another. The
user may indicate through pre-selected configuration options, modes,
or selectable user interface toggles, with appropriate reporting to
the user when the agent detects an error."
This GPN also updated:
Authoritative metadata: Agents MUST NOT ignore authoritative metadata
unless the user given consent to this behavior.
----------------------------
revision 1.488
date: 2004/05/04 23:41:45; author: ijacobs; state: Exp; lines: +4 -2
http://www.w3.org/2001/tag/2003/lc1209/issues.html#diwg3
Added "or transformed dynamically
to the hardware or software capabilities of the recipient" to
section 3.4
----------------------------
revision 1.487
date: 2004/05/04 23:33:46; author: ijacobs; state: Exp; lines: +14 -0
NEW: Added a paragraph to scope of document on voice browsing and
other interaction contexts.
----------------------------
revision 1.486
date: 2004/05/04 22:49:27; author: ijacobs; state: Exp; lines: +1 -1
Based on comment from Voice WG [1], changed:
"It is a breakdown of the Web architecture if agents cannot use URIs
to reconstruct a "paper trail" of transactions"
to
"It is a breakdown of the Web architecture if agents cannot use URIs
to reconstruct a "paper trail" of transaction results"
[1] http://www.w3.org/2004/03/02-tag-summary.html#voice-liaison
(see discussion of 3.4.2)
----------------------------
revision 1.485
date: 2004/05/04 22:07:27; author: ijacobs; state: Exp; lines: +2 -1
added link to summary
----------------------------
revision 1.480
date: 2004/05/03 15:57:34; author: ijacobs; state: Exp; lines: +30 -27
Per Martin Duerst Comment:
http://lists.w3.org/Archives/Public/public-webarch-comments/2004Feb/0031.html
Now only using principle, constraint, good practice (in that order).
Also highlighted in abstract
----------------------------
revision 1.479
date: 2004/05/03 15:46:57; author: ijacobs; state: Exp; lines: +5 -5
http://www.w3.org/2001/tag/2003/lc1209/issues.html#duerst1
Changed indicated titles of GPNs
----------------------------
revision 1.478
date: 2004/04/28 20:31:40; author: ijacobs; state: Exp; lines: +26 -25
http://www.w3.org/2001/tag/2003/lc1209/issues.html#kopecky1
- Moved story from beginning of 3.5 to a few paragraphs in.
- Moved one sentence from 3.5 story to 3.5.1 story.
----------------------------
revision 1.477
date: 2004/04/28 20:24:43; author: ijacobs; state: Exp; lines: +18 -15
http://www.w3.org/2001/tag/2003/lc1209/issues.html#kopecky1
Did the following editorial (or they were subsumed):
1 under first story in point 2, application/xml+xhtml should be
application/xhtml+xml
1.2, "principles apply *to* across all three bases" - drop the "to"
1.2.1 2nd para: "The fact, for example, that *the* an image..." - drop
the "the"
2.3.1 last sentence misses a 'when': "URI ambiguity arises *when* a URI
is used to identify two..."
3.6.1 should point to 4.5.4 as a good example
3.6.2 second bullet should probably provide a better example, mentioning
the intended semantics of the resource
4 second para - something missing where the X is in "Below we describe
some characteristics of a data format X make it easier to integrate into
the Web architecture."
4.3 remove the 'the': "Experience shows that *the* allowing authors to
separate content,..."
4.3 last sentence missing '-ity': "this follows from the principle of
orthogonal*ity* of specifications".
4.5.3 para below story: "(for example, suppose that the "p" element is
defined in two or more XML formats)" - I suggest that a more concrete
example be added, like mentioning two different meanings possible for
the element "p".
4.5.3 "The type attribute from W3C XML Schema..." should be
distinguished from the type attribute on element declarations; the
customary reference is xsi:type. The whole paragraph doesn't mention
"instance" and says incorrectly that the type attribute is defined the
W3C XML Schema namespace (there are multiple XML Schema namespaces, see
last para of
http://www.w3.org/TR/xmlschema-1/#Instance_Document_Constructions)
5 Secondary resource definition doesn't parse, probably should drop the
second "that".
Did NOT do:
5 A Link does not need to be internal to a representation of any of the
two (or more) resources between which there is a relationship, the
definition might want to mention that.
----------------------------
revision 1.476
date: 2004/04/28 20:02:55; author: ijacobs; state: Exp; lines: +7 -2
Per http://www.w3.org/2001/tag/2003/lc1209/issues.html#kopecky1,
added to end of 3.6.1:
"For example, the owner of an XML Namespace should
provide a Namespace Document; below
we discuss useful characteristics of a Namespace Document."
----------------------------
revision 1.475
date: 2004/04/28 19:54:45; author: ijacobs; state: Exp; lines: +7 -6
http://www.w3.org/2001/tag/2003/lc1209/issues.html#dhm7
In GPNs, s/server manager/representation provider/ which I think
is true in its more general form. There is also a connection
between URI owner and "providing a representation" in the
section on authoritative metadata. Not sure yet whether
there needs to be a more formal definition of a representation
provider.
----------------------------
revision 1.474
date: 2004/04/28 19:49:58; author: ijacobs; state: Exp; lines: +34 -33
http://www.w3.org/2001/tag/2003/lc1209/issues.html#dhm7
Once more, in an attempt to reduce the number of subjects
of GPNs:
s/language|format designer/[format] specification/ in the GPNs.
----------------------------
revision 1.473
date: 2004/04/28 19:33:37; author: ijacobs; state: Exp; lines: +42 -35
http://www.w3.org/2001/tag/2003/lc1209/issues.html#dhm7
---
* "authors of a specification" vs "language designer" vs "format
designer"
The distinction between format and language is said to be null in the
document; I believe that usually, format is associated to the syntactic
part of a language (which also includes the semantics); I think that at
least the terms should be used consistently (ie either 'language
designer' or 'format designer') in the conformance requirements, if only
for ease of reading.
Also, the terms "authors of a specifications" seems to be bound to the
same type of subjects, but probably with a wider scope - maybe is there
a way to merge all these terms in one?
--
1) In GPNs, s/Language designer/Specification designer/
2) In document, s/specification author/specification designer/
s/author/content author/
s/developer/software developer/
3) Moved note about format v. language to section on
audience, and introduce phrase "specification designer" as
an encompassing term.
----------------------------
revision 1.472
date: 2004/04/28 18:59:21; author: ijacobs; state: Exp; lines: +3 -3
http://www.w3.org/2001/tag/2003/lc1209/issues.html#dhm7
s/user agent/agent in
"Agents should detect such inconsistencies but should not
resolve them without involving the user."
----------------------------
revision 1.471
date: 2004/04/28 18:58:29; author: ijacobs; state: Exp; lines: +3 -3
http://www.w3.org/2001/tag/2003/lc1209/issues.html#dhm7
Consistent with "Authoritative Metadata" finding and
this reviewer's comment:
Changed "User agents MUST NOT silently ignore authoritative
metadata. "
to
"Agents MUST NOT silently ignore authoritative metadata. "
----------------------------
revision 1.470
date: 2004/04/28 18:56:16; author: ijacobs; state: Exp; lines: +6 -6
s/uri publisher/uri owner per
http://www.w3.org/2001/tag/2003/lc1209/issues.html#dhm7
This is also consistent with eliminating "resource owner",
also suggested by the reviewer.
----------------------------
revision 1.469
date: 2004/04/28 18:15:04; author: ijacobs; state: Exp; lines: +11 -10
http://www.w3.org/2001/tag/2003/lc1209/issues.html#dhm6
Agreed with reviewer based on "Authoritative Metadata" Finding.
Removed "server" from GPN.
Also tweaked some text regarding "authority responsible for
domain X":
In this document, the phrase "authority responsible for domain X"
indicates that the same entity owns those URIs where the authority
component is domain X.
----------------------------
revision 1.468
date: 2004/04/28 17:19:41; author: ijacobs; state: Exp; lines: +6 -5
http://www.w3.org/2001/tag/2003/lc1209/issues.html#dhm5
Editorial changes to text on Unicode.
----------------------------
revision 1.467
date: 2004/04/27 23:07:02; author: ijacobs; state: Exp; lines: +3 -3
Did not implement the following suggestions from sandro hawke:
===========================================
== Comment 2, 1. Introduction:
The server responds with a representation that includes XHTML
data and the Internet Media Type "application/xml+xhtml".
In the graphic, you show the media type as text/html, which is
probably the better choice for simplicity's sake.
Rationale: Adjusted image to application/xhtml+xml.
===========================================
== Comment 3, 1.1.3 Principles, Constraints, and Good Practice
This categorization is derived from Roy Fielding's work on
"Representational State Transfer" [REST]. Authors of protocol
specifications in particular should invest time in understanding
the REST model and consider the role to which of its principles
could guide their design: statelessness, clear assignment of
roles to parties, uniform address space, and a limited, uniform
set of verbs.
The first sentence is fine, the second reads rather like a paid
product placement. Is Fielding's thesis that much better than every
other work ever written on distributed systems design that it merits
strong recommendation in the section introducing labeling terms? If
you want to save this text, put it in a Recommended Reading section.
===========================================
== Comment 7, 1.2.4. Protocol-based Interoperability
Did NOT add a GPN.
http://www.w3.org/2001/tag/2003/lc1209/issues.html#hawke1
=======================
http://www.w3.org/2001/tag/2003/lc1209/issues.html#hawke6
I would suggest instead [of "secondary resource"] that you:
(1) Name the the portion of the URI up the the "#". TimBL has
called this the "racine", but I like "stem", "trunk", or
maybe even "non-fragment portion".
(2) Call the resource identified by a URI's stem the "stem
resource", or something like that.
=======================
----------------------------
revision 1.466
date: 2004/04/27 23:06:03; author: ijacobs; state: Exp; lines: +6 -3
http://www.w3.org/2001/tag/2003/lc1209/issues.html#hawke10
Tried to clarify meaning of "safe" by adding note:
"Note: In this context, the word "unsafe" does not mean
"dangerous"; the term "safe" is used in section 9.1.1 of
[RFC2616] and "unsafe" is the natural opposite."
----------------------------
revision 1.465
date: 2004/04/27 22:59:59; author: ijacobs; state: Exp; lines: +4 -4
Followed
http://www.w3.org/2001/tag/2003/lc1209/issues.html#hawke9
In 3.2, s/electronic data/data
----------------------------
revision 1.464
date: 2004/04/27 22:59:17; author: ijacobs; state: Exp; lines: +5 -5
Followed suggestion of
http://www.w3.org/2001/tag/2003/lc1209/issues.html#hawke8
s/representation of the state of a resource/representation of a
resource/
However, left "resource state" elsewhere.
----------------------------
revision 1.462
date: 2004/04/27 22:43:01; author: ijacobs; state: Exp; lines: +17 -6
markup fixes, added more example of sameAs per
http://www.w3.org/2001/tag/2003/lc1209/issues.html#hawke7
----------------------------
revision 1.461
date: 2004/04/27 22:16:37; author: ijacobs; state: Exp; lines: +36 -40
Proposed fix to
http://www.w3.org/2001/tag/2003/lc1209/issues.html#hawke3
in previous edits.
In this draft, adopted SH proposal to s/URI ambiguity/URI overloading/
http://www.w3.org/2001/tag/2003/lc1209/issues.html#hawke4
As a result I *also* deleted the paragraph on natural language
ambiguity; this seems less and less relevant. I substituted
a paragraph at the end of the section on authoritative metadata:
"Note that the choice and expressive power of a format can affect
how precisely a representation provider communicates resource state.
The use of natural language to communicate resource state may lead to
ambiguity about what the associated resource is. This ambiguity can in
turn lead to URI overloading."
----------------------------
revision 1.460
date: 2004/04/27 21:56:05; author: ijacobs; state: Exp; lines: +10 -11
http://lists.w3.org/Archives/Public/public-webarch-comments/2004Feb/0018.html
===========================================
== Comment 9, 2.2. URI Ownership
... the "uuid" scheme ...
and
... the "md5" scheme ...
but you don't give references. They are not on IANA's list. I pay
some attention, and I'm not aware of a stable specification for either
one. The spec on DanC's list for UUID has long since expired; the
reference for MD5 is simply to a hypothetical use of it.
For uuid you could use urn:nid-5, but that's technically not a
"URI scheme":
http://www.iana.org/assignments/urn-namespaces
http://lists.research.netsol.com/pipermail/urn-nid/2002-July/000308.html
Maybe you can says "such as a possible 'UUID' scheme", etc, or you
could use WebDAV's unique-lock-token scheme.
Instead:
Merged "Random number" and "Checksums" list items into one
list item:
"Large numbers. The generation of a fairly large random
number or a checksum
reduces the risk of ambiguity to a calculated small risk.
A draft "uuid" scheme adopted this approach; one could also
imagine a scheme based on md5 checksums."
----------------------------
revision 1.458
date: 2004/04/27 21:47:31; author: ijacobs; state: Exp; lines: +5 -5
Agreed with and implemented
http://www.w3.org/2001/tag/2003/lc1209/issues.html#hawke2
----------------------------
revision 1.457
date: 2004/04/27 21:38:14; author: ijacobs; state: Exp; lines: +12 -7
As suggested by SH, added forward link. However, did not
add a GPN. Added "View source effect" to the glossary.
http://lists.w3.org/Archives/Public/public-webarch-comments/2004Feb/0018.html
===========================================
== Comment 7, 1.2.4. Protocol-based Interoperability
It is common for programmers working with the Web to write code
that generates and parses these messages directly. It is less
common, but not unusual, for end users to have direct exposure to
these messages. This leads to the well-known "view source"
effect, whereby users gain expertise in the workings of the
systems by direct exposure to the underlying protocols.
This seems out of place. I get the point, but it's never summed up.
And I don't see how it belongs in 1.2 General Architecture Principles.
I think you mean:
Good practice: design protocols and data formats which
people can view and reproduce with a minimum of special tools and
effort.
[ Ahhh, this is finally covered in Section 4.1; maybe a forward link? ]
and maybe:
Good practice: user agents should allow user to look "inside" to
see (and even manipulate) the protocol interactions the agent is
performing on behalf of the user.
----------------------------
revision 1.456
date: 2004/04/27 21:15:18; author: ijacobs; state: Exp; lines: +7 -7
Based on comment from SH:
http://lists.w3.org/Archives/Public/public-webarch-comments/2004Feb/0018.html
QUOTE
===========================================
== Comment 6, 1.2.2. Extensibility:
The following applies to languages, in particular the
specifications of data formats, of message formats, and
URIs. Note: This document does not distinguish in any formal way
the terms "format" and "language." Context has determined which
term is used.
I can't really parse the first sentence. Maybe you mean something like:
The data formats and (more generally) formal languages used
in the bodies of messages and even in the text of URIs can be
defined to have certain properties to promote evolution and
interoperation.
/QUOTE
Changed to:
"Below we discuss the property of "extensibility," exhibited by URIs
and some data and message formats, which promotes technology evolution and
interoperability. Note: This document does not
distinguish in any formal way the terms "format" and "language."
Context determines which term is used."
----------------------------
revision 1.455
date: 2004/04/27 21:06:03; author: ijacobs; state: Exp; lines: +3 -3
Accepted proposal from SH:
http://lists.w3.org/Archives/Public/public-webarch-comments/2004Feb/0018.html
===========================================
== Comment 4, 1.2.1. Orthogonal Specifications:
... agents can interact with any identifier ...
That's ambiguous. Replace "with" with "using" and I think you're
okay. Otherwise it sounds rather like the identifier is one of the
parties doing something in an interaction.
----------------------------
revision 1.454
date: 2004/04/27 21:04:26; author: ijacobs; state: Exp; lines: +5 -5
Accepted proposal from SH:
http://lists.w3.org/Archives/Public/public-webarch-comments/2004Feb/0018.html
===========================================
== Comment 1, 1. Introduction:
Identification. Each resource is identified by a URI. In this
travel scenario, the resource is about the weather in Oaxaca and
the URI... ^^^^^
This was jarring to read. The text up to that point is simple and
direct, but suddenly here there's handwaving with "about." What *is*
the resource identified by that URI? Fortunately, in the picture you
answer this question.
Suggested text:
Each resource is identified by a URI. In this travel scenario, the
resource is a periodically-updated report on the weather in Oaxaca,
and the URI ...
----------------------------
revision 1.453
date: 2004/04/27 20:44:32; author: ijacobs; state: Exp; lines: +24 -21
More clean-up of resource owner v. URI owner.
I hope this resolves
http://www.w3.org/2001/tag/2003/lc1209/issues.html#pps1
----------------------------
revision 1.452
date: 2004/04/27 20:35:03; author: ijacobs; state: Exp; lines: +3 -3
Previous changes take into account these issues:
http://www.w3.org/2001/tag/2003/lc1209/issues.html#stickler5
http://www.w3.org/2001/tag/2003/lc1209/issues.html#stickler6
http://www.w3.org/2001/tag/2003/lc1209/issues.html#stickler7
NOT DONE from Patrick's comments:
------------
Section 3.2, para 1, last sentence:
Consider changing to "A message may even include metadata about the
message itself (for message-integrity checks, for instance).
Rationale: This is about the message metadata, not the message,
I believe.
------------
Section 3.3.1, last para, last sentence:
This sentence seems misleading, as if one can infer something
about the nature of a secondary resource by interpreting a
URI reference with fragement identifier.
One cannot infer the nature of any URI denoted resource based
either on the URI *or* based on any representation obtained by
dereferencing that URI, either directly, or for URI references
with fragment identifiers, by first dereferencing the base URI
and interpreting the fragment in terms of the MIME type of
the returned represenatation.
This last sentence could either be removed or clarified/reworked.
-------------
These issues:
http://www.w3.org/2001/tag/2003/lc1209/issues.html#stickler2
http://www.w3.org/2001/tag/2003/lc1209/issues.html#stickler3
http://www.w3.org/2001/tag/2003/lc1209/issues.html#stickler4
http://www.w3.org/2001/tag/2003/lc1209/issues.html#stickler9
http://www.w3.org/2001/tag/2003/lc1209/issues.html#stickler10
----------------------------
revision 1.451
date: 2004/04/27 20:24:43; author: ijacobs; state: Exp; lines: +3 -3
Per stickler comments:
s/cell phone/mobile phone
----------------------------
revision 1.450
date: 2004/04/27 20:21:13; author: ijacobs; state: Exp; lines: +13 -13
Deleted "Resource owner" from the document, replacing it with
URI owner.
----------------------------
revision 1.449
date: 2004/04/27 20:11:32; author: ijacobs; state: Exp; lines: +13 -7
Clarified per suggestion of stickler1
http://www.w3.org/2001/tag/2003/lc1209/issues.html#stickler1
Section 3.6, para 1:
- Per suggestion from PS, added two more examples of
unreliability.
- Continue to move away from "resource owner" (since nobody
owns the weather in Oaxaca) to "URI owner".
----------------------------
revision 1.448
date: 2004/04/27 20:05:51; author: ijacobs; state: Exp; lines: +9 -7
Clarified per suggestion of stickler1
http://www.w3.org/2001/tag/2003/lc1209/issues.html#stickler1
Story in 3.5.1 on unsafe interactions and accountability.
----------------------------
revision 1.447
date: 2004/04/27 19:34:16; author: ijacobs; state: Exp; lines: +24 -17
Per suggestion of stickler1
http://www.w3.org/2001/tag/2003/lc1209/issues.html#stickler1
"Section 3.4, para 2:
The text of this paragraph is a bit too strong regarding URI owner's
rights.
The owner of a URI has the right to decide which representations
of the denoted resource are accessible via that URI -- but in fact
anyone has the license to create a representation of that resource,
and indirectly associate that representation via another URI
that is declared (e.g. using own:sameAs) as semantically equivalent.
I.e. the rights of the owner of a URI are limited to the access of
representations via that particular URI, not (necessarily) to total
control of the resource denoted as well as any and all representations
of that resource (accessible via other URIs)."
Did two things:
1) Added this to the section on future directions and URIs:
"One consequence of this direction is that URIs syntactically
different can be used to identify the same resource. This means that
multiple parties may create representations of the (same) resource,
all available for retrieval using multiple URIs. The URI owner's
rights (e.g., to provide authoritative representation metadata) extend
only to the representations served for requests given that URI."
2) Changed:
In our travel scenario, the authority
responsible for "weather.example.com" has license to create
representations of this resource. Which representation(s) Nadia receives
depends on a number of factors, including:
to:
In our travel scenario, the owner
of "http://weather.example.com/oaxaca" provides the
authoritative metadata for representations retrieved for
that URI. Precisely which representation(s) Nadia receives
depends on a number of factors, including:
----------------------------
revision 1.446
date: 2004/04/27 19:15:55; author: ijacobs; state: Exp; lines: +7 -5
stickler1
http://www.w3.org/2001/tag/2003/lc1209/issues.html#stickler1
Section 3.4, para 1, last sentence:
The phrase "authoritative interpretation of representations of
the resource" is a bit unclear. The owner of the URI can specify
the denotation of the URI and what representations of that
resource are accessible, but is it not the case that the MIME
type specifications define the interpretation of any given
representation -- insofar as the web architecture is concerned?
I.e., for a given representation, it is the MIME type specification
that defines the interpretation of that representation, not the
owner of the URI denoting the represented resource. ???
FIXED (though might require additional editing) according
to the "Authoritative Metadata" finding.
----------------------------
revision 1.445
date: 2004/04/27 19:09:00; author: ijacobs; state: Exp; lines: +9 -13
Per suggestion of stickler1
http://www.w3.org/2001/tag/2003/lc1209/issues.html#stickler1
Removed first part of para after story, since it said almost
the same thing as following paragraph and was less clear.
----------------------------
revision 1.444
date: 2004/04/27 19:00:56; author: ijacobs; state: Exp; lines: +3 -3
tweak in section 3.2, para 1: added "itself"
----------------------------
revision 1.443
date: 2004/04/27 18:59:33; author: ijacobs; state: Exp; lines: +12 -6
Per suggestion of stickler1
http://www.w3.org/2001/tag/2003/lc1209/issues.html#stickler1
Adopted suggested replacement sentence in 3.1:
Access may take many forms, including
retrieving a representation of the state of the resource (for instance,
by using HTTP GET or HEAD), adding or modifying a representation of
the state of the resource (for instance, by using HTTP POST or PUT,
which in some cases may change the actual state of the resource if
the submitted representations are interpreted as instructions to that
affect), and deleting some or all representations of the state of the
resource (for instance, by using HTTP DELETE, which in some cases may
result in the deletion of the resource itself)."
----------------------------
revision 1.442
date: 2004/04/27 18:57:46; author: ijacobs; state: Exp; lines: +25 -11
Per suggestion of stickler1
http://www.w3.org/2001/tag/2003/lc1209/issues.html#stickler1
Added example in 2.3 on URI ambiguity. Also moved some
content around to try to better explain what it means.
----------------------------
revision 1.441
date: 2004/04/23 19:45:48; author: ijacobs; state: Exp; lines: +4 -4
Also tried to make clearer that "URI ambiguity" means that
the URI is used to refer to more than one resource in a context
of Web protocols and formats.
----------------------------
revision 1.440
date: 2004/04/23 19:44:35; author: ijacobs; state: Exp; lines: +11 -11
per http://www.w3.org/2001/tag/2003/lc1209/issues.html#stickler1
- s/Web resource/resource globally to avoid confusion.
- In 2.3, changed last sentence to:
"URI ambiguity arises when a URI is used to identify two different
resources outside the context of Web protocols and formats."
----------------------------
revision 1.439
date: 2004/04/23 19:35:32; author: ijacobs; state: Exp; lines: +7 -4
per http://www.w3.org/2001/tag/2003/lc1209/issues.html#stickler1
Added example in 2.1:
"By following the "http" URI specification, agents are licensed to
conclude that "http://Weather.Example.Com/Oaxaca" and
"http://weather.example.com/Oaxaca" identify the same resource."
----------------------------
revision 1.438
date: 2004/04/23 16:33:45; author: ijacobs; state: Exp; lines: +82 -65
Editorial changes based on
http://www.w3.org/2001/tag/2003/lc1209/issues.html#goodwin1
In particular, reorganized 2.1 to read more clearly, and
made second half a new subsection.
----------------------------
revision 1.437
date: 2004/04/23 15:32:22; author: ijacobs; state: Exp; lines: +9 -5
Added sentence to GPN in 4.5.4 per
http://www.w3.org/2001/tag/2003/lc1209/issues.html#booth3
"When a namespace representation is provided by
the authority responsible for the namespace, that material
is authoritative."
Also changed "Resource owner" to "Authority responsible for
[an XML Namespace Name]"
----------------------------
revision 1.436
date: 2004/04/21 23:54:53; author: ijacobs; state: Exp; lines: +29 -21
http://www.w3.org/2001/tag/2003/lc1209/issues.html#booth2
Added forward link to section on representation management (3.6.3).
Also reworked the text to state more clearly:
URI owners get to serve authoritative metadata.
----------------------------
revision 1.435
date: 2004/04/21 23:24:17; author: ijacobs; state: Exp; lines: +4 -4
Issue http://www.w3.org/2001/tag/2003/lc1209/issues.html#ducharme1
Source
http://lists.w3.org/Archives/Public/public-webarch-comments/2003Dec/0019.html
Minor editorial fixes:
1.2.2 "Context has determined which term" should read "Context determines
which term" for agreement of tense with sentence that precedes this ones.
1.2.3 "error condition so that a an agent" "so that an agent"
----------------------------
revision 1.434
date: 2004/04/21 23:22:53; author: ijacobs; state: Exp; lines: +8 -4
Issue http://www.w3.org/2001/tag/2003/lc1209/issues.html#ducharme1
Source
http://lists.w3.org/Archives/Public/public-webarch-comments/2003Dec/0019.html
Improved glossary entry for "secondary resource"
----------------------------
revision 1.433
date: 2004/04/21 23:18:35; author: ijacobs; state: Exp; lines: +9 -7
Issue http://www.w3.org/2001/tag/2003/lc1209/issues.html#ducharme1
Source
http://lists.w3.org/Archives/Public/public-webarch-comments/2003Dec/0019.html
4.5.6, number 3: changed
"might reveal the attributes of type ID" to
"might reveal the attributes declared to be of type ID".
Made some other minor tweaks as well.
----------------------------
revision 1.432
date: 2004/04/21 23:15:42; author: ijacobs; state: Exp; lines: +9 -5
Issue http://www.w3.org/2001/tag/2003/lc1209/issues.html#ducharme1
Source
http://lists.w3.org/Archives/Public/public-webarch-comments/2003Dec/0019.html
3.4.1: Added examples to both bullets.
----------------------------
revision 1.431
date: 2004/04/21 23:01:45; author: ijacobs; state: Exp; lines: +13 -14
Issue http://www.w3.org/2001/tag/2003/lc1209/issues.html#ducharme1
Source
http://lists.w3.org/Archives/Public/public-webarch-comments/2003Dec/0019.html
Globally changed "orthogonal" to "independent"
----------------------------
revision 1.430
date: 2004/04/21 22:59:47; author: ijacobs; state: Exp; lines: +7 -5
Issue http://www.w3.org/2001/tag/2003/lc1209/issues.html#ducharme1
Source
http://lists.w3.org/Archives/Public/public-webarch-comments/2003Dec/0019.html
1.1.3:
s/<p>/p
also made the explanation a little more self-contained.
----------------------------
revision 1.429
date: 2004/04/21 22:57:02; author: ijacobs; state: Exp; lines: +3 -3
Issue http://www.w3.org/2001/tag/2003/lc1209/issues.html#ducharme1
Source
http://lists.w3.org/Archives/Public/public-webarch-comments/2003Dec/0019.html
1.1 s/at least//
----------------------------
revision 1.428
date: 2004/04/21 21:56:35; author: ijacobs; state: Exp; lines: +4 -3
added clarification of what the "authority component" part
of an http URI is.
Cf:
http://www.w3.org/2001/tag/2003/lc1209/issues.html#karr1
----------------------------
revision 1.427
date: 2004/04/21 21:49:44; author: ijacobs; state: Exp; lines: +3 -3
bug fix in media type of intro story
----------------------------
revision 1.426
date: 2004/04/21 20:09:10; author: ijacobs; state: Exp; lines: +4 -4
http://www.w3.org/2001/tag/2003/lc1209/issues.html#harold1
Comment: "The constraint and the title do not seem to match. Perhaps
the title is supposed to be "URI non-uniqueness" or perhaps the text
is supposed to be something like "Each URI identifies exactly one
resource". However, the title suggests to me that URIs are unique, and
the text suggests the opposite."
Solution: Changed title to "URI nonuniqueness"
----------------------------
revision 1.424
date: 2004/03/31 22:56:51; author: ijacobs; state: Exp; lines: +15 -14
Editorial changes based on
http://lists.w3.org/Archives/Public/public-webarch-comments/2003Dec/0006.html
- All typos fixed.
IMPLEMENTED:
* Sect 5 - Term Index. Maybe missing some terms? Would be useful to see
'Web' (and 'WWW', 'World Wide Web'), 'URI' (as a 'see Unifo...'
cross-reference), 'Data Format', 'Media Type' (maybe).
* Sect 2.4.1, 2nd para, 3rd bullet, 'One should not expect...' - suggest
change from 'will do anything useful with URIs of this scheme' to something
like 'will do anything with URIs of this scheme beyond comparison' or some
other wording.
* Sect 4.1. Suggest to interchange 1st and 2nd paras to reflect order in
section title.
DID NOT IMPLEMENT:
>* Sect 4 is entitled 'Data Formats', and Sect 1, 3rd bullet has 'Formats'.
>Would suggest that both should be changed to 'Representation' in keeping
>with the 3 bases articulated in the Abstract (identification, interaction,
>representation). This shift in gears from representation to data formats is
>potentially confusing. Maybe within the section one could talk of data
>formats (as a more concrete realization of the abstraction
>'representation'), but I think the section (and bullet) are better labeled
>at the more generic/abstract level.
We used to have that and then chose the current organization
instead.
>* Almost all the Story examples seem to make use of HTTP URIs. Any chance of
>sneaking in some other URI schemes just here and there just to reinforce
>that the fact that this is a democrarcy not a monarchy? Perhaps even just a
>mailto, or urn, or something more exotic?
We have examples of other schemes. No need to use exotic schemes
if not motivated by story.
>* Sect 6 - References. Still minded to have a division between normative and
>informative refs. Otherwise seems rather haphazard like the Web itself. Cf.
>the [IETFXML] entry: 'This IETF Internet Draft is available at .... If this
>document is no longer available, refer to...' And BTW, my understanding is
>that I-Ds should ony be referenced as a work in progress. Same with [IRI]
>entry below.
TAG did not feel the need to have normative refs.
>* Sect 2.4, 3rd para, 1st sentence, 'While the Web architecture...' - change
>'is costly' to 'can be costly'?
Not sure about this one.
>* Sect 2.4, 3rd para, 3rd sentence, 'Introducing a new URI scheme...' -
>change 'requires' to 'may require'?
Not sure about this one.
>(There is the problem here that unregistered scheme URIs may not be
>authoritatively compared. OTOH if we have a registered scheme URI and an
>unregistered scheme URI *using the same scheme* - can we authoritatively
>compare them? Anyway, the point I am trying to bring out in this comment is
>that URI identity/comparison is in and of itself a powerful utility, beyond
>dereference.)
>
>* Sect 2.4, last para, last sentence - 'When an agent does not handle a new
>URI scheme, it cannot retrieve a representation.' This seems prejudicial, as
>if the only intersting operations are retrieval. An agent can already make
>use of the identitiy afforded by a URI and comparison of URIs in
>applications such as merging of RDF graphs or of merging Topic Maps which
>identify resources by means of URIs.
Nonetheless, the statement is true.
>* Sect 3, last para ('Note') before Sect 3.1. I would strongly query the
>sentence 'Informally, a resource is "on the Web" when it has a URI and an
>agent can use the URI to retrieve a representation of it ...'. I would
>rather say that a resource is "on the Web" when it is referenced by means of
>a URI. That would seem to me to be a full and sufficient condition. A
>resource referenced by a URI participates within the Web information space
>and assertions can be made about that resource.
The TAG did not agree to that definition.
>* Sect 3.6.2, 1st para. Should clarify here that 'URI persistence' actualy
>refers to persistence of the referenced resource, not to the URI. (That
>point is made in the [Cool] reference entry but should be made here and not
>in the refrence section.)
Having reread the sentence, I don't believe that's necessary. It's
defined clearly.
>* Sect 4.5.5, 1st para, 2nd sentence. 'A qualified name is a pair consisting
>of a URI,..., and a local name...' Surely the qualified name itself consists
>of a 'prefix' which represents the URI (i.e. is a URI placeholder), and a
>local name?
I think that's a qname rather than a qualified name.
----------------------------
revision 1.423
date: 2004/03/31 21:21:55; author: ijacobs; state: Exp; lines: +15 -2
Per comments from Tony Hammond
http://lists.w3.org/Archives/Public/public-webarch-comments/2003Dec/0006.html
Added World Wide Web, WWW, Web, and URI to the term index.
Changes between 5 Dec 2003 Editor's Draft and the 9 Dec 2003 Last Call Working Draft.
Changes between 3 Dec 2003 Editor's Draft and the 5 Dec 2003 Editor's Draft (diff).
Changes between 28 Nov 2003 Editor's Draft and the 3 Dec 2003 Editor's Draft (diff).
functionalProperty per
TBL suggestion.Changes between 11 Nov 2003 Editor's Draft and the 28 Nov 2003 Editor's Draft (diff).
Most of these changes were the result of the TAG's ftf meeting in Japan (minutes). A fair number of editorial changes are not listed here, based on a previous IJ review, a TB review, TBL review, and SW review.
Changes between 27 Oct 2003 Editor's Draft and 11 Nov 2003 Editor's Draft (diff).
Changes between 1 Oct 2003 Working Draft and 27 Oct 2003 Editor's Draft
Unless otherwise indicated, the changes in this draft were the result of discussion at the TAG's Bristol ftf meeting.
Changes between 26 Sep 2003 Editor's Draft and 1 Oct 2003 Working Draft (diff).
Changes between 18 Sep 2003 Editor's Draft and 26 Sep 2003 Editor's Draft (diff).
Changes between 1 Aug 2003 Editor's Draft and 18 Sep 2003 Editor's Draft (diff).
Other changes:
Changes between 16 Jul 2003 Editor's Draft and 1 Aug 2003 Editor's Draft (diff).
Most of these changes were discussed at the TAG's 21-23 July face-to-face meeting in Vancouver. Note that sections 3 and 4 were swapped since the 16 July draft. The numbers of sections below are those of the 1 August draft.
Additional editorial changes:
Changes between 15 Jul 2003 Editor's Draft and 16 Jul 2003 Editor's Draft (diff).
Editorial changes:
Changes between 27 Jun 2003 Working Draft and 15 Jul 2003 Editor's Draft (diff).
There were no material changes between the 26 Jun 2003 Editor's Draft and the 27 Jun 2003 Working Draft.
Changes between 23 Jun 2003 Editor's Draft and 26 Jun 2003 Editor's Draft (diff)
The changes in this draft are editorial, based on Dan Connolly suggestions and Tim Bray suggestions. The primary changes are:
Changes between 16 Jun 2003 Editor's Draft and 23 Jun 2003 Editor's Draft (diff)
Changes between 26 Mar 2003 Working Draft and 16 Jun 2003 Editor's Draft
The primary changes in this draft are the result of the TAG walk-through of the document at its 2 June 2003 and 9 June 2003 teleconferences. They include:
Additional editorial changes based on:
Changes between 21 Mar 2003 Editor's Draft and 26 Mar 2003 Working Draft
Editorial changes per 24 Mar 2003 TAG teleconf.
Changes between 21 Feb 2003 Editor's Draft and 21 Mar 2003 Editor's Draft and
Changes between 6 Feb 2003 Editor's Draft and 21 Feb 2003 Editor's Draft.
Listed in order of MN's suggestions:
Changes between 6 Dec 2002 Editor's Draft and 6 Feb 2003 Editor's Draft.
Changes between 15 Nov 2002 Working Draft and 6 Dec 2002 Editor's Draft.
Changes between 12 Nov 2002 Editor's Draft and 15 Nov 2002 Working Draft.
Changes between 7 Nov draft and 12 Nov draft.
Editorial:
Changes between 7 Nov draft and 29 Oct draft.
Changes between 29 Oct draft and 30 Aug 2002 first public WD.
The principles in this document are based on experience. There has been some theoretical and modeling work in the area of Web Architecture, notably Roy Fielding's work on Representational State Transfer [REST].