c58075bf82
Try to make text around filtering like/followers/following clearer
...
Based on feedback from #139 .
2016-10-13 16:17:26 -05:00
8779c0a0aa
Update the special Public collection to point to use a fragment identifier
2016-10-13 15:54:54 -05:00
476192d905
Switch over to activitystreams namespace
...
Closes #131 .
2016-10-13 15:02:53 -05:00
52bfdda2d8
Clarify that likes/following/followers collections MAY be filtered
...
See #139 .
2016-10-13 14:59:01 -05:00
0eb0d24be3
Put "likes" property in actor profile example.
2016-10-13 14:36:15 -05:00
e2bd6cecd8
Oops, we forgot to list "likes" as a property
2016-10-13 14:35:48 -05:00
86cc5acffa
Change property identifiers to "*-property" and link to definitions
2016-10-13 14:35:37 -05:00
9e66383144
Oops, removing duplicate identifiers for "inbox" and "outbox"
2016-10-13 14:14:29 -05:00
7ffd44fa53
Mark preferredUsername at-risk. Also add ids to other props.
...
Closes #145 .
2016-10-13 13:49:48 -05:00
702ef315b2
Clarify that followers/following are links/uris, not embedded
...
Closes #144
2016-10-13 12:07:37 -05:00
3675b5e201
Merge pull request #138 from Lexas/patch-1
...
fix typo on section 2.2
2016-10-13 12:04:26 -05:00
cc25318eb1
Change "ActivityStreams Vocabulary" to "Activity Vocabulary"
...
Closes #135 .
2016-10-13 11:49:06 -05:00
83d8f229e0
More clearly reference ActivityStreams targeting in the overview
...
This is in response to feedback in #141
2016-10-13 10:19:49 -05:00
78735bc157
Fix word ordering in "client to server interaction side effects"
...
Thanks for a catch in #136
2016-10-13 10:09:24 -05:00
5224ac6979
@r12a's spouse gave some better text, use it!
...
For issue #128
2016-10-13 07:52:40 -05:00
8396048897
Add en-GB to examples 6 and 8 per @aphillips' suggestions
...
See #128
2016-10-12 21:41:31 -05:00
c14715f2a5
Fix up actor-text-direction section based on @aphillips' feedback.
...
Closes #126
2016-10-12 19:03:19 -05:00
69b04aa317
A note on text direction and the actor profile.
2016-10-12 18:27:56 -05:00
745b23ccdf
Remove explicit pointer to bidirectional text section.
...
I think the linked-to section in the ActvityStreams document covers
this already.
2016-10-12 18:20:58 -05:00
c28c7f3c68
Clarify language direction in Actor for #126
2016-10-12 18:19:10 -05:00
4a080f4753
Note that ActivityPub shares the same URI / IRI conventions as in ActivityStreams.
2016-10-12 15:11:08 -05:00
fd6483eddf
Switch to using a Japanese example for Person example, courtesy @r12a
...
This is in relation to issue #128 .
2016-10-12 14:24:49 -05:00
538a18c36b
Add @language to last two properties where it's relevant.
...
This should satisfy #128 .
2016-10-12 12:54:42 -05:00
8a807640d9
Link to i18n LanguageDetection wiki page
2016-10-12 12:44:34 -05:00
ebe39ef0b2
Add @language property to two more examples
...
This references issue #128 .
2016-10-12 11:03:10 -05:00
1356994af4
Added "@language" to three more examples
...
This is in reference to #128 .
2016-10-12 10:46:01 -05:00
2f4c73929b
Update index.html
2016-10-06 13:01:25 -06:00
6536d26475
clarify or as and/or in public/followers default
2016-10-05 19:39:05 -05:00
afcf935f29
Fix broken anchor tag links
2016-10-04 16:31:45 -05:00
77b969acf5
Update publishDate
2016-10-04 16:26:16 -05:00
cab1ab01a8
Update changelog.
2016-10-04 11:25:55 -05:00
ca0f91973f
Remove commented out section
2016-10-04 11:20:06 -05:00
2acda78e9d
Leave a note about which properties are acceptable to use for OrderedCollection
...
Really, it needs to not change, and somehow fit "reverse chronological" order!
2016-10-04 11:07:53 -05:00
9eda0afd9f
Add @language to example 1
...
Closes #128
2016-10-04 10:56:36 -05:00
2a217fab65
Removing superfluous words from at risk section
2016-10-04 10:30:07 -05:00
206377d9b3
should allocate -> SHOULD allocate
2016-10-04 10:21:28 -05:00
ba1a764cec
Remove issue about normalizing entries without URI scheme
2016-10-04 10:19:43 -05:00
d4af6a6406
Remove issue to mention json-ld @context, which has been done.
2016-10-04 10:19:18 -05:00
d4e77f25f7
Adjust text around what verification methods are possible.
...
Previously this specified a "general mechanism" for checking the
object as originally received at its origin. We now say that while no
mechanism is specified, we've laid out some possible directions,
and while the "general mechanism" is still suggested as a fallback,
stronger verification methods are encouraged.
2016-10-04 09:49:44 -05:00
ce79e8423d
Move emphasis from "having" to "done"
2016-10-04 09:38:29 -05:00
8ed885cb38
Switch note to about scheme to be part of ID normalization rules
2016-10-04 06:40:51 -05:00
bb1649afad
Note that if no URI scheme in a client interface is provided, "https" is ok.
2016-10-04 06:37:49 -05:00
7306f457d4
Removed duplicate "GET" method section.
...
It's the only method on objects described now, and is described above
anyway.
2016-10-03 16:47:23 -05:00
206612c27f
Add "source" field, and mark as "at risk"
...
Closes #107 .
2016-10-03 16:46:06 -05:00
2644b0baf2
Add "At Risk features" section; add "Binary Data" mechanism/endpoint to it
...
Closes #109 .
2016-10-03 11:46:39 -05:00
15f90ee98c
Editor's Draft is now at w3c.github.io, not w3c-social.*
2016-09-29 14:59:04 -05:00
c8afe18da8
Try to get authentication/authorization right
2016-09-28 07:54:36 -05:00
c4480a5f09
Fix capitalization of Micropub
...
It's not microPub or MicroPub or micro-pub....
2016-09-28 06:48:58 -05:00
617220b899
specify the dae of self-review security/privacy questionaire
2016-09-27 12:05:30 -05:00
d0b9566be5
Add security and privacy review section.
2016-09-27 12:04:45 -05:00
