W3C home > Mailing lists > Public > public-media-annotation@w3.org > May 2009

RE: Concerning to the available paths for mapping target element in TV-Anytime

From: Evain, Jean-Pierre <evain@ebu.ch>
Date: Tue, 26 May 2009 11:17:25 +0200
Message-ID: <14AE8514098875488F9FEACD90C747A227798A@gnvasmail1a.gva.ebu.ch>
To: "???" <wslee@etri.re.kr>
Cc: <public-media-annotation@w3.org>
Dear Wonsuk,

I said the instance related information would take precedence.

According to what type of programme is being described, one of the following
would come first of  present
/TVAMain/ProgramDescription/ProgramLocationTable/Schedule/ScheduleEvent/Inst
anceDescription/Synopsis
	
/TVAMain/ProgramDescription/ProgramLocationTable/OnDemandProgram/InstanceDes
criptionType/Synopsis
	
/TVAMain/ProgramDescription/ProgramLocationTable/OnDemandService/OnDemandPro
gram/InstanceDescriptionType/Synopsis

AND OF COURSE NOT 

/TVAMain/ProgramDescription/ProgramInformationTable/ProgramInformation/Basic
Description/Synopsis

As you suggested.

Regards,

Jean-pierre

-----Original Message-----
From: 이원석 [mailto:wslee@etri.re.kr] 
Sent: mercredi, 20. mai 2009 18:12
To: Evain, Jean-Pierre
Cc: public-media-annotation@w3.org
Subject: RE: Concerning to the available paths for mapping target element in
TV-Anytime

Dear jean-Pierre.

I added inline comments.

-----Original Message-----
From: Evain, Jean-Pierre [mailto:evain@ebu.ch] 
Sent: Thursday, May 21, 2009 12:07 AM
To: 이원석
Cc: public-media-annotation@w3.org
Subject: RE : Concerning to the available paths for mapping target element
in TV-Anytime


Dear Wonsuk,
 
this is correct.  
 
There is actually some prioritisation that occurs when ever instance related
information is available, which takes precedence over basic programme
information.	

I think you means that
/TVAMain/ProgramDescription/ProgramInformationTable/ProgramInformation/Basic
Description/Synopsis is the first.
Am I right?
But I am not sure how could we define the orders for others and we need to
add the order information to the ontology as some values.
I think this is a practical issue for implementing the ontology and API.

I wouldn't put the "relation description" in this category. You can remove
it from the second list.

Could you explain more about "relation description"? I couldn't got the
exact meaning of this.

Best regards,
Wonsuk


Regards,
 
jean-Pierre 

	-------- Message d'origine-------- 
	De: ??? [mailto:wslee@etri.re.kr] 
	Date: mer. 20.05.2009 16:45 
	À: Evain, Jean-Pierre 
	Cc: public-media-annotation@w3.org 
	Objet: Concerning to the available paths for mapping target element
in TV-Anytime
	
	

	Dear Jean-Pierre and all,

	 

	When I reviewed the mapping information of TV-Anytime, I wonder that
I can find a lot of the mapping target element in many paths.

	For example as you defined, ma:description could be mapped with the
information of Synopsis, Description, Keywords, PromotionalInformation,
ParentalGuidance, AwardList / Award.

	This means that Synopsis is one of mapping information related with
ma:description.

	By the way I can fine the available paths of Synopsis in TV-Anytime
XML schema as below.

	 

	
/TVAMain/ProgramDescription/ProgramInformationTable/ProgramInformation/Basic
Description/Synopsis

	
/TVAMain/ProgramDescription/ProgramLocationTable/Schedule/ScheduleEvent/Inst
anceDescription/Synopsis

	
/TVAMain/ProgramDescription/ProgramLocationTable/OnDemandProgram/InstanceDes
criptionType/Synopsis

	
/TVAMain/ProgramDescription/ProgramLocationTable/OnDemandService/OnDemandPro
gram/InstanceDescriptionType/Synopsis

	
/TVAMain/ProgramDescription/SegmentInformationTable/SegmentList/SegmentInfor
mation/Description/Synopsis

	
/TVAMain/ProgramDescription/SegmentInformationTable/SegmentGroupList/Segment
GroupInformation/Description/Synopsis

	 

	In case of Description, it has same situation as below

	
/TVAMain/ProgramDescription/ProgramInformationTable/ProgramInformation/Basic
Description/PurchaseList/PurchaseItem/Description

	
/TVAMain/ProgramDescription/GroupInformationTable/GroupInformation/BasicDesc
ription/PurchaseList/PurchaseItem/Description

	
/TVAMain/ProgramDescription/ProgramLocationTable/Schedule/ScheduleEvent/Inst
anceDescription/PurchaseList/PurchaseItem/Description

	
/TVAMain/ProgramDescription/ProgramLocationTable/BroadcaseEvent/InstanceDesc
ription/PurchaseList/PurchaseItem/Description

	
/TVAMain/ProgramDescription/ProgramLocationTable/OnDemandService/OnDemandPro
gram/InstanceDescription/PurchaseList/PurchaseItem/Description

	
/TVAMain/ProgramDescription/ProgramLocationTable/OnDemandProgram/InstanceDes
cription/PurchaseList/PurchaseItem/Description

	
/TVAMain/ProgramDescription/ProgramInformationTable/PurchaseInformation/Desc
ription

	
/TVAMain/ProgramDescription/ProgramInformationTable/ProgramInformation/Deriv
edFrom/DerivationReason/Description

	
/TVAMain/ProgramDescription/SegmentInformationTable/SegmentList/SegmentInfor
mation/Description (BasicSegmentDescriptionType)

	
/TVAMain/ProgramDescription/SegmentInformationTable/SegmentGroupList/Segment
GroupInformation/Description (BasicSegmentDescriptionType)

	 

	Am I right?

	If it’s right, should we have to handle this all paths or select one
?

	 

	best regards,

	Wonsuk

	 

-----------------------------------------
**************************************************

This email and any files transmitted with it 
are confidential and intended solely for the 
use of the individual or entity to whom they
are addressed. 
If you have received this email in error, 
please notify the system manager.
This footnote also confirms that this email 
message has been swept by the mailgateway

**************************************************



Received on Tuesday, 26 May 2009 09:18:18 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 26 May 2009 09:18:18 GMT