activitystreams_traits/
actor.rs

1/*
2 * This file is part of ActivityStreams Traits.
3 *
4 * Copyright © 2018 Riley Trautman
5 *
6 * ActivityStreams Traits is free software: you can redistribute it and/or modify
7 * it under the terms of the GNU General Public License as published by
8 * the Free Software Foundation, either version 3 of the License, or
9 * (at your option) any later version.
10 *
11 * ActivityStreams Traits is distributed in the hope that it will be useful,
12 * but WITHOUT ANY WARRANTY; without even the implied warranty of
13 * MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
14 * GNU General Public License for more details.
15 *
16 * You should have received a copy of the GNU General Public License
17 * along with ActivityStreams Traits.  If not, see <http://www.gnu.org/licenses/>.
18 */
19
20use crate::object::Object;
21
22/// `Actor` types are `Object` types that are capable of performing activities.
23///
24/// This specification intentionally defines `Actors` in only the most generalized way, stopping
25/// short of defining semantically specific properties for each. All Actor objects are
26/// specializations of `Object` and inherit all of the core properties common to all Objects.
27/// External vocabularies can be used to express additional detail not covered by the Activity
28/// Vocabulary. VCard [[vcard-rdf](https://www.w3.org/TR/vcard-rdf/) SHOULD be used to provide
29/// additional metadata for `Person`, `Group`, and `Organization` instances.
30///
31/// While implementations are free to introduce new types of Actors beyond those defined by the
32/// Activity Vocabulary, interoperability issues can arise when applications rely too much on
33/// extension types that are not recognized by other implementations. Care should be taken to not
34/// unduly overlap with or duplicate the existing `Actor` types.
35///
36/// When an implementation uses an extension type that overlaps with a core vocabulary type, the
37/// implementation MUST also specify the core vocabulary type. For instance, some vocabularies
38/// (e.g. VCard) define their own types for describing people. An implementation that wishes, for
39/// example, to use a `vcard:Individual` as an `Actor` MUST also identify that `Actor` as a
40/// `Person`.
41pub trait Actor: Object {}
activitystreams_traits/actor.rs

activitystreams_traits/
actor.rs
