[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: [OASIS Issue Tracker] (OSLCCORE-179) Behaviour if neither oslc.where nor oslc.searchTerms are specified
David Honey created OSLCCORE-179: ------------------------------------ Summary: Behaviour if neither oslc.where nor oslc.searchTerms are specified Key: OSLCCORE-179 URL: https://issues.oasis-open.org/browse/OSLCCORE-179 Project: OASIS OSLC Lifecycle Integration Core (OSLC Core) TC Issue Type: Improvement Components: Query Reporter: David Honey Assignee: James Amsden Currently, the OSLC Query 3.0 draft specification does not define the behaviour of OSLC Query when neither oslc.where nor oslc.searchTerms is specified. We should provide more guidance on this. Some implementations might want to return all artifacts of the RDF type associated with the query capability. However, when the number of artifacts is very large, and especially when a server does not support paging, such a request could overwhelm a server, or the resultant large response might overwhelm the requesting client. -- This message was sent by Atlassian JIRA (v7.7.2#77003)
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]