search

HyperAgents / hmas

An ontology to describe Hypermedia Multi-Agent Systems, interactions, and organizations.
https://purl.org/hmas/
1 stars 0 forks source link

hmas:Workspace vs ldp:Container #24

Closed FabienGandon closed 2 years ago

FabienGandon commented 2 years ago

We could want to position the two classes hmas:Workspace and ldp:Container w.r.t. each other.

LDP has the ldp:Container and the ldp:contains that links a container with resources in the container: https://www.w3.org/ns/ldp#

Questions could be:

DrLeturc commented 2 years ago

I do not see any counter argument to not see hmas:Workspace as a ldp:Container.

andreiciortea commented 2 years ago

Very good point to address, @FabienGandon.

The definition for ldp:Container:

A Linked Data Platform RDF Source (LDP-RS) that also conforms to additional patterns and conventions for managing membership. Readers should refer to the specification defining this ontology for the list of behaviors associated with it.

This references the W3C Recommendation, where an LDP Container is defined as:

A LDP-RS representing a collection of linked documents (RDF Document [rdf11-concepts] or information resources [WEBARCH]) that responds to client requests for creation, modification, and/or enumeration of its linked members and documents, and that conforms to the simple lifecycle patterns and conventions in section 5. Linked Data Platform Containers.

The tricky part is the last part: "that conforms to the simple lifecycle patterns and conventions in section 5. Linked Data Platform Containers". The LDP defines an HTTP-based protocol for reading and writing Linked Data. It does so by imposing constraints on HTTP requests & responses and on the representation of resources (incl. here also the membership triples). If we say that all hmas:Workspaces are ldp:Containers, then all hmas:Platforms that host workspaces need to implement the LDP specs.

I think we should align Yggdrasil with the LDP if possible, but I would not constrain all Hypermedia MAS platforms to implement the LDP specs. We could have a resource that is both an hmas:Workspace and an ldp:Container.

@FabienGandon @DrLeturc do you agree?

oboissier commented 2 years ago

I agree with andrei. We shouldn't impose to impose that any hmas:Workspace is a ldp:Container.

FabienGandon commented 2 years ago

Agreed we can just make a note / comment that in the context of HMAS an option is to use an ldp:Container as a hmas:Workspace. This can be done by multi-typing the container or by multiple inheritance on a Class ex:Workcontainer