Calendars with a related space are easier to find and use. Find out why, and set related spaces.
- EDIT THE CALENDAR
Customise the different types of events you'd like to manage in this calendar.#legIndex/#totalLegs
- RESTRICT THE CALENDAR
Optionally, restrict who can view or add events to the team calendar.#legIndex/#totalLegs
- SHARE WITH YOUR TEAM
Grab the calendar's URL and email it to your team, or paste it on a page to embed the calendar.#legIndex/#totalLegs
- ADD AN EVENT
The calendar is ready to go! Click any day on the calendar to add an event or use the Add event button.#legIndex/#totalLegs
Subscribe to calendars using your favourite calendar client.#legIndex/#totalLegs
I've created a brainstorming page for JSON mapping of XJDF and PrintTalk: JSON mapping for XJDF datatypes
There is also a Jira issue: JDF-716 - Getting issue details... STATUS
The entire discussion is based on the epic "JDF in the cloud"
Although JSON has little additional merit compared to XML, we can't keep our eyes closed and ignore JSON. We definitely neither want XJDF to be ignored (too old school; not JSON...), nor do we want variant translation dialects.
Disclaimer: This is not a decision to actually add JSON to XJDF 2.1 but rather a request for comments.
An updated minor version of PrintTalk has been released. See PTK-264 - Getting issue details... STATUS .
We decided to update rather than create an errata version in order to avoid duplicate implementation efforts this early in the release cycle. The schema for PrintTalk 2.0 has been updated to reflect this change. The value of PrintTalk/@Version will not change and remains "2.0".
Updated schema and specification are available at: PrintTalk
The now obsolete 2.0 version has been moved to: PrintTalk Archive
- No labels