- From: Sridhar Krishnamurthy <ksridhar@amagi.com>
- Date: Tue, 19 Mar 2024 14:32:51 +0530
- To: Joshua Cornejo <josh@marketdata.md>
- Cc: Renato Iannella <r@iannel.la>, public-odrl@w3.org
- Message-ID: <CAML7Ke84rxci-4feRZ7FmcADEd2W1OXD-UMFwaoC+RAo2YMT_g@mail.gmail.com>
Thank you.
Yes sir, I should have defined it.
But I also get the import of the statements made by you all.
Thank you all for the patience shown.
Forgive me if my collaborative manner is not right.
regards
On Tue, Mar 19, 2024 at 1:56 PM Joshua Cornejo <josh@marketdata.md> wrote:
> Good morning Sridhar,
>
>
>
> To clarify, I think it would have been simpler to define amg:dc.
>
>
>
> I also noticed as per Renato’s comment, but focused on your original
> question.
>
>
>
> If you’re satisfied with your definition, I suppose we have no further
> comment around it at this stage.
>
>
>
> Regards,
>
> ___________________________________
>
> *Joshua Cornejo*
>
> *marketdata <https://www.marketdata.md/>*
>
> embed open standards
>
> across your supply chain
>
>
>
> *From: *Sridhar Krishnamurthy <ksridhar@amagi.com>
> *Date: *Tuesday 19 March 2024 at 07:25
> *To: *Joshua Cornejo <josh@marketdata.md>
> *Cc: *Renato Iannella <r@iannel.la>, <public-odrl@w3.org>
> *Subject: *Re: is overloading of leftOperand possible using dataType
> pertaining to rightOperand ?
> *Resent-From: *<public-odrl@w3.org>
> *Resent-Date: *Tue, 19 Mar 2024 07:25:26 +0000
>
>
>
> Respected Sir,
>
>
>
> Forgive me for my persistence with a presumption that I may be wrong.
>
>
>
> I was just trying to use a custom dataType amg:dc to set the type
>
> of the IRI <http://www.amagi.com/metadata/ontologies/media/dc#_VOD>.
>
>
>
> Please see
>
>
>
> # -----[A]-----
>
>
>
> <http://www.w3.org/ns/odrl/2/#constraints>
> a skos:Collection ;
> skos:prefLabel "Constraint"@en ;
> skos:scopeNote "ODRL Core Vocabulary Terms"@en ;
>
> #.....
> skos:member :dataType ;
> skos:member :status .
>
>
>
> :dataType
> a rdf:Property, skos:Concept ;
> rdfs:isDefinedBy odrl: ;
> rdfs:domain :Constraint ;
> rdfs:range rdfs:Datatype ;
> rdfs:label "Datatype"@en ;
> skos:definition "The datatype of the value of the rightOperand or
> rightOperandReference of a Constraint."@en ;
> skos:note "In RDF encodings, use of the rdf:datatype MUST be used. In
> JSON-LD encoding, the use of @type MUST be used."@en .
>
>
>
> # -----[B]-----
>
>
>
> https://www.w3.org/TR/rdf-schema/#ch_datatype
>
> https://www.w3.org/TR/rdf11-concepts/#dfn-recognized-datatype-iris
>
>
>
> On Mon, Mar 18, 2024 at 7:50 PM Joshua Cornejo <josh@marketdata.md> wrote:
>
> Sridhar,
>
>
>
> Renato refers to this 2 lines:
>
>
> odrl:rightOperand <
> http://www.amagi.com/metadata/ontologies/media/dc#_VOD> ;
>
> odrl:dataType amg:dc ;
>
>
>
> Where <http://www.amagi.com/metadata/ontologies/media/dc#_VOD> is a URI,
> could be from the *xsd* namespace you already imported:
>
>
>
> @prefix xsd: <http://www.w3.org/2001/XMLSchema#
> <http://www.w3.org/2001/XMLSchema>> .
>
>
>
> odrl:rightOperand <
> http://www.amagi.com/metadata/ontologies/media/dc#_VOD> ;
>
> odrl:dataType xsd:anyURI ;
>
>
>
> Regards,
>
> ___________________________________
>
> *Joshua Cornejo*
>
> *marketdata <https://www.marketdata.md/>*
>
> embed open standards
>
> across your supply chain
>
>
>
> *From: *Sridhar Krishnamurthy <ksridhar@amagi.com>
> *Date: *Monday 18 March 2024 at 14:06
> *To: *Renato Iannella <r@iannel.la>
> *Cc: *<public-odrl@w3.org>
> *Subject: *Re: is overloading of leftOperand possible using dataType
> pertaining to rightOperand ?
> *Resent-From: *<public-odrl@w3.org>
> *Resent-Date: *Mon, 18 Mar 2024 14:06:29 +0000
>
>
>
> Sir, in the current context i wanted to qualify the type of the
> rightOperand instance as done in
>
> EBU classification schemes in SKOS. As in
> https://www.ebu.ch/metadata/ontologies/skos/ebu_Iso3166_CountryCodeCS.rdf
>
> specified in
> https://www.ebu.ch/metadata/ontologies/skos/?_gl=1*xqztea*_ga*MTkxNTUyMjk1Ni4xNzEwNzY5ODY5*_ga_TVTB816MPW*MTcxMDc2OTg2OS4xLjEuMTcxMDc3MDE4Mi42MC4wLjA
> .
>
>
>
> A snapshot of the above page is presented here in ttl format:
>
>
>
> @prefix countrycode: <
> http://www.ebu.ch/metadata/ontologies/skos/ebu_Iso3166_CountryCodeCS#
> <http://www.ebu.ch/metadata/ontologies/skos/ebu_Iso3166_CountryCodeCS>> .
>
> @prefix dc: <http://purl.org/dc/elements/1.1/> .
> @prefix dct: <http://purl.org/dc/terms/> .
> @prefix ebucore: <http://www.ebu.ch/metadata/ontologies/ebucore/ebucore#
> <http://www.ebu.ch/metadata/ontologies/ebucore/ebucore>> .
> @prefix owl: <http://www.w3.org/2002/07/owl#
> <http://www.w3.org/2002/07/owl>> .
> @prefix rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#
> <http://www.w3.org/1999/02/22-rdf-syntax-ns>> .
> @prefix rdfs: <http://www.w3.org/2000/01/rdf-schema#
> <http://www.w3.org/2000/01/rdf-schema>> .
> @prefix skos: <http://www.w3.org/2004/02/skos/core#
> <http://www.w3.org/2004/02/skos/core>> .
> @prefix xml: <http://www.w3.org/XML/1998/namespace> .
> @prefix xsd: <http://www.w3.org/2001/XMLSchema#
> <http://www.w3.org/2001/XMLSchema>> .
>
> <http://www.ebu.ch/metadata/ontologies/skos/ebu_Iso3166_CountryCodeCS.rdf>
> a owl:Ontology ;
> dct:contributor "EBU metadata community experts" ;
> dct:creator "Jean-Pierre Evain, EBU, metadata@ebu.ch" ;
> dct:description """An RDF vocabulary defining television, radio and
> associated
> media ISO 3166 country codes"""@en ;
> dct:publisher "EBU" ;
> dct:rights "http://creativecommons.org/licenses/by-nc-sa/3.0/" ;
> dct:title "EBU SKOS Classification Scheme for ISO 3166 country
> codes"@en ;
> rdfs:seeAlso <http://www.iso.org/iso/country_codes.htm>,
> <http://www.unc.edu/~rowlett/units/codes/country.htm> .
>
> #........
>
>
> <http://www.ebu.ch/metadata/ontologies/skos/ebu_Iso3166_CountryCodeCS> a
> skos:ConceptScheme ;
> rdfs:label """EBU SKOS Classification Scheme for ISO 3166 country
> codes"""@en ;
> rdfs:isDefinedBy <
> http://www.ebu.ch/metadata/ontologies/skos/ebu_Iso3166_CountryCodeCS> ;
> skos:hasTopConcept
>
> countrycode:_AD,
> countrycode:_US,
> ....,
> .
>
>
>
> #.......
>
>
>
> countrycode:_US a ebucore:CountryCode ;
> skos:changeNote """First version after conversion of P/META into XML.
> First version
> date is version date from ISO""" ;
> skos:example "" ;
> skos:historyNote "2007-04-12" ;
> skos:inScheme <
> http://www.ebu.ch/metadata/ontologies/skos/ebu_Iso3166_CountryCodeCS> ;
> skos:note "Valid" ;
> skos:prefLabel "UNITED STATES"@en,
> "ETATS-UNIS"@fr .
>
>
>
> thanks and regards
>
>
>
>
>
> On Mon, Mar 18, 2024 at 6:46 PM Renato Iannella <r@iannel.la> wrote:
>
> Hi Sridhar…a small point...
>
>
>
> The odrl:dataType is the data type of the value of odrl:rightOperand.
>
>
>
> In the example below, that does not seem correct as the value of
> odrl:rigthOperand is a “URI” datatype.
>
>
>
> Cheers - Renato
>
>
>
>
>
> On 16 Mar 2024, at 18:35, Sridhar Krishnamurthy <ksridhar@amagi.com>
> wrote:
>
>
>
> I tried to model (forgive my naivety) by addressing both of these cases
> through a single leftOperand ('deliveryChannel') and by specifying
> different 'types' of the rightOperand values through odrl:datatype (amg:dc
> for VOD and amg:lc for linear channels).
>
>
>
> The modelling was to be as follows:
>
>
>
> Example (a) :
>
>
>
> <http://example.com/policy:1010>
> a odrl:Set ;
> odrl:permission [
> odrl:action odrl:play ;
> odrl:target <http://example.com/asset:99898> ;
> odrl:constraint [
>
> odrl:leftOperand odrl:deliveryChannel ;
>
> odrl:operator odrl:eq ;
>
> odrl:rightOperand <
> http://www.amagi.com/metadata/ontologies/media/dc#_VOD> ;
>
> odrl:dataType amg:dc ;
>
> ];
>
> ];
>
> .
>
>
>
>
>
>
> *DISCLAIMER: *The contents of this email, including any attachments that
> it may contain, are privileged and confidential information, and may also
> constitute as proprietary, and are intended solely for the use of the
> addressee(s). If you are not the intended recipient, please notify the
> sender by email and delete the original message. Unintended recipients are
> strictly prohibited from copying, disclosing, and/or distributing such
> contents in any manner or form. Opinions, conclusions, and other
> information in this transmission that do not relate to the official
> business of Amagi, including all its affiliates, shall be understood as
> neither given nor endorsed by it. Any statements made herein that are
> tantamount to contractual obligations, promises, claims or commitments
> shall not be binding on the Company unless expressly and specifically
> stated as otherwise, or followed by written confirmation, by an authorized
> signatory of the Company.
>
>
> *DISCLAIMER: *The contents of this email, including any attachments that
> it may contain, are privileged and confidential information, and may also
> constitute as proprietary, and are intended solely for the use of the
> addressee(s). If you are not the intended recipient, please notify the
> sender by email and delete the original message. Unintended recipients are
> strictly prohibited from copying, disclosing, and/or distributing such
> contents in any manner or form. Opinions, conclusions, and other
> information in this transmission that do not relate to the official
> business of Amagi, including all its affiliates, shall be understood as
> neither given nor endorsed by it. Any statements made herein that are
> tantamount to contractual obligations, promises, claims or commitments
> shall not be binding on the Company unless expressly and specifically
> stated as otherwise, or followed by written confirmation, by an authorized
> signatory of the Company.
>
--
**DISCLAIMER: **The contents of this email, including any attachments
that it may contain, are privileged and confidential information, and may
also constitute as proprietary, and are intended solely for the use of the
addressee(s). If you are not the intended recipient, please notify the
sender by email and delete the original message. Unintended recipients are
strictly prohibited from copying, disclosing, and/or distributing such
contents in any manner or form. Opinions, conclusions, and other
information in this transmission that do not relate to the official
business of Amagi, including all its affiliates, shall be understood as
neither given nor endorsed by it. Any statements made herein that are
tantamount to contractual obligations, promises, claims or commitments
shall not be binding on the Company unless expressly and specifically
stated as otherwise, or followed by written confirmation, by an authorized
signatory of the Company.
Received on Tuesday, 19 March 2024 09:03:08 UTC