Skip to content

Latest commit

 

History

History
103 lines (65 loc) · 4.37 KB

spec23.md

File metadata and controls

103 lines (65 loc) · 4.37 KB
Raw

Pipi Specification

This document defines what it means to be Pipi

Copyright and Language can be found in RFC1

Change Process

This document is governed by the Consensus-Oriented Specification System (COSS).

Goal

To advance the state of the art in the digital creation of content without a clear end-of-life status.

Content Life Cycle

Broadly speaking, content passes through at least four stages; creation, review, management and delivery. Each stage orthogonal to the next; meaning that pursuing one does not advance the next. E.g. no matter how much you create, you won't achieve better management, and regardless of how much you manage, you won't achieve better deliveries.

Each stage must be approached separately and ultimately work together to fulfill the requirements put on you to produce your content. As illustrated, the process is a cycle. Once delivered, creation resumes. This facilitates a iterative development style.

References

Creation involves running your Digital Content Creation Software (DCCS) and, using the tools provided, pursue the goal set by your criteria and requirements.

Pipi is set out to provide DCCS specific tools, both plug-ins to existing DCCS and standalone software.

References

  • Fabric Engine
  • Houdini Engine

Review is the process of sharing your work with others in order to receive feedback. It includes versioning, conform and discoverability of your work so that it may be scrutinised by others with as little effort as possible.

References

  • Shotgun Review
  • FTrack Review

Content management involves the standardisation of output in an attempt to facilitate change, reuse and automation. Content management is the fight against information silos and is the life-blood of the Content Life Cycle.

References

Delivery is the final step of a content life cycle and involves holistic filtering and conform. At the end of a delivery, your content aligns with content much like it. The point of which is to facilitate reuse and automation.

References

  • Shot building
  • Asset library
  • Automated representations

What is Digital Content Creation?

The word 'content' is loosely defined. 'Content' within the context of Pipi means 'data', meaning information. Thus digital content creation is the creation of information by means of computers.

References

What is a framework?

Pipi is a framework. Google defines 'framework' as

an essential supporting structure of a building, vehicle, or object.

Thus Pipi facilitates rapid development of digital content creation systems, also known as digital asset management systems.

Conclusion

Now that we've got that all out of the way, got questions? Have a look at the FAQ. Want to know more? Have a look at the related documents listed above. Still got questions? Contact us or me: