- From: John Arwe <johnarwe@us.ibm.com>
- Date: Mon, 23 Sep 2013 11:47:15 -0400
- To: "public-ldp-wg@w3.org" <public-ldp-wg@w3.org>
- Message-ID: <OF21C9ABD9.5F6B701A-ON85257BEF.0056AC13-85257BEF.0056B9F2@us.ibm.com>
Since we just struck inlining, this is no longer an issue. Best Regards, John Voice US 845-435-9470 BluePages Tivoli OSLC Lead - Show me the Scenario From: Nandana Mihindukulasooriya <nmihindu@fi.upm.es> To: "public-ldp-wg@w3.org" <public-ldp-wg@w3.org>, Cc: John Arwe/Poughkeepsie/IBM@IBMUS, Steve Speicher <sspeiche@gmail.com> Date: 09/10/2013 04:17 PM Subject: Resource Inlining - clarification Hi, A small clarification on resource inlining in the case of LDPR has inlining but does not require paging. The question is specially on the following requirement, [[ 4.11.3.1 LDPR servers that support resource inlining must include a ldp:Page resource in the representation describing the set of inlined resources, whether or not the representation contains subsequent pages. ]] If I have a <bug3> resource that inlines <bug4> resource, does it mean that it has to act as a resource with one page or could we just define the <bug3> resource to be a page (i.e. without the redirection) with information about inlined resources ? Concretely, is [A] correct or does it have to be like [B] in the example http://ctrlv.it/id/MzU3OTQ4 ? Best Regards, Nandana
Received on Monday, 23 September 2013 16:05:41 UTC