diff --git a/PublicSchedule_Schema_2.0.doc b/PublicSchedule_Schema_2.0.doc
new file mode 100755
index 0000000..5add8cd
Binary files /dev/null and b/PublicSchedule_Schema_2.0.doc differ
diff --git a/README b/README
new file mode 100755
index 0000000..e69de29
diff --git a/README.md b/README.md
index 1a50cc3..5f00ef4 100644
--- a/README.md
+++ b/README.md
@@ -15,14 +15,4 @@ Material contains technical data of the transmission or video file, such as aspe
Material also contains rights for the programs, for example if it is allowed to be viewed on a tablet or allowed to
recorded and be available on demand.
-#History
-Public Schedule was invented by a joined effort from two of the major TV-channels in Sweden. The reason behind the effort was the lack of a common standard within this area, that
-also would enable to exchange information of new demands within the TV-area. It was also important that this would
-be kept an open standard, not proprietary to any of the founders, and that the format should evolve over time.
-Seeking broad acceptance for Public Schedule is also important for enabling it as a standard.
-
-The founders was TV4 and SVT. TeliaSonera, one of the major distributors in the Nordics, was an early adopter of the standard. When it was time do develop the next version 4 of Public Schedule, TeliaSonera took the lead, and it was also at this time as June was involved as contributor.
-
-TerracomBoxer, one of the other major distributors in the Nordic is also supporting this standard, and when there was
-a need to let this standard be supervised by an external, independant organization, June was asked to perform this task.
diff --git a/content.xsd b/content.xsd
new file mode 100755
index 0000000..0043d56
--- /dev/null
+++ b/content.xsd
@@ -0,0 +1,303 @@
+
+
+
+
+
+
+ Root element for content object
+
+
+
+
+
+
+ unique id for content, should include provider name
+
+
+
+
+ id for series, not unique
+
+
+
+
+ if available, the no of the season, start with 1
+
+
+
+
+ episode number in this content, could be 0
+
+
+
+
+ no of episodes in this content, could be 0
+
+
+
+
+
+
+
+
+
+
+
+ list of production countries
+
+
+
+
+ title list for content, limited length, see type. At least one occurence for swedish language (normally) should occur
+
+
+
+
+ description list for series, limited length, see type
+
+
+
+
+ short description list for content, limited length, see type
+
+
+
+
+ same as short description list, but longer limited length, see type
+
+
+
+
+ dvb genres, two numbers between 0-15
+
+
+
+
+ list of keywords for the content, should be single words, and consistent within each provider
+
+
+
+
+ list of actors, producers etc. should be consistent within each provider
+
+
+
+
+ list of content related media such as images and weblinks
+
+
+
+
+ This is for usage for the graphical presentation of the content in for instance a VOD shop.
+
+
+
+
+ Category path expression
+
+
+
+
+ true indicates regional content
+
+
+
+
+ Parental rating 3-18y
+
+
+
+
+
+
+
+
+
+
+
+ Timestamp when document is created
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ code in ISO 639-2
+
+
+
+
+
+
+
+
+
+ code in ISO 3166-1-alpha-2
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ lower level means higher importance
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ element in a category tree
+
+
+
+
+
+
+ position in category tree
+
+
+
+
+
+
+
+
+
+ importance of category
+
+
+
+
+
+
+
+
+
+
+
+ content for this event, optional. if not set contentIdRef must be set
+
+
+
+
+
diff --git a/event.xsd b/event.xsd
new file mode 100755
index 0000000..57233c0
--- /dev/null
+++ b/event.xsd
@@ -0,0 +1,119 @@
+
+
+
+
+
+
+ root node of event
+
+
+
+
+
+
+
+ unique id for the event, should start with provider name, for example: 'se.svt.123456'
+
+
+
+
+ id for the current service or channel, could be for example 'se.svt.svt2', 'se.svt.play' or 'se.tv4.tv4plus'
+
+
+
+
+ start date and time for the event. in UTC timezone
+
+
+
+
+ end date and time for the event. in UTC timezone
+
+
+
+
+ duration for the event. in timecode format, for exmple 00:30:00:00
+
+
+
+
+ indicates if this is a rerun, the rules for decision could is set by the provider and could be different between providers
+
+
+
+
+ indicates if this event is live
+
+
+
+
+ indicates if this event is hidden, i.e. if it should be public
+
+
+
+
+
+
+
+
+
+
+ reference to contentId for this event for convinience as this could be obtained via materialIdRef
+
+
+
+
+ reference to contentId for this event
+
+
+
+
+ list if events that occured in time before current event, i.e. same contentId
+
+
+
+
+ list of events that occured in time after current event, i.e. same contentId
+
+
+
+
+
+
+
+
+
+
+
+
+ list of events that occurs as part of current event.
+
+
+
+
+
+ Timestamp when document is created
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
diff --git a/material.xsd b/material.xsd
new file mode 100755
index 0000000..4855c21
--- /dev/null
+++ b/material.xsd
@@ -0,0 +1,268 @@
+
+
+
+
+
+
+ Root element for material object
+
+
+
+
+
+
+ unique id for content, should include provider name
+
+
+
+
+ reference to content
+
+
+
+
+ type of material, for example TX (Transmission Copy)
+
+
+
+
+ format for video, for example HD
+
+
+
+
+ list of available audio for this material
+
+
+
+
+ aspect ratio for the material
+
+
+
+
+ list of available subtitles
+
+
+
+
+ list of reference to physical material, could be filenames or an url
+
+
+
+
+ list of rights for this material, each right is for a rights period
+
+
+
+
+
+ Timestamp when document is created
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ audio format, for example surround
+
+
+
+
+
+
+
+
+
+ code in ISO 639-2
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ type of subtitle, for example teletext
+
+
+
+
+
+
+
+
+
+ code in ISO 639-2
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ type of reference, for example video or audio
+
+
+
+
+
+
+
+
+
+
+
+
+ duration in timecode for referenced material, example 00:00:00:00
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ DateTime in UTC
+
+
+
+
+ start of period where right is valid
+
+
+
+
+ end of period where right is valid
+
+
+
+
+ indicates if there is a period or not. If true, the rightsCategory is valid until otherwise said
+
+
+
+
+ list of right categories
+
+
+
+
+
+
+
+
+
+
+
+
+
+ type of rights category, could for example be timeshift
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Reference to external rights type definition; for instance se.tv4.paymentref3
+
+
+
+
+
+
+
+ options for the selected type
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
diff --git a/publicSchedule_teknisk beskrivning_2.3.doc b/publicSchedule_teknisk beskrivning_2.3.doc
new file mode 100755
index 0000000..89412fe
Binary files /dev/null and b/publicSchedule_teknisk beskrivning_2.3.doc differ
diff --git a/publish.xsd b/publish.xsd
new file mode 100755
index 0000000..2c927ed
--- /dev/null
+++ b/publish.xsd
@@ -0,0 +1,47 @@
+
+
+
+
+
+
+
+
+
+ root node of publish
+
+
+
+
+
+ id for the provider, could be for example 'se.svt' or 'se.tv4'
+
+
+
+
+ content list for the document, at least 1 content is required
+
+
+
+
+ material list for the document, could be 0 entries
+
+
+
+
+ Event list for the document, could be 0 entries
+
+
+
+
+ id for the current service or channel, could be for example 'se.svt.svt2', 'se.svt.play' or 'se.tv4.tv4plus'
+
+
+
+
+
+ Timestamp when document is created
+
+
+
+
+
diff --git a/schedule.xsd b/schedule.xsd
new file mode 100755
index 0000000..98df95c
--- /dev/null
+++ b/schedule.xsd
@@ -0,0 +1,52 @@
+
+
+
+
+
+
+
+
+
+ root node of schedule, always complete
+
+
+
+
+
+ Start dateTime from which the events in this document occur
+
+
+
+
+ End dateTime from which the events in this document occur
+
+
+
+
+ id for the provider, could be for example 'se.svt' or 'se.tv4'
+
+
+
+
+ content list for the document, could be 0 entries which would indicate no events for this period
+
+
+
+
+ material list for the document, could be 0 entries which would indicate no events for this period
+
+
+
+
+ event list for the document, could be 0 entries which would indicate no events for this period
+
+
+
+
+
+ Timestamp when document is created
+
+
+
+
+