Hi Rubén, Roles in Roles, Tags in Tags! Agreed.
And when it comes to deal between <tags><tag>value 1</tag><tag>value 2</tag></tags> and <tags>value_1,value_2</tags> I would like to learn more about tags in mediapackages and in mediapackage elements - and how we are using them in the project, and then pick on the appropriate approach. My idea would be to notice, that: comma separated list: it encourages to use A..Za..z0..1-_ characters and <tag> approach encourages to use spaces and special characters... Actually I have to learn if we could use this everywhere in the project, that if there is a comma spearated list then only allowed characters are A..Za..z0..1-_ in a list element so list: <alist>abc, def, ghi jkl</alist> is a list of elements: "abc", "def", "hgi" "jkl" and: <items> <item>an element</item></items> Means that everything can be placed in an item. Special characters (Polish letters), spaces etc... But this is a subject to completly different discussion, about the design, and I have to learn more about the project. I am willing to commit to re-implement this feature if we will change the approach on the list representative, after we will make sure that a rule like the one above applies to entire project. I hated comma separated list of contributors/creators(?) in mediapackage. Thanks a lot. --- On Thu, 6/21/12, Rubén Pérez <[email protected]> wrote: From: Rubén Pérez <[email protected]> Subject: Re: [Opencast Matterhorn] Filtering list of Workflows #proposal To: "Opencast Matterhorn" <[email protected]> Cc: "Pawel Fic" <[email protected]> Date: Thursday, June 21, 2012, 11:28 PM Chris, Pawel, The Mediapackage elements can be tagged, too, and those tags are represented as: <tags> <tag>so-and-so</tag> <tag>this-and-that</tag> <tag>you-say-tomato-and-I-say-tohmahtoh</tag></tags> Just giving another alternative. BTW, since we are rising questions that may be addressed in a very long scope, I do think we shouldn't mix role specifications with tags, and we should allow another field for roles: <roles> <role>ROLE_PAWEL</role> <role>ROLE_CHRIS</role></roles> or <roles>ROLE_PAWEL, ROLE_CHRIS</roles> (I think in some places roles are represented as a comma-separated list, which incidentally rises the question of whether or not we should standarize the way we provide lists of elements). I think this discussion is really interesting and, even though what's being discussed here can't be addressed in a short period, a story card should be made to reflect all these questions to be kept for the future. RegardsRubén 2012/6/21 Christopher Brooks <[email protected]> > > <tags> > > <tag>unconference stream</tag> > > <tag>something else</tag> > > </tags> > > > > That would allow you to have spaces in the workflow ids > > again. > > > > > I am not proposing to store workflows IDs in <tags> > I assure you spaces will be allowed in workflow ID if ther are > allowed there now :-) even with comma separated, space separate tags > approach. I understand, this is just some single word semantic identifier to describe the workflow. Understood, Chris -- Christopher Brooks, BSc, MSc ARIES Laboratory, University of Saskatchewan Web: http://www.cs.usask.ca/~cab938 Phone: 1.306.966.1442 Mail: Advanced Research in Intelligent Educational Systems Laboratory Department of Computer Science University of Saskatchewan 176 Thorvaldson Building 110 Science Place Saskatoon, SK S7N 5C9 _______________________________________________ Matterhorn mailing list [email protected] http://lists.opencastproject.org/mailman/listinfo/matterhorn To unsubscribe please email [email protected] _______________________________________________
_______________________________________________ Matterhorn mailing list [email protected] http://lists.opencastproject.org/mailman/listinfo/matterhorn To unsubscribe please email [email protected] _______________________________________________
