Add Terminology section. #8
Conversation
index.html
Outdated
| </section> | ||
| <section class="informative"> | ||
| <h2>Introduction</h2> | ||
| <p> | ||
| Data portability is the ability of a user to move their data on one | ||
| Data portability is the ability of a user to move their data from one | ||
| system to another system. This includes moving between ActivityPub |
There was a problem hiding this comment.
If you're intending to define the terms "instance" and "server", do you want to leave this "system" terminology here or update it? it seems fine to me but I thought I'd mention it.
There was a problem hiding this comment.
would "from one instance to another instance, even if they are instances of different servers" be too confusing for the first sentence of an introduction? 🙃
There was a problem hiding this comment.
If you're intending to define the terms "instance" and "server", do you want to leave this "system" terminology here or update it? it seems fine to me but I thought I'd mention it.
Yeah, good catch. I wasn't sure how strongly we felt about 'system' as a term. Maybe we can come back to it
|
|
||
| <dl class="termlist"> | ||
| <dt><dfn data-lt="instance|instances">instance</dfn></dt> | ||
| <dd>An informal name for an ActivityPub <a>server</a>, specifically, |
There was a problem hiding this comment.
| <dd>An informal name for an ActivityPub <a>server</a>, specifically, | |
| <dd>An informal name for a deployed ActivityPub <a>service</a>, i.e., |
There was a problem hiding this comment.
@bumblefudge I like the 'deployed' part. It shouldn't be service though, unless we define that term in Terminology.
| <dt><dfn data-lt="instance|instances">instance</dfn></dt> | ||
| <dd>An informal name for an ActivityPub <a>server</a>, specifically, | ||
| a particular instance of a given ActivityPub server implementation. | ||
| In current implementations, instances are typically bound to a given |
There was a problem hiding this comment.
what does "bound to" mean here, effectively? that a domain controlled by the controllers of the instance is used as the domain elemtn of all the URLs that serve as ids and other URIs? something more esoteric about reputation and federation/allowlisting? both?
There was a problem hiding this comment.
that a domain controlled by the controllers of the instance is used as the domain elemtn of all the URLs that serve as ids and other URIs?
Yes, that! AND allow-listing. We can define the binding later on.
| </dd> | ||
| <dt><dfn data-lt="server|servers">server</dfn></dt> | ||
| <dd> | ||
| An implementation of an <strong>ActivityPub conformant Server</strong>, |
There was a problem hiding this comment.
| An implementation of an <strong>ActivityPub conformant Server</strong>, | |
| A piece of software that, when deployed, can function as <strong>ActivityPub-conformant Server</strong>, |
There was a problem hiding this comment.
I'm not sure 'piece of software' sounds quite right..
dmitrizagidulin
force-pushed
the
terminology
branch
from
7308962
to
3f08f8f
Compare
Add a Terminology section, seed it with initial definitions of
serverandinstance.