streams-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Joey Frazee <joey.fra...@icloud.com.INVALID>
Subject Re: Streams Roadmap and Alignment with Any23
Date Fri, 05 Oct 2018 20:38:08 GMT
The final Activity Streams 2.0 spec is here: https://www.w3.org/TR/activitystreams-core/ <https://www.w3.org/TR/activitystreams-core/>.

Specific processors, type converters, readers and writers live under streams-contrib: https://github.com/apache/streams/tree/master/streams-contrib
<https://github.com/apache/streams/tree/master/streams-contrib>.

The Java interfaces are in streams-core: https://github.com/apache/streams/tree/master/streams-core
<https://github.com/apache/streams/tree/master/streams-core>.

In general Activity Streams classes and the classes for different sources are generated from
jsonschema. For Activity Streams it’s in streams-schemas: https://github.com/apache/streams/tree/master/streams-schemas
<https://github.com/apache/streams/tree/master/streams-schemas>.


> On Oct 4, 2018, at 10:55 AM, lewis john mcgibbney <lewismc@apache.org> wrote:
> 
> Hi Joey,
> Correct Any23 does support JSON-LD as one of a number of common data
> formats to read and write data from and to resources.
> From the steams Website, it is not obvious to me where reader and writer
> interfaces are. Can you please point them out to me?
> Can you also point me to Activity Streams 2.0 documentation which
> highlights the data format(s)?
> Thank you
> Lewis
> 
> On Thu, Oct 4, 2018 at 8:28 AM <dev-digest-help@streams.apache.org> wrote:
> 
>> 
>> From: Joey Frazee <joey.frazee@icloud.com.invalid>
>> To: dev@streams.apache.org
>> Cc:
>> Bcc:
>> Date: Tue, 02 Oct 2018 16:39:50 -0500
>> Subject: Re: Streams Roadmap and Alignment with Any23
>> Lewis, there definitely seems to be some overlap conceptually. What were
>> you thinking? Any23 appears to support JSON-LD and I think we’re lacking
>> true support for it which we need for ActivityStreams 2.0.
>> 
>> I think it makes a ton of sense to look at where the overlaps and
>> complements are.
>> 
>> 


Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message