A small tool to view real-world ActivityPub objects as JSON! Enter a URL
or username from Mastodon or a similar service below, and we'll send a
request with
the right
Accept
header
to the server to view the underlying object.
{
"@context": [
"https://www.w3.org/ns/activitystreams",
{
"ostatus": "http://ostatus.org#",
"atomUri": "ostatus:atomUri",
"inReplyToAtomUri": "ostatus:inReplyToAtomUri",
"conversation": "ostatus:conversation",
"sensitive": "as:sensitive",
"toot": "http://joinmastodon.org/ns#",
"votersCount": "toot:votersCount",
"Hashtag": "as:Hashtag"
}
],
"id": "https://discuss.systems/users/ocratato/statuses/113002817194682026",
"type": "Note",
"summary": null,
"inReplyTo": null,
"published": "2024-08-22T00:22:31Z",
"url": "https://discuss.systems/@ocratato/113002817194682026",
"attributedTo": "https://discuss.systems/users/ocratato",
"to": [
"https://www.w3.org/ns/activitystreams#Public"
],
"cc": [
"https://discuss.systems/users/ocratato/followers"
],
"sensitive": false,
"atomUri": "https://discuss.systems/users/ocratato/statuses/113002817194682026",
"inReplyToAtomUri": null,
"conversation": "tag:discuss.systems,2024-08-22:objectId=23927070:objectType=Conversation",
"content": "<p><a href=\"https://discuss.systems/tags/SASSY\" class=\"mention hashtag\" rel=\"tag\">#<span>SASSY</span></a></p><p>Natural Language Generation has gone through three major phases. Initially templates were used. This evolved into Rhetorical Structure Theory which tried to use planning to deduce the structure of the text. More recently Large Language Models have got the attention of the NLG community.</p><p>Templates do not have the flexibility to handle arbitrary software designs. Any novel attribute of a design would likely be overlooked by the templates.</p><p>LLMs appear to be non-deterministic. This is a problem for design documents. They need to be able to be regenerated at any time and the only changes should be a direct result of changes in the data.</p><p>A lot of work was done on RST in the 80's and 90's. The fact that there is not any readily available RST based software available today is a good clue that it was not a successful endevour. </p><p>I found two major issues with RST: Firstly the planning approach could leave important information unreported. This is a show stopper for SASSY. Secondly, in order to get good results it took months long collaboration between linguists and subject matter experts. This would also be an obsticle for SASSY that aims to be an easy to use tool for helping with software design.</p><p>Next I will discuss my plan to adapt RST for use in SASSY.</p><p><a href=\"https://discuss.systems/tags/SoftwareArchitecture\" class=\"mention hashtag\" rel=\"tag\">#<span>SoftwareArchitecture</span></a><br /><a href=\"https://discuss.systems/tags/NLG\" class=\"mention hashtag\" rel=\"tag\">#<span>NLG</span></a> <a href=\"https://discuss.systems/tags/NaturalLanguageGeneration\" class=\"mention hashtag\" rel=\"tag\">#<span>NaturalLanguageGeneration</span></a></p>",
"contentMap": {
"en": "<p><a href=\"https://discuss.systems/tags/SASSY\" class=\"mention hashtag\" rel=\"tag\">#<span>SASSY</span></a></p><p>Natural Language Generation has gone through three major phases. Initially templates were used. This evolved into Rhetorical Structure Theory which tried to use planning to deduce the structure of the text. More recently Large Language Models have got the attention of the NLG community.</p><p>Templates do not have the flexibility to handle arbitrary software designs. Any novel attribute of a design would likely be overlooked by the templates.</p><p>LLMs appear to be non-deterministic. This is a problem for design documents. They need to be able to be regenerated at any time and the only changes should be a direct result of changes in the data.</p><p>A lot of work was done on RST in the 80's and 90's. The fact that there is not any readily available RST based software available today is a good clue that it was not a successful endevour. </p><p>I found two major issues with RST: Firstly the planning approach could leave important information unreported. This is a show stopper for SASSY. Secondly, in order to get good results it took months long collaboration between linguists and subject matter experts. This would also be an obsticle for SASSY that aims to be an easy to use tool for helping with software design.</p><p>Next I will discuss my plan to adapt RST for use in SASSY.</p><p><a href=\"https://discuss.systems/tags/SoftwareArchitecture\" class=\"mention hashtag\" rel=\"tag\">#<span>SoftwareArchitecture</span></a><br /><a href=\"https://discuss.systems/tags/NLG\" class=\"mention hashtag\" rel=\"tag\">#<span>NLG</span></a> <a href=\"https://discuss.systems/tags/NaturalLanguageGeneration\" class=\"mention hashtag\" rel=\"tag\">#<span>NaturalLanguageGeneration</span></a></p>"
},
"attachment": [],
"tag": [
{
"type": "Hashtag",
"href": "https://discuss.systems/tags/sassy",
"name": "#sassy"
},
{
"type": "Hashtag",
"href": "https://discuss.systems/tags/softwarearchitecture",
"name": "#softwarearchitecture"
},
{
"type": "Hashtag",
"href": "https://discuss.systems/tags/nlg",
"name": "#nlg"
},
{
"type": "Hashtag",
"href": "https://discuss.systems/tags/naturallanguagegeneration",
"name": "#naturallanguagegeneration"
}
],
"replies": {
"id": "https://discuss.systems/users/ocratato/statuses/113002817194682026/replies",
"type": "Collection",
"first": {
"type": "CollectionPage",
"next": "https://discuss.systems/users/ocratato/statuses/113002817194682026/replies?min_id=113009084793506870&page=true",
"partOf": "https://discuss.systems/users/ocratato/statuses/113002817194682026/replies",
"items": [
"https://discuss.systems/users/ocratato/statuses/113009084793506870"
]
}
},
"likes": {
"id": "https://discuss.systems/users/ocratato/statuses/113002817194682026/likes",
"type": "Collection",
"totalItems": 0
},
"shares": {
"id": "https://discuss.systems/users/ocratato/statuses/113002817194682026/shares",
"type": "Collection",
"totalItems": 0
}
}