[OASIS Issue Tracker] Updated: (ICOM-7) Investigate multiplecontainment relations

[OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org>]

     [ http://tools.oasis-open.org/issues/browse/ICOM-7?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Eric Chan updated ICOM-7:
-------------------------

    Resolution: 
ICOM RDF representation did not use RDF collections, so avoided the issue of representing closed or open collections. ICOM RDF uses properties and cardinality "multiple" to represent sets.

ICOM specification introduced an optional property definition in Item class to represent multi-containment relation:

Class name:     icom:Item
Property name: icom:container
Description: 	Zero, one, or more containers of an item.
Required: 	False
Inherited: 	False
Property Type: 	icom:Container
Cardinality: 	Multi
Updatability: 	Read Write


  was:ICOM RDF representation used RDF collections, so avoided the issue of representing closed or open collections. ICOM RDF uses properties and cardinality "multiple" to represent sets.


> Investigate multiple containment relations
> ------------------------------------------
>
>                 Key: ICOM-7
>                 URL: http://tools.oasis-open.org/issues/browse/ICOM-7
>             Project: OASIS Integrated Collaboration Object Model for Interoperable Collaboration  Services (ICOM) TC 
>          Issue Type: Task
>            Reporter: Eric Chan
>
> Investigate multiple containment of an entity by one or more community, bom:workspace/sioc:space, and bom:folder/sioc:container. What are the implications of multi-containment on access control and policy enforcement? Is the containment a graph or directed acyclic graph?

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://tools.oasis-open.org/issues/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira