[oslc-core] Fw: Issue with the Use of dcterms:title and dcterms:description with oslc:ResponseInfo

[Arthur Ryman]

Steve,

206 is used for partial GET requests. Does the Core spec discuss those? 

I don't think we're creating an HTML solution, just specifying how to use 
existing mechanisms. Paging is very common in HTML, especially for large 
documents.

Regards, 
___________________________________________________________________________ 

Arthur Ryman, PhD, DE

Chief Architect, Project and Portfolio Management
IBM Software, Rational
Markham, ON, Canada | Office: 905-413-3077, Cell: 416-939-5063





From:
Steve K Speicher/Raleigh/IBM at IBMUS
To:
oslc-core at open-services.net
Cc:
Arthur Ryman <ryman at ca.ibm.com>, Martin Nally/Raleigh/IBM at IBMUS
Date:
12/07/2010 09:15 AM
Subject:
Re: [oslc-core] Fw: Issue with the Use of dcterms:title and 
dcterms:description with oslc:ResponseInfo



> From: Martin Nally/Raleigh/IBM at IBMUS
> To: Arthur Ryman <ryman at ca.ibm.com>
> Cc: oslc-core at open-services.net, oslc-core-bounces at open-services.net
> Date: 12/06/2010 06:51 PM
> Subject: Re: [oslc-core] Fw: Issue with the Use of dcterms:title and 
> dcterms:description with oslc:ResponseInfo
> Sent by: oslc-core-bounces at open-services.net

<snip> 
> >> Each page would be a valid HTML document.

In coming into this discussion late, I'm not sure I understand the need 
around creating a pagination solution for HTML content.  Also, it is very 
unlikely case that applications produce valid HTML, maybe there are a few.

I don't see HTML being a true "representation" format for resource formats 

that could become very large and require pagination.  If so, would this 
not use an already well-known approach with HTTP - 206 partial content?

<snip>

> Maybe an example would help

Agree

Thanks,
Steve Speicher | IBM Rational Software | (919) 254-0645