You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
A Public Working Draft is published on the W3C's Technical Reports page [TR] for review, and for simple historical reference. For all Public Working Drafts a Working Group
SHOULD document outstanding issues, and parts of the document on which the Working Group does not have consensus, and
MAY request publication of a Working Draft even if its content is considered unstable and does not meet all Working Group requirements.
I propose adding more significant issues inline to the spec, currently:
ISSUE: as:Link uses same @id as resource it targets and most of its properties (except as:rel) describe the representation of a resource it targets not the link itself
ISSUE: using blank node identifiers (eg. _:post) for values of as:verb can cause problems with comparing it across multiple JSON-LD documents even when they serialize single activity stream. Persisting activities with such blank node identifiers in triple stores will also result in them changing to different, not predictable, blank node identifiers. Also various processing algorithms will relabel blank nodes.
The text was updated successfully, but these errors were encountered:
With Editors Hat on, I would rather address this issue by issue. If the WG feels that a particular issue is controversial enough to call out specifically in the draft, I will include an appropriate ed note. Otherwise, the draft already has a link back to the issues list for reference
http://www.w3.org/2014/Process-20140801/#working-draft states:
I propose adding more significant issues inline to the spec, currently:
The text was updated successfully, but these errors were encountered: