Hi Marc
The six main activities/functional requirements that you list for the datasets seem very much to speak to the capabilities of Fedora. Fedora's capable of managing assets with a large degree of flexibility in how those assets are to be modelled. It also has a XACML-based access control layer which would seem to be of some relevance I think. Are there any specific use cases you have that perhaps would allow us to comment in a little bit more detail how Fedora's capability may be applied to them? Regards Steve _____ From: J. Marc Edwards [mailto:marc.edwa...@nimbisservices.com] Sent: 19 September 2011 11:02 To: fedora-commons-users@lists.sourceforge.net Subject: [fcrepo-user] Fedora Object Model application in cloud computing model for semiconductor design-to-release-manufacturing portal... All: It seems to me that Fedora has been primarily applied to digital libraries. However, in my review of the Fedora project, it seems to me that perhaps the fundamental technology could be applied in the domain space of digital rights management workflows for cloud computing services. I'd very much welcome some candid feedback on my thoughts of applying Fedora in this manner. I'm presently developing a semiconductor design-to-release-manufacturing, WorkFlow-as-a-Service (WFaaS) & Digital-Rights-as-a-Service (DRaaS) cloud computing portal. Here is a brief description of the problem. The semiconductor industry is characterized by four (4) distinct supply chain stakeholders, namely, (1) Silicon manufacturing foundries, (2) Electronic Design Automation (EDA) ISVs, (3) semiconductor intellectual property (SIP) providers, and (4) designers. These four (4) identity profiles constitute a tangled web of inter-organizational workflows and processes that will be addressed through the WFaaS & DRaaS cloud offering. My assertion is that within the context of an inter-organizational workflow, WFaaS is a producer and consumer of intellectual property and therefore mandates an effective digital rights service, ala, DRaaS. Semiconductor design is almost ubiquitously defined through the generation and use of intellectual property. The production and consumption of IP within the semiconductor design process is manifested through thousands of specialized datasets that must be (1) tracked, (2) managed, (3) tagged, (4) version controlled, (5) archived, and (6) life cycle managed ACROSS the multiple semiconductor supply chain identity profiles previously noted. >From this extremely succinct description of the problem, does this community believe that the various software and object models defined by the Fedora project would be an appropriate application of Fedora's objectives as applied to the development of a Digital-Rights-as-a-Service (DRaaS) for the life cycle management and provisioning of digital IP for semiconductor design? Kind regards, Marc -- J. Marc Edwards Lead Architect - Semiconductor Design Portals Nimbis Services, Inc. Skype: (919) 747-3775 Cell: (919) 345-1021 Fax: (919) 882-8602 marc.edwa...@nimbisservices.com www.nimbisservices.com
------------------------------------------------------------------------------ BlackBerry® DevCon Americas, Oct. 18-20, San Francisco, CA Learn about the latest advances in developing for the BlackBerry® mobile platform with sessions, labs & more. See new tools and technologies. Register for BlackBerry® DevCon today! http://p.sf.net/sfu/rim-devcon-copy1
_______________________________________________ Fedora-commons-users mailing list Fedora-commons-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/fedora-commons-users
