Initial write-up of Apache Streams #356
Conversation
This document reflects the proposed feature set of AS 2.0 which is currently implemented in Apache Streams using AS 1.0 Apache Streams (incubating) supports the efforts of the Social Working Group to publish AS 2.0 as a formal specification. As more providers are added to Apache Streams and the variety of documents they produce increases, the project intends to align and remain aligned with the AS 2.0 vocubulary.
|
So, the main point of our implementation reports is to verify if and how implementations are using the features of this specification. I think that an implementation report for AS1 is useful as input but probably doesn't fit with the implementation reports for AS2. I'd appreciate some feedback on this. |
|
@evanp et all, this PR summarizes what the Apache Streams implementation report would look like if the community ported our existing functionality to support AS 2.0. There are plenty of other object and verb types that match up with endpoints from existing providers as yet un-utilized, or easily added to providers matching other popular SNS APIs. If we need to meet the criteria for basic AS 2.0 compatibility before merging, let's start a conversation about how we'll verify that has been achieved and I'll maintain the PR branch until we get there. It seems achievable to have AS 2.0 support in a release by the end of Q4 if we set after that soon. |
This document reflects the proposed feature set of AS 2.0 which is currently implemented in Apache Streams using AS 1.0
Apache Streams (incubating) supports the efforts of the Social Working Group to publish AS 2.0 as a formal specification. As more providers are added to Apache Streams and the variety of documents they produce increases, the project intends to align and remain aligned with the AS 2.0 vocubulary.