HyperCat RFCs - results of review meeting

[Pilgrim Beart]

We had a good call today to discuss the two RFCs:

1) Adding support for GET to multi-search (approved)

2) Adding paging (rejected).

Attendees

• Greg of Asset Mapping
  
• Dritan Kaleshi of Digital Catapult
  
• Andy Stanford-Clark of IBM
  
• Toby Jaffey of 1248
  
• Sam Mulube of Thingful
  
• (John Davies of BT sent his apologies)

Multi-search

We agreed that it would become mandatory for HC servers to support the GET method as well as the existing POST method. GET is preferred for RESTful compliance, but POST may be necessary if search definition becomes large.

Paging

Reviewers agreed that the proposed paging RFC by Sam Mulube is a well-written, however it does not consider the case where paging is requested by a client (rather than decided by a server). We therefore decided to keep this as an RFC for now, and add an entry to the Wiki to point people towards that: http://wiki.1248.io/doku.php?id=start&#does_hypercat_support_paging

Given the minor nature of the change (i.e. just multi-search change) then I propose we just move HyperCat to a draft 2.01 specification, which I will keep in sync with the ongoing PAS 212 work.

Regards,

-P

---

Sign up to learn more about 1248 Device Manager at http://1248.io  @1248_io  +44 7961 125282

Deploying connected devices? Take our survey: goo.gl/kuClzQ