OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

cmis message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


Subject: [OASIS Issue Tracker] (CMIS-759) discussion of social features


    [ https://issues.oasis-open.org/browse/CMIS-759?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=41746#comment-41746 ] 

Eric Chan commented on CMIS-759:
--------------------------------


Here are a few comments to the draft https://www.oasis-open.org/apps/org/workgroup/cmis/download.php/52932.

1.	The draft provided an example: "For each comment, the document is the root parent. However commenting on a comment creates a dependent object for which the original comment is the immediate parent." Another possible use case: if the "root parent" is a folder, the chains of comments through the "immediate parent" can represent conversation threads.

2.	Tags are not defined as Dependent Objects (whereas Comments and Annotations are defined as Dependent Objects). If the TC were to define a construct for tagging using the Dependent Object, I believe we would need two type of objects, Tag and TagApplication (ICOM model). Tag can be a specialized Folder which is the “root parent” of one or more TagApplication’s. A TagApplication is a Dependent Object whose “immediate parent” is any primary CMIS object, a document, a folder, a policy, a relationship that is being tagged. This construct can support Tag Clouds, which is measured by the size of the “Tag” folder.  



> discussion of social features
> -----------------------------
>
>                 Key: CMIS-759
>                 URL: https://issues.oasis-open.org/browse/CMIS-759
>             Project: OASIS Content Management Interoperability Services (CMIS) TC
>          Issue Type: New Feature
>          Components: Domain Model
>    Affects Versions: Proposals for 2.0
>            Reporter: Scott Malabarba
>            Priority: Minor
>
> Placeholder for discussion about the introduction of social features into the specification.
> We can loosely define "social features" to mean metadata that is informally created and managed by end users in order to quickly categorize, find and share content.
> Comments, tags, recommendations and/or ratings, statistics ("most commented", "most downloaded", etc.) all fall into this category. All are document-centric; we would not add a general forums feature to the spec, only comments linked to documents.



--
This message was sent by Atlassian JIRA
(v6.2.2#6258)


[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]