--- a/ldp-bp/ldp-bp.html Sun Sep 15 21:00:31 2013 -0400
+++ b/ldp-bp/ldp-bp.html Mon Sep 16 11:10:19 2013 -0500
@@ -67,7 +67,7 @@
//authors: [
// { name: "Your Name", url: "http://example.org/",
- // company: "Your Company", companyURL: "http://example.com/" },
+ // company: "Your Company", companyURL: "http://example.org/" },
//],
// name of the WG
@@ -407,11 +407,11 @@
<p>One example of such a model can be found in the case of the <code>oslc_cm:attachment</code> container from the vocabularies defined by the <a href="http://open-services.net/">Open Service for Lifecycle Management (OSLC)</a> community. The OSLC defines specifications and vocabularies that are well-aligned to the LDP. A resource in an OSLC compliant change management system such as an issue or bug tracker may have attachments represented by the <code>oslc_cm:attachment</code>
container. The URI for such a container might be represented as follows:</p>
- <p><code>http://example.com/bugs/2314/attachments/</code></p>
+ <p><code>http://example.org/bugs/2314/attachments/</code></p>
<p>From this URI, you can easily discern the URI of the parent resource, which holds the attachments. You can also discern the base container for other sibling resources by moving up the hierarchy, which is implied by the URI. You might also go down the hierarchy to fetch meta-data or binary content using a URI such as the following:</p>
- <p><code>http://example.com/bugs/2314/attachments/1</code></p>
+ <p><code>http://example.org/bugs/2314/attachments/1</code></p>
<p>As you can see, in addition to making the use of relative URIs possible, hierarchical URIs make interacting with resources easier because they represent the actual structure of the underlying graph.</p>
@@ -463,7 +463,7 @@
<p>The fragment identifier introduced by a hash mark <b><code>#</code></b> is the optional last part of a URI for an object, which is typically used to identify a subordinate or related object.</p>
<p>
- Take the URI, <code>http://www.example.com/products#item10245</code>, for example. The base URI is the part preceding the hash mark, <code>http://www.example.com/products</code>, and the fragment identifier is the part that follows,
+ Take the URI, <code>http://www.example.org/products#item10245</code>, for example. The base URI is the part preceding the hash mark, <code>http://www.example.org/products</code>, and the fragment identifier is the part that follows,
<code>item10245</code>.
</p>