Skip to content

How micro should a Personator be? #3

@bhaugen

Description

@bhaugen

This is a much more general issue, not really about this app, but related to https://github.com/valueflows/valueflows/issues/86

I'm putting it here because it came to mind when I was thinking of a Personator as an impersonator. The purpose of this app is well-stated as "to enable someone...to create, view, edit, or delete their personal linked open data profile".

As an impersonator, a personator would be your agent, able to post your intents, respond to other peoples' intents, engage in conversations for action, give and take goods and services, etc.

Is that too much for one app? Do people think that the proper architecture for an Open Apps Ecosystem is more like https://en.wikipedia.org/wiki/Unix_philosophy where tools that do one and only thing can be piped together like the late lamented Yahoo Pipes?

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions