W3C home > Mailing lists > Public > public-socialweb@w3.org > January 2015

additions from Boeing

From: Bassetti, Ann <ann.bassetti@boeing.com>
Date: Thu, 29 Jan 2015 06:33:58 +0000
To: "public-socialweb@w3.org" <public-socialweb@w3.org>, "public-social-interest@w3.org" <public-social-interest@w3.org>
Message-ID: <96210A64A8AC40458F5180192EB9257431E4F604@XCH-PHX-101.sw.nos.boeing.com>
Adam Boyet and I <finally!> met last night to document our internal social networking tool, "inSite".  Because inSite was created entirely within Boeing, based on attributes of assorted popular public tools and specific to Boeing requirements, it has a wide variety of functions.

We'd like your collective guidance on the most useful way in which to document our inputs.

Our approach for our own discussion was to annotate a printed copy (old fashioned paper!) of the Social API requirements list (https://www.w3.org/wiki/Socialwg/Social_API/Requirements).   I typed up some examples of our additions in the comparison table below. (I'm also attaching a PDF, since I'm not sure how this table will render once it goes through other servers and systems.)

We're not even sure if the API Requirements page is the best place to put our additional information.  But it seemed like a simple place to start.

Please advise.  I'd be happy to chat, if anyone wants to do that.

Thanks in advance for your guidance!  -- Ann (Bassetti), with Adam Boyet

Social API Requirements

Boeing potential additions

Content

Content:  we have all of what's listed on left, plus the following. Would these be "other content types" or new functionality?


*         Create content




o    Image




o    Text




o    Video




o    Audio




o    Enterprise documents




o    Other content types




*         Read content created by one user




*         Modify content

<users only have 1 hour in which to modify>


*         Delete content

<users cannot delete content>

...






*         Add tag(s) (metadata)




o    when posting




o    to existing content




*         Put security restrictions (3 levels) on content when posting




*         Attach a document or video to content




o    Update attachment to new version (sometime later)




*         Ask a question




*         Post status update (e.g., "tweet")

...


...







Received on Thursday, 29 January 2015 06:34:57 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 17:26:14 UTC