http://ontologydesignpatterns.org/api.php?action=feedcontributions&feedformat=atom&user=VictorRodriguezDoncel 2026-06-04T08:21:25Z User contributions MediaWiki 1.25.6 http://ontologydesignpatterns.org/index.php?title=Submissions:LicenseLinkedDataResources&diff=11616 2013-07-18T21:31:07Z

<p>VictorRodriguezDoncel: Article is waiting for review.</p> <hr /> <div>{{Content_OP_Proposal_toolbar}}<br /> {{Graphical representation header}}<br /> {{Graphical representation<br /> |ImageName=licenselinkeddataresources.png<br /> }}<br /> {{Content OP Proposal Template<br /> |SubmittedBy=VictorRodriguezDoncel<br /> |Name=LicenseLinkedDataResources<br /> |Intent=To provide a pattern for expressing rights on Linked Data Resources, understood as RDF triples, datasets or mappings.<br /> These rights include intellectual property rights, database rights and the right of access, which can be limited by personal data protection laws and others.<br /> Rights expressions may assert, waive and license the rights, either conditionally or inconditionally, either to the public or to agents in particular.<br /> |Domain=Linked Data<br /> |ContentODPDescription=-Adhere to the underlying structure present in other Rights Expression Languages<br /> <br /> -Be able to represent existing known licenses (i.e. Creative Commons licenses etc.)<br /> <br /> -Support database rights: extraction and re-utilization<br /> <br /> -Support privacy law (personal data handling) and the right to access<br /> <br /> -Support the intellectual property law rights: reproduction, distribution, transformation<br /> <br /> -Support these right declarations: Unconditionally waiving rights, Restating that some rights are reserved, Licensing rights subject to conditions<br /> <br /> -Supporting existing licensing practices for RDF resources<br /> <br /> -Supporting these business models: Open data business models, Non open data business models, Hybrid models.<br /> |ReusableOWLBuildingBlock=http://purl.oclc.org/NET/lldr/ns#<br /> |Consequences=A more precise attribution of rights expression to Linked Data<br /> |Scenario=Declaring rights on both Linked Open Data and Linked Closed Data<br /> |SpecializationOf=http://ontologydesignpatterns.org/wiki/Submissions:N-Ary_Relation_Pattern_(OWL_2)<br /> }}<br /> {{Element list header}}<br /> {{Has Element Template<br /> |HasElement=http://vocab.deri.ie/void#<br /> }}<br /> {{Has Element Template<br /> |HasElement=http://xmlns.com/foaf/0.1/<br /> }}<br /> {{Has Element Template<br /> |HasElement=http://creativecommons.org/ns#<br /> }}<br /> {{Has Element Template<br /> |HasElement=http://purl.org/dc/terms/<br /> }}<br /> {{Has Element Template<br /> |HasElement=http://purl.org/dc/elements/1.1/<br /> }}<br /> {{Additional information header}}<br /> <br /> {{Scenarios about me}}<br /> {{Reviews about me}}<br /> {{Modeling issues about me}}<br /> {{My references}}<br /> {{Submission to event<br /> |Event=WOP at ISWC2013<br /> }}<br /> {{Submission to event}}<br /> [[Category:Waiting for review]]</div>

VictorRodriguezDoncel http://ontologydesignpatterns.org/index.php?title=Submissions:LicenseLinkedDataResources&diff=11615 2013-07-18T20:38:46Z

<p>VictorRodriguezDoncel: </p> <hr /> <div>{{Content_OP_Proposal_toolbar}}<br /> {{Graphical representation header}}<br /> {{Graphical representation<br /> |ImageName=licenselinkeddataresources.png<br /> }}<br /> {{Content OP Proposal Template<br /> |SubmittedBy=VictorRodriguezDoncel<br /> |Name=LicenseLinkedDataResources<br /> |Intent=To provide a pattern for expressing rights on Linked Data Resources, understood as RDF triples, datasets or mappings.<br /> These rights include intellectual property rights, database rights and the right of access, which can be limited by personal data protection laws and others.<br /> Rights expressions may assert, waive and license the rights, either conditionally or inconditionally, either to the public or to agents in particular.<br /> |Domain=Linked Data<br /> |ContentODPDescription=-Adhere to the underlying structure present in other Rights Expression Languages<br /> <br /> -Be able to represent existing known licenses (i.e. Creative Commons licenses etc.)<br /> <br /> -Support database rights: extraction and re-utilization<br /> <br /> -Support privacy law (personal data handling) and the right to access<br /> <br /> -Support the intellectual property law rights: reproduction, distribution, transformation<br /> <br /> -Support these right declarations: Unconditionally waiving rights, Restating that some rights are reserved, Licensing rights subject to conditions<br /> <br /> -Supporting existing licensing practices for RDF resources<br /> <br /> -Supporting these business models: Open data business models, Non open data business models, Hybrid models.<br /> |ReusableOWLBuildingBlock=http://purl.oclc.org/NET/lldr/ns#<br /> |Consequences=A more precise attribution of rights expression to Linked Data<br /> |Scenario=Declaring rights on both Linked Open Data and Linked Closed Data<br /> |SpecializationOf=http://ontologydesignpatterns.org/wiki/Submissions:N-Ary_Relation_Pattern_(OWL_2)<br /> }}<br /> {{Element list header}}<br /> {{Has Element Template<br /> |HasElement=http://vocab.deri.ie/void#<br /> }}<br /> {{Has Element Template<br /> |HasElement=http://xmlns.com/foaf/0.1/<br /> }}<br /> {{Has Element Template<br /> |HasElement=http://creativecommons.org/ns#<br /> }}<br /> {{Has Element Template<br /> |HasElement=http://purl.org/dc/terms/<br /> }}<br /> {{Has Element Template<br /> |HasElement=http://purl.org/dc/elements/1.1/<br /> }}<br /> {{Additional information header}}<br /> <br /> {{Scenarios about me}}<br /> {{Reviews about me}}<br /> {{Modeling issues about me}}<br /> {{My references}}<br /> {{Submission to event<br /> |Event=WOP at ISWC2013<br /> }}<br /> {{Submission to event}}</div>

VictorRodriguezDoncel http://ontologydesignpatterns.org/index.php?title=Submissions:LicenseLinkedDataResources&diff=11614 2013-07-18T20:38:08Z

<p>VictorRodriguezDoncel: </p> <hr /> <div>{{Content_OP_Proposal_toolbar}}<br /> {{Graphical representation header}}<br /> {{Graphical representation<br /> |ImageName=licenselinkeddataresources.png<br /> }}<br /> {{Content OP Proposal Template<br /> |SubmittedBy=VictorRodriguezDoncel<br /> |Name=LicenseLinkedDataResources<br /> |Intent=To provide a pattern for expressing rights on Linked Data Resources, understood as RDF triples, datasets or mappings.<br /> These rights include intellectual property rights, database rights and the right of access, which can be limited by personal data protection laws and others.<br /> Rights expressions may assert, waive and license the rights, either conditionally or inconditionally, either to the public or to agents in particular.<br /> |Domain=Linked Data<br /> |ContentODPDescription=-Adhere to the underlying structure present in other Rights Expression Languages<br /> <br /> -Be able to represent existing known licenses (i.e. Creative Commons licenses etc.)<br /> <br /> -Support database rights: extraction and re-utilization<br /> <br /> -Support privacy law (personal data handling) and the right to access<br /> <br /> -Support the intellectual property law rights: reproduction, distribution, transformation<br /> <br /> -Support these right declarations: Unconditionally waiving rights, Restating that some rights are reserved, Licensing rights subject to conditions<br /> <br /> -Supporting existing licensing practices for RDF resources<br /> <br /> -Supporting these business models: Open data business models, Non open data business models, Hybrid models.<br /> |ReusableOWLBuildingBlock=http://purl.oclc.org/NET/lldr/ns#<br /> |Consequences=A more precise attribution of rights expression to Linked Data<br /> |Scenario=Declaring rights on both Linked Open Data and Linked Closed Data<br /> |SpecializationOf=n-ary relation pattern<br /> }}<br /> {{Element list header}}<br /> {{Has Element Template<br /> |HasElement=http://vocab.deri.ie/void#<br /> }}<br /> {{Has Element Template<br /> |HasElement=http://xmlns.com/foaf/0.1/<br /> }}<br /> {{Has Element Template<br /> |HasElement=http://creativecommons.org/ns#<br /> }}<br /> {{Has Element Template<br /> |HasElement=http://purl.org/dc/terms/<br /> }}<br /> {{Has Element Template<br /> |HasElement=http://purl.org/dc/elements/1.1/<br /> }}<br /> {{Additional information header}}<br /> <br /> {{Scenarios about me}}<br /> {{Reviews about me}}<br /> {{Modeling issues about me}}<br /> {{My references}}<br /> {{Submission to event<br /> |Event=WOP at ISWC2013<br /> }}<br /> {{Submission to event}}</div>

VictorRodriguezDoncel http://ontologydesignpatterns.org/index.php?title=Submissions:LicenseLinkedDataResources&diff=11613 2013-07-18T20:37:18Z

<p>VictorRodriguezDoncel: </p> <hr /> <div>{{Content_OP_Proposal_toolbar}}<br /> {{Graphical representation header}}<br /> {{Graphical representation<br /> |ImageName=licenselinkeddataresources.png<br /> }}<br /> {{Content OP Proposal Template<br /> |SubmittedBy=VictorRodriguezDoncel<br /> |Name=LicenseLinkedDataResources<br /> |Intent=To provide a pattern for expressing rights on Linked Data Resources, understood as RDF triples, datasets or mappings.<br /> These rights include intellectual property rights, database rights and the right of access, which can be limited by personal data protection laws and others.<br /> Rights expressions may assert, waive and license the rights, either conditionally or inconditionally, either to the public or to agents in particular.<br /> |Domain=Linked Data<br /> |ContentODPDescription=-Adhere to the underlying structure present in other Rights Expression Languages<br /> <br /> -Be able to represent existing known licenses (i.e. Creative Commons licenses etc.)<br /> <br /> -Support database rights: extraction and re-utilization<br /> <br /> -Support privacy law (personal data handling) and the right to access<br /> <br /> -Support the intellectual property law rights: reproduction, distribution, transformation<br /> <br /> -Support these right declarations: Unconditionally waiving rights, Restating that some rights are reserved, Licensing rights subject to conditions<br /> <br /> -Supporting existing licensing practices for RDF resources<br /> <br /> -Supporting these business models: Open data business models, Non open data business models, Hybrid models.<br /> |ReusableOWLBuildingBlock=http://purl.oclc.org/NET/lldr/ns#<br /> |Consequences=A more precise attribution of rights expression to Linked Data<br /> |Scenario=Declaring rights on both Linked Open Data and Linked Closed Data<br /> |SpecializationOf=n-ary relation pattern<br /> }}<br /> {{Element list header}}<br /> {{Has Element Template<br /> |HasElement=http://vocab.deri.ie/void#<br /> }}<br /> {{Has Element Template<br /> |HasElement=http://xmlns.com/foaf/0.1/<br /> }}<br /> {{Has Element Template<br /> |HasElement=http://creativecommons.org/ns#<br /> }}<br /> {{Has Element Template<br /> |HasElement=http://purl.org/dc/terms/<br /> }}<br /> {{Has Element Template<br /> |HasElement=http://purl.org/dc/elements/1.1/<br /> }}<br /> {{Additional information header}}<br /> asdf<br /> {{Scenarios about me}}<br /> {{Reviews about me}}<br /> {{Modeling issues about me}}<br /> {{My references}}</div>

VictorRodriguezDoncel http://ontologydesignpatterns.org/index.php?title=Submissions:LicenseLinkedDataResources&diff=11612 2013-07-18T20:35:17Z

<p>VictorRodriguezDoncel: </p> <hr /> <div>{{Content_OP_Proposal_toolbar}}<br /> {{Graphical representation header}}<br /> {{Graphical representation<br /> |ImageName=licenselinkeddataresources.png<br /> }}<br /> {{Content OP Proposal Template<br /> |SubmittedBy=VictorRodriguezDoncel<br /> |Name=LicenseLinkedDataResources<br /> |Intent=To provide a pattern for expressing rights on Linked Data Resources, understood as RDF triples, datasets or mappings.<br /> These rights include intellectual property rights, database rights and the right of access, which can be limited by personal data protection laws and others.<br /> Rights expressions may assert, waive and license the rights, either conditionally or inconditionally, either to the public or to agents in particular.<br /> |Domain=Linked Data<br /> |ContentODPDescription=-Adhere to the underlying structure present in other Rights Expression Languages<br /> <br /> -Be able to represent existing known licenses (i.e. Creative Commons licenses etc.)<br /> <br /> -Support database rights: extraction and re-utilization<br /> <br /> -Support privacy law (personal data handling) and the right to access<br /> <br /> -Support the intellectual property law rights: reproduction, distribution, transformation<br /> <br /> -Support these right declarations: Unconditionally waiving rights, Restating that some rights are reserved, Licensing rights subject to conditions<br /> <br /> -Supporting existing licensing practices for RDF resources<br /> <br /> -Supporting these business models: Open data business models, Non open data business models, Hybrid models.<br /> <br /> |ReusableOWLBuildingBlock=http://purl.oclc.org/NET/lldr/ns#<br /> |Consequences=A more precise attribution of rights expression to Linked Data<br /> |Scenario=Declaring rights on both Linked Open Data and Linked Closed Data<br /> |SpecializationOf=n-ary relation pattern<br /> }}<br /> {{Element list header}}<br /> {{Additional information header}}<br /> asdf<br /> {{Scenarios about me}}<br /> {{Reviews about me}}<br /> {{Modeling issues about me}}<br /> {{My references}}</div>

VictorRodriguezDoncel http://ontologydesignpatterns.org/index.php?title=Submissions:LicenseLinkedDataResources&diff=11611 2013-07-18T20:34:27Z

<p>VictorRodriguezDoncel: </p> <hr /> <div>{{Content_OP_Proposal_toolbar}}<br /> {{Graphical representation header}}<br /> {{Graphical representation<br /> |ImageName=licenselinkeddataresources.png<br /> }}<br /> {{Content OP Proposal Template<br /> |SubmittedBy=VictorRodriguezDoncel<br /> |Name=LicenseLinkedDataResources<br /> |Intent=To provide a pattern for expressing rights on Linked Data Resources, understood as RDF triples, datasets or mappings.<br /> These rights include intellectual property rights, database rights and the right of access, which can be limited by personal data protection laws and others.<br /> Rights expressions may assert, waive and license the rights, either conditionally or inconditionally, either to the public or to agents in particular.<br /> |Domain=Linked Data<br /> |ContentODPDescription=-Adhere to the underlying structure present in other Rights Expression Languages<br /> -Be able to represent existing known licenses (i.e. Creative Commons licenses etc.)<br /> -Support database rights: extraction and re-utilization<br /> -Support privacy law (personal data handling) and the right to access<br /> -Support the intellectual property law rights: reproduction, distribution, transformation<br /> -Support these right declarations: Unconditionally waiving rights, Restating that some rights are reserved, Licensing rights subject to conditions<br /> -Supporting existing licensing practices for RDF resources<br /> -Supporting these business models: Open data business models, Non open data business models, Hybrid models.<br /> <br /> <br /> |ReusableOWLBuildingBlock=http://purl.oclc.org/NET/lldr/ns#<br /> |Consequences=A more precise attribution of rights expression to Linked Data<br /> |Scenario=Declaring rights on both Linked Open Data and Linked Closed Data<br /> |SpecializationOf=n-ary pattern<br /> }}<br /> {{Element list header}}<br /> {{Additional information header}}<br /> asdf<br /> {{Scenarios about me}}<br /> {{Reviews about me}}<br /> {{Modeling issues about me}}<br /> {{My references}}</div>

VictorRodriguezDoncel http://ontologydesignpatterns.org/index.php?title=Submissions:LicenseLinkedDataResources&diff=11610 2013-07-18T20:26:14Z

<p>VictorRodriguezDoncel: Imported from OWL file.</p> <hr /> <div>{{Content_OP_Proposal_toolbar}}<br /> {{Graphical representation header}}<br /> {{Graphical representation<br /> |ImageName=licenselinkeddataresources.png<br /> }}<br /> {{Content OP Proposal Template<br /> |SubmittedBy=VictorRodriguezDoncel<br /> |ReusableOWLBuildingBlock=http://purl.oclc.org/NET/lldr/ns#<br /> |Name=LicenseLinkedDataResources<br /> }}<br /> {{Element list header}}<br /> asdf<br /> {{Additional information header}}<br /> <br /> {{Scenarios about me}}<br /> {{Reviews about me}}{{Modeling issues about me}}{{My references}}</div>

VictorRodriguezDoncel http://ontologydesignpatterns.org/index.php?title=File:Licenselinkeddataresources.png&diff=11609 2013-07-18T19:57:56Z

<p>VictorRodriguezDoncel: License Linked Data Resources Pattern</p> <hr /> <div>License Linked Data Resources Pattern</div>

VictorRodriguezDoncel http://ontologydesignpatterns.org/index.php?title=Ontology:Media_Value_Chain_Ontology&diff=6893 2010-02-19T10:54:35Z

<p>VictorRodriguezDoncel: </p> <hr /> <div>{{Ontology<br /> |Name=Media Value Chain Ontology<br /> |OntologyOrganization=MPEG<br /> |OntologyAuthor=ISO/IEC JTC 1/SC 29/WG 11.<br /> |Description=ISO/IEC 21000-19:2010 - Information technology — Multimedia framework (MPEG-21) — Part 19: Media Value Chain Ontology. Final Committee Draft.<br /> |SubmittedBy=VictorRodriguezDoncel<br /> |OntologyPurpose=Represent the value chain of the intellectual property.<br /> |OntologyURI=http://purl.oclc.org/NET/mvco.owl<br /> |LongDescription=ISO/IEC 21000-19:2010, MPEG Media Value Chain Ontology (MVCO) is an ontology formalizing the media value chain within the framework of ISO/IEC 21000.<br /> <br /> ISO/IEC 21000-19:2010 understands a media value chain as the process by which a work is conceived, represented, performed, fixated, distributed, or broadcast, and lastly consumed; acknowledging that different chains exist for different works, going through different transformations, being distributed through different channels and being consumed in different manners. The MVCO captures a base model for those different value chains, focusing on the processes relevant to intellectual property. <br /> <br /> The ontology represents a minimum necessary model common to most markets and jurisdictions reflected in for example, World International Intellectual Property Organization treaties and in regards to any minor differences between different legislations the MVCO is neutral.<br /> <br /> ISO/IEC 21000-19:2010 declares a normative OWL 1.0 ontology RDF/XML syntax to be used by MVCO enabled applications. MVCO enabled applications can derive software modules within the ISO/IEC 21000 framework based on this common model, handling ontology classes and instances, answering advanced queries and making use of the semantic power of the OWL language. MVCO enabled applications can import the MVCO ontology in extended ontologies adapted to the particular needs of the standard user while granting the logical consistency with the core model and facilitating the operation with third party applications.<br /> <br /> ISO/IEC 21000-19:2010 includes the definition of an API to facilitate the implementation of MVCO enabled applications, and provides examples of use in practical scenarios.<br /> |Justification=This ontology may become a reference given its International Standard nature.<br /> |RecommendedBy=http://purl.oclc.org/NET/mvco.owl<br /> |CompetencyQuestion=Who is the rights holder of this intellectual property protected work?<br /> If this is a derived, work... where does it derive from?<br /> Which kind of intellectual property has this object?<br /> Which role plays this person respecting this intellectual property protected object?<br /> |Scenario=Digital Rights Management platforms, Content distribution systems, MPEG-21 middleware<br /> |WebReference=http://www.iso.org/iso/catalogue_detail.htm?csnumber=52887<br /> |OtherReference=http://dmag.ac.upc.edu/ontologies/, http://portal.acm.org/citation.cfm?id=1685140.1685158&amp;coll=portal&amp;dl=ACM<br /> }}</div>

VictorRodriguezDoncel http://ontologydesignpatterns.org/index.php?title=Ontology:Media_Value_Chain_Ontology&diff=6892 2010-02-19T10:52:10Z

<p>VictorRodriguezDoncel: </p> <hr /> <div>{{Ontology<br /> |Name=Media Value Chain Ontology<br /> |OntologyOrganization=MPEG<br /> |OntologyAuthor=ISO/IEC JTC 1/SC 29/WG 11<br /> |Description=ISO/IEC 21000-19:2010 - Information technology — Multimedia framework (MPEG-21) — Part 19: Media Value Chain Ontology. Final Committee Draft.<br /> |SubmittedBy=VictorRodriguezDoncel<br /> |OntologyPurpose=Represent the value chain of the intellectual property.<br /> |OntologyURI=http://purl.oclc.org/NET/mvco.owl<br /> |LongDescription=ISO/IEC 21000-19:2010, MPEG Media Value Chain Ontology (MVCO) is an ontology formalizing the media value chain within the framework of ISO/IEC 21000.<br /> <br /> ISO/IEC 21000-19:2010 understands a media value chain as the process by which a work is conceived, represented, performed, fixated, distributed, or broadcast, and lastly consumed; acknowledging that different chains exist for different works, going through different transformations, being distributed through different channels and being consumed in different manners. The MVCO captures a base model for those different value chains, focusing on the processes relevant to intellectual property. <br /> <br /> The ontology represents a minimum necessary model common to most markets and jurisdictions reflected in for example, World International Intellectual Property Organization treaties and in regards to any minor differences between different legislations the MVCO is neutral.<br /> <br /> ISO/IEC 21000-19:2010 declares a normative OWL 1.0 ontology RDF/XML syntax to be used by MVCO enabled applications. MVCO enabled applications can derive software modules within the ISO/IEC 21000 framework based on this common model, handling ontology classes and instances, answering advanced queries and making use of the semantic power of the OWL language. MVCO enabled applications can import the MVCO ontology in extended ontologies adapted to the particular needs of the standard user while granting the logical consistency with the core model and facilitating the operation with third party applications.<br /> <br /> ISO/IEC 21000-19:2010 includes the definition of an API to facilitate the implementation of MVCO enabled applications, and provides examples of use in practical scenarios.<br /> |Justification=This ontology may become a reference given its International Standard nature.<br /> |RecommendedBy=http://purl.oclc.org/NET/mvco.owl<br /> |CompetencyQuestion=Who is the rights holder of this intellectual property protected work?<br /> If this is a derived, work... where does it derive from?<br /> Which kind of intellectual property has this object?<br /> Which role plays this person respecting this intellectual property protected object?<br /> |Scenario=Digital Rights Management platforms, Content distribution systems, MPEG-21 middleware<br /> |WebReference=http://www.iso.org/iso/catalogue_detail.htm?csnumber=52887<br /> |OtherReference=http://dmag.ac.upc.edu/ontologies/, http://portal.acm.org/citation.cfm?id=1685140.1685158&amp;coll=portal&amp;dl=ACM<br /> }}</div>

VictorRodriguezDoncel http://ontologydesignpatterns.org/index.php?title=Ontology:Media_Value_Chain_Ontology&diff=6891 2010-02-19T10:49:58Z

<p>VictorRodriguezDoncel: First update of this page.</p> <hr /> <div>{{Ontology<br /> |Name=Media Value Chain Ontology<br /> |OntologyOrganization=MPEG<br /> |OntologyAuthor=ISO/IEC JTC 1/SC 29/WG 11<br /> |Description=ISO/IEC 21000-19:2010 - Information technology — Multimedia framework (MPEG-21) — Part 19: Media Value Chain Ontology. Final Committee Draft.<br /> |SubmittedBy=VictorRodriguezDoncel<br /> |OntologyPurpose=Represent the value chain of the intellectual property.<br /> <br /> |OWLImplementation=http://purl.oclc.org/NET/mvco.owl<br /> |LongDescription=ISO/IEC 21000-19:2010, MPEG Media Value Chain Ontology (MVCO) is an ontology formalizing the media value chain within the framework of ISO/IEC 21000.<br /> <br /> ISO/IEC 21000-19:2010 understands a media value chain as the process by which a work is conceived, represented, performed, fixated, distributed, or broadcast, and lastly consumed; acknowledging that different chains exist for different works, going through different transformations, being distributed through different channels and being consumed in different manners. The MVCO captures a base model for those different value chains, focusing on the processes relevant to intellectual property. <br /> <br /> The ontology represents a minimum necessary model common to most markets and jurisdictions reflected in for example, World International Intellectual Property Organization treaties and in regards to any minor differences between different legislations the MVCO is neutral.<br /> <br /> ISO/IEC 21000-19:2010 declares a normative OWL 1.0 ontology RDF/XML syntax to be used by MVCO enabled applications. MVCO enabled applications can derive software modules within the ISO/IEC 21000 framework based on this common model, handling ontology classes and instances, answering advanced queries and making use of the semantic power of the OWL language. MVCO enabled applications can import the MVCO ontology in extended ontologies adapted to the particular needs of the standard user while granting the logical consistency with the core model and facilitating the operation with third party applications.<br /> <br /> ISO/IEC 21000-19:2010 includes the definition of an API to facilitate the implementation of MVCO enabled applications, and provides examples of use in practical scenarios.<br /> <br /> |Justification=This ontology may become a reference given its International Standard nature.<br /> |CompetencyQuestion=Who is the rights holder of this intellectual property protected work?<br /> If this is a derived, work... where does it derive from?<br /> Which kind of intellectual property has this object?<br /> Which role plays this person respecting this intellectual property protected object?<br /> <br /> |Domain=Value chain of the intellectual property<br /> |Scenario=Content distribution system<br /> |WebReference=http://www.iso.org/iso/catalogue_detail.htm?csnumber=52887<br /> |OtherReference=http://dmag.ac.upc.edu/ontologies/, http://portal.acm.org/citation.cfm?id=1685140.1685158&amp;coll=portal&amp;dl=ACM<br /> }}</div>

VictorRodriguezDoncel