Re: [dam-cmis-profile-discuss] Draft Technical Committee Charter: CMIS4DAM

[Chet Ensign <chet.ensign@oasis-open.org>]

Hi Ralph, hi Ray - 

Apologies, I got behind - I was going to send you my thoughts on the use case question. 

Ralph, I think a few short use cases in the purpose section of a charter help crystalize for readers the purpose of the effort by highlighting problems to which they can relate. You can see an example in the Legal Citations charter where several typical, generic operational problems were included: https://www.oasis-open.org/committees/legalcitem/charter.php 

So I think including a few like that definitely helps. If nothing else, the "oh yeah! I had that problem yesterday" personal recognition keeps people reading. 

The FAQ, I think, is a great place to include even more and with a bit more meat to them. Most TC proposers don't put together a FAQ which I think is too bad because it can really go a long way towards explaining the value of the outcome and getting key people on board. Carol loves getting FAQs with charters because she can use them to help with recruitment and education. 

So my suggestion is: a few lightening-rod type use cases in the statement of purpose to get people's attention and then your more fleshed out use cases in the FAQ. 

/chet

On Sat, May 10, 2014 at 7:33 AM, Ralph Windsor <ralph@daydream.co.uk> wrote:

Hi Ray,

> Is that the sort of feedback you were looking for?

Yes, definitely, that's exactly what I was looking for.

You make a fair point about the use cases and expanding the scope outside metadata.  I am envisaging a lot of effort just to get the metadata elements widely used and accepted across the DAM industry which is probably why I focussed on it.  You are correct, however, we should still anticipate this so there is some kind of road map for the work ahead.

I will expand the scope section and make the required adjustments to the statement of purpose.  I'm not sure where to put the use cases, do they go in this proposal, or a separate document?  I see there is an FAQ section, would that be suitable?

This is the first OASIS Technical Committee proposal I've written, so any guidance on how to structure this properly (what to go where etc) would be greatly appreciated.  I'll review some of the other examples that Chet has passed on also.

Thanks,

Ralph

-----Original Message-----
From: Ray Gauss II [mailto:ray.gauss@alfresco.com]
Sent: 09 May 2014 15:13
To: ralph@daydream.co.uk
Cc: dam-cmis-profile-discuss@lists.oasis-open.org
Subject: Re: [dam-cmis-profile-discuss] Draft Technical Committee Charter: CMIS4DAM

Hi Ralph,

Thanks for keeping the ball rolling on this and starting the draft.

We may want to outline some of those high level use cases before solidifying the Statement of Purpose and Scope.  Those usage scenarios shouldn’t necessarily be tied to the potential standards used, but be as generic as possible and only describe the workflow, systems involved, and the type of interaction and data needed between those systems for that use case.  I hope to have some time to draft a few examples in the near future.

At the moment the Statement of Purpose and Scope sections seem primarily focused on metadata.  The definition of additional rendition kinds, and as we’ve discussed here, possibly even defining the means to request the creation of 'ad-hoc’ renditions, may end up as part of the standard.  Perhaps we could broaden those sections.

Rapid implementation should certainly be a goal of the community around the standard, but I’m not sure how much it should directly influence the standard itself, that's really up to the libraries/SDKs that work with it.  We may want to consider changing the language of the Scope section a bit to reflect that.

Is that the sort of feedback you were looking for?

Regards,

Ray


On May 1, 2014 at 3:53:06 PM, Ralph Windsor (ralph@daydream.co.uk) wrote:
> After a bit of a pause, we have made some progress on a draft technical
> committee charter in regard to "CMIS4DAM" (which is the friendlier name that
> Carol Geyer of OASIS suggested we use for this standard).
>
> I have written a DAM News article about it and placed a link to the docs
> which you can download here (no registration required)
>
> http://digitalassetmanagementnews.org/wp-content/uploads/2014/05/Draft-Propo
> sal-for-New-OASIS-Technical-Committee_r002.docx
>
> It would be useful to get some feedback on this from list participants.
> Once agreed, we will need to have this sponsored also by five people from at
> least two OASIS organisational members.
>
> Based on information kindly provided by Florian Mueller a few months ago, we
> are planning some basic examples also to explain how to access a CMIS
> repository and from that we will need to consider how to incorporate various
> DAM standards like IPTC, PLUS, PBCore etc so they can interoperate with
> CMIS. That is likely to be the point where we move away from the procedural
> discussion and into the more in-depth technical elements.
>
> Any questions, comments etc, please feel free to respond to myself and/or
> the list.
>
> Thanks,
>
> Ralph
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dam-cmis-profile-discuss-unsubscribe@lists.oasis-open.org
> For additional commands, e-mail: dam-cmis-profile-discuss-help@lists.oasis-open.org
>
>

--

/chet 
----------------
Chet Ensign
Director of Standards Development and TC Administration 
OASIS: Advancing open standards for the information society
http://www.oasis-open.org

Primary: +1 973-996-2298
Mobile: +1 201-341-1393 

Check your work using the Support Request Submission Checklist at http://www.oasis-open.org/committees/download.php/47248/tc-admin-submission-checklist.html 

TC Administration information and support is available at http://www.oasis-open.org/resources/tcadmin

Follow OASIS on:
LinkedIn:    http://linkd.in/OASISopen
Twitter:        http://twitter.com/OASISopen
Facebook:  http://facebook.com/oasis.open