http://ontologydesignpatterns.org/api.php?action=feedcontributions&feedformat=atom&user=Pierre-YvesVandenbussche 2026-05-15T11:07:39Z User contributions MediaWiki 1.25.6 http://ontologydesignpatterns.org/index.php?title=File:ConceptGroupPattern.jpg&diff=5892 2009-10-07T19:11:00Z

<p>Pierre-YvesVandenbussche: uploaded a new version of &quot;Image:ConceptGroupPattern.jpg&quot;</p> <hr /> <div>Picture describing concept group pattern.</div>

Pierre-YvesVandenbussche http://ontologydesignpatterns.org/index.php?title=Submissions:ConceptTerms&diff=5834 2009-09-18T09:51:33Z

<p>Pierre-YvesVandenbussche: </p> <hr /> <div>{{Content_OP_Proposal_toolbar}}<br /> {{Include Image<br /> |ImageName=ConceptTermsPattern.jpg<br /> }}<br /> {{Content OP Proposal Template<br /> |SubmittedBy=Pierre-YvesVandenbussche, JeanCharlet<br /> |Name=ConceptTerms<br /> |Intent=This CP allows designers to represent jointly conceptual and linguistic part of a vocabulary. <br /> The pattern purpose is not to encompass all linguistic complexity as Linginfo or LMF does, but to describe linguistic information in more details than SKOS which names concept whith simple labels.<br /> |Domain=Linguistic, Vocabulary,<br /> |CompetencyQuestion=How to distinguish a preferred term or label from synonyms in order to name a concept?, How to enable cross language searching?, How to allow adding properties on term?<br /> |ContentODPDescription=A concept is named in a particular language by a preferred term and a set of simple non preferred terms. Those terms artifacts specialize the term entity which owns common properties. This list of properties may be extended depending on vocabulary specific needs. <br /> This pattern suits for various vocabularies (thesaurus, terminology, taxonomy…) and has been applied to GEMET, Eurovoc, CIM10 among other.<br /> Modeling takes into account:<br /> -the possibility to extend the current pattern in order to add some more precise linguistic information (for instance represent translation relation between two terms since term is a class)<br /> -minimal linguistic artifacts necessary for vocabulary resource access by providing a preferred Term to name a concept and some synonyms which are Simple non preferred terms.<br /> |ReusableOWLBuildingBlock=http://sites.google.com/site/pierreyvesvandenbussche/resources/ConceptTerms.owl<br /> |Consequences=Compare to labels on a concept class, this solution has a higher data load.<br /> |Scenario=Used for vocabulary representation. For example in Eurovoc(http://europa.eu/eurovoc/), a concept has a preferred term &quot;social sciences&quot; in english and a simple non preferred term (i.e. synonyms) &quot;humanities&quot; in the same language whereas the same concept has a preferred term &quot;sciences sociales&quot; in french and a simple non preferred term &quot;sciences humaines&quot; in this language. If we wanted to add a translation relation between terms we could state that &quot;social sciences&quot; english term is a translation of &quot;sciences sociales&quot; french term. If we consider a second preferred term in english &quot;award&quot; which names a concept, in a particular information retrieval context, we could define a coumpound non preferred term &quot;social sciences awards&quot; which is related to preferred terms &quot;social sciences&quot; and &quot;award&quot;.<br /> |CPInstantiationExample=http://sites.google.com/site/pierreyvesvandenbussche/resources/ConceptTermsEurovocExample.owl<br /> |ReengineeredFrom=BS8723-5 model: http://schemas.bs8723.org/Examples.aspx In BS8723 model, triangular-shaped relations are defined between a thesaurus concept, a preferred term and some simple non preferred terms. We are convinced that maintaining this model can be optimized by reifying those relations in a single relation class. That is why we defines the Concept-Terms relation which reusing N-ary pattern in order to represent terms on a concept. Between all terms, we distinguish a preferred term and some synonyms (simple non preferred terms).<br /> }}<br /> {{Element list header}}<br /> {{Takes in account review<br /> |TakesInAccountReview=WimPeters about ConceptTerms<br /> }}<br /> {{Takes in account review<br /> |TakesInAccountReview=VojtechSvatek about ConceptTerms<br /> }}<br /> {{Takes in account review<br /> |TakesInAccountReview=MariCarmenSuarezFigueroa about ConceptTerms<br /> }}<br /> <br /> {{Scenarios about me}}<br /> {{Reviews about me}}<br /> {{Submission to event<br /> |Event=WOP2009<br /> }}</div>

Pierre-YvesVandenbussche http://ontologydesignpatterns.org/index.php?title=File:ConceptTermsPattern.jpg&diff=5833 2009-09-17T16:30:48Z

<p>Pierre-YvesVandenbussche: uploaded a new version of &quot;Image:ConceptTermsPattern.jpg&quot;</p> <hr /> <div></div>

Pierre-YvesVandenbussche http://ontologydesignpatterns.org/index.php?title=Submissions:ConceptTerms&diff=5832 2009-09-17T16:25:25Z

<p>Pierre-YvesVandenbussche: </p> <hr /> <div>{{Content_OP_Proposal_toolbar}}<br /> {{Include Image<br /> |ImageName=ConceptTermsPattern.jpg<br /> }}<br /> {{Content OP Proposal Template<br /> |SubmittedBy=Pierre-YvesVandenbussche, JeanCharlet<br /> |Name=ConceptTerms<br /> |Intent=This CP allows designers to represent both conceptual and linguistic part of a vocabulary. <br /> The pattern purpose is not to encompass all linguistic complexity as Linginfo or LMF does, but to describe linguistic information in more details than SKOS which names concept whith simple labels.<br /> |Domain=Linguistic, Vocabulary,<br /> |CompetencyQuestion=How to distinguish a preferred term or label from synonyms in order to name a concept?, How to enable cross language searching?, How to allow adding properties on term?<br /> |ContentODPDescription=A concept is named in a particular language by a preferred term and a set of simple non preferred terms. Those terms artifacts specialize the term entity which owns common properties. This list of properties may be extended depending on vocabulary specific needs. <br /> This pattern suits for various vocabularies (thesaurus, terminology, taxonomy…) and has been applied to GEMET, Eurovoc, CIM10 among other.<br /> Modeling takes into account:<br /> -the possibility to extend the current pattern in order to add some more precise linguistic information (for instance represent translation relation between two terms since term is a class)<br /> -minimal linguistic artifacts necessary for vocabulary resource access by providing a preferred Term to name a concept and some synonyms which are Simple non preferred terms.<br /> |ReusableOWLBuildingBlock=http://sites.google.com/site/pierreyvesvandenbussche/resources/ConceptTerms.owl<br /> |Consequences=Compare to labels on a concept class, this solution has a higher data load.<br /> |Scenario=Used for vocabulary representation. For example in Eurovoc(http://europa.eu/eurovoc/), a concept has a preferred term &quot;social sciences&quot; in english and a simple non preferred term (i.e. synonyms) &quot;humanities&quot; in the same language whereas the same concept has a preferred term &quot;sciences sociales&quot; in french and a simple non preferred term &quot;sciences humaines&quot; in this language. If we wanted to add a translation relation between terms we could state that &quot;social sciences&quot; english term is a translation of &quot;sciences sociales&quot; french term. If we consider a second preferred term in english &quot;award&quot; which names a concept, in a particular information retrieval context, we could define a coumpound non preferred term &quot;social sciences awards&quot; which is related to preferred terms &quot;social sciences&quot; and &quot;award&quot;.<br /> |CPInstantiationExample=http://sites.google.com/site/pierreyvesvandenbussche/resources/ConceptTermsEurovocExample.owl<br /> |ReengineeredFrom=BS8723-5 model: http://schemas.bs8723.org/Examples.aspx In BS8723 model, triangular-shaped relations are defined between a thesaurus concept, a preferred term and some simple non preferred terms. We are convinced that maintaining this model can be optimized by reifying those relations in a single relation class. That is why we defines the Concept-Terms relation which reusing N-ary pattern in order to represent terms on a concept. Between all terms, we distinguish a preferred term and some synonyms (simple non preferred terms).<br /> }}<br /> {{Element list header}}<br /> {{Takes in account review<br /> |TakesInAccountReview=WimPeters about ConceptTerms<br /> }}<br /> {{Takes in account review<br /> |TakesInAccountReview=VojtechSvatek about ConceptTerms<br /> }}<br /> {{Takes in account review<br /> |TakesInAccountReview=MariCarmenSuarezFigueroa about ConceptTerms<br /> }}<br /> <br /> {{Scenarios about me}}<br /> {{Reviews about me}}<br /> {{Submission to event<br /> |Event=WOP2009<br /> }}</div>

Pierre-YvesVandenbussche http://ontologydesignpatterns.org/index.php?title=Submissions:ConceptTerms&diff=5831 2009-09-17T16:20:56Z

<p>Pierre-YvesVandenbussche: </p> <hr /> <div>{{Content_OP_Proposal_toolbar}}<br /> {{Include Image<br /> |ImageName=ConceptTermsPattern.jpg<br /> }}<br /> {{Content OP Proposal Template<br /> |SubmittedBy=Pierre-YvesVandenbussche, JeanCharlet<br /> |Name=ConceptTerms<br /> |Intent=This CP allows designers to represent both conceptual and linguistic part of a vocabulary. <br /> The pattern purpose is not to encompass all linguistic complexity as Linginfo or LMF does, but to describe linguistic information in more details than SKOS which names concept whith simple labels.<br /> |Domain=Linguistic, Vocabulary,<br /> |CompetencyQuestion=How to distinguish a preferred term or label from synonyms in order to name a concept?, How to enable cross language searching?, How to allow adding properties on term?<br /> |ContentODPDescription=A concept is named in a particular language by a preferred term and a set of simple non preferred terms. Those terms artifacts specialize the term entity which owns common properties. This list of properties may be extended depending on vocabulary specific needs. <br /> This pattern suits for various vocabularies (thesaurus, terminology, taxonomy…) and has been applied to GEMET, Eurovoc, CIM10 among other.<br /> Modeling takes into account:<br /> -the possibility to extend the current pattern in order to add some more precise linguistic information (for instance represent translation relation between two terms since term is a class)<br /> -minimal linguistic artifacts necessary for vocabulary resource access by providing a preferred Term to name a concept and some synonyms which are Simple non preferred terms.<br /> |ReusableOWLBuildingBlock=http://sites.google.com/site/pierreyvesvandenbussche/resources/ConceptTerms.owl<br /> |Consequences=Compare to labels on a concept class, this solution has a higher data load.<br /> |Scenario=Used for vocabulary representation. For example in Eurovoc(http://europa.eu/eurovoc/), a concept has a preferred term &quot;social sciences&quot; in english and a simple non preferred term (i.e. synonyms) &quot;humanities&quot; in the same language whereas the same concept has a preferred term &quot;sciences sociales&quot; in french and a simple non preferred term &quot;sciences humaines&quot; in this language. If we wanted to add a translation relation between terms we could state that &quot;social sciences&quot; english term is a translation of &quot;sciences sociales&quot; french term. If we consider a second preferred term in english &quot;award&quot; which names a concept, in a particular information retrieval context, we could define a coumpound non preferred term &quot;social sciences awards&quot; which is related to preferred terms &quot;social sciences&quot; and &quot;award&quot;.<br /> |ReengineeredFrom=BS8723-5 model: http://schemas.bs8723.org/Examples.aspx In BS8723 model, triangular-shaped relations are defined between a thesaurus concept, a preferred term and some simple non preferred terms. We are convinced that maintaining this model can be optimized by reifying those relations in a single relation class. That is why we defines the Concept-Terms relation which reusing N-ary pattern in order to represent terms on a concept. Between all terms, we distinguish a preferred term and some synonyms (simple non preferred terms).<br /> }}<br /> {{Element list header}}<br /> {{Takes in account review<br /> |TakesInAccountReview=WimPeters about ConceptTerms<br /> }}<br /> {{Takes in account review<br /> |TakesInAccountReview=VojtechSvatek about ConceptTerms<br /> }}<br /> {{Takes in account review<br /> |TakesInAccountReview=MariCarmenSuarezFigueroa about ConceptTerms<br /> }}<br /> <br /> {{Scenarios about me}}<br /> {{Reviews about me}}<br /> {{Submission to event<br /> |Event=WOP2009<br /> }}</div>

Pierre-YvesVandenbussche http://ontologydesignpatterns.org/index.php?title=Submissions:ConceptTerms&diff=5830 2009-09-17T16:16:50Z

<p>Pierre-YvesVandenbussche: </p> <hr /> <div>{{Content_OP_Proposal_toolbar}}<br /> {{Include Image<br /> |ImageName=ConceptTermsPattern.jpg<br /> }}<br /> {{Content OP Proposal Template<br /> |SubmittedBy=Pierre-YvesVandenbussche, JeanCharlet<br /> |Name=ConceptTerms<br /> |Intent=This CP allows designers to represent both conceptual and linguistic part of a vocabulary. <br /> The pattern purpose is not to encompass all linguistic complexity as Linginfo or LMF does, but to describe linguistic information in more details than simple labels on a concept as SKOS does.<br /> |Domain=Linguistic, Vocabulary,<br /> |CompetencyQuestion=How to distinguish a preferred term or label from synonyms in order to name a concept?, How to enable cross language searching?, How to allow adding properties on term?<br /> |ContentODPDescription=A concept is named in a particular language by a preferred term and a set of simple non preferred terms. Those terms artifacts specialize the term entity which owns common properties. This list of properties may be extended depending on vocabulary specific needs. <br /> This pattern suits for various vocabularies (thesaurus, terminology, taxonomy…) and has been applied to GEMET, Eurovoc, CIM10 among other.<br /> Modeling takes into account:<br /> -the possibility to extend the current pattern in order to add some more precise linguistic information (for instance represent translation relation between two terms since term is a class)<br /> -minimal linguistic artifacts necessary for vocabulary resource access by providing a preferred Term to name a concept and some synonyms which are Simple non preferred terms.<br /> |ReusableOWLBuildingBlock=http://sites.google.com/site/pierreyvesvandenbussche/resources/ConceptTerms.owl<br /> |Consequences=Compare to labels on a concept class, this solution has a higher data load.<br /> |Scenario=Used for vocabulary representation. For example in Eurovoc(http://europa.eu/eurovoc/), a concept has a preferred term &quot;social sciences&quot; in english and a simple non preferred term (i.e. synonyms) &quot;humanities&quot; in the same language whereas the same concept has a preferred term &quot;sciences sociales&quot; in french and a simple non preferred term &quot;sciences humaines&quot; in this language. If we wanted to add a translation relation between terms we could state that &quot;social sciences&quot; english term is a translation of &quot;sciences sociales&quot; french term. If we consider a second preferred term in english &quot;award&quot; which names a concept, in a particular information retrieval context, we could define a coumpound non preferred term &quot;social sciences awards&quot; which is related to preferred terms &quot;social sciences&quot; and &quot;award&quot;.<br /> |ReengineeredFrom=BS8723-5 model: http://schemas.bs8723.org/Examples.aspx In BS8723 model, triangular-shaped relations are defined between a thesaurus concept, a preferred term and some simple non preferred terms. We are convinced that maintaining this model can be optimized by reifying those relations in a single relation class. That is why we defines the Concept-Terms relation which reusing N-ary pattern in order to represent terms on a concept. Between all terms, we distinguish a preferred term and some synonyms (simple non preferred terms).<br /> }}<br /> {{Element list header}}<br /> {{Takes in account review<br /> |TakesInAccountReview=WimPeters about ConceptTerms<br /> }}<br /> {{Takes in account review<br /> |TakesInAccountReview=VojtechSvatek about ConceptTerms<br /> }}<br /> {{Takes in account review<br /> |TakesInAccountReview=MariCarmenSuarezFigueroa about ConceptTerms<br /> }}<br /> <br /> {{Scenarios about me}}<br /> {{Reviews about me}}<br /> {{Submission to event<br /> |Event=WOP2009<br /> }}</div>

Pierre-YvesVandenbussche http://ontologydesignpatterns.org/index.php?title=File:ConceptTermsEurovocExample.jpg&diff=5829 2009-09-17T16:13:27Z

<p>Pierre-YvesVandenbussche: uploaded a new version of &quot;Image:ConceptTermsEurovocExample.jpg&quot;</p> <hr /> <div></div>

Pierre-YvesVandenbussche http://ontologydesignpatterns.org/index.php?title=Submissions:ConceptTerms/Scenario_1&diff=5828 2009-09-17T15:53:11Z

<p>Pierre-YvesVandenbussche: </p> <hr /> <div>{{Scenario Template<br /> |Description=This ontology contains an example ABox for the ConceptTerms CP available at http://sites.google.com/site/pierreyvesvandenbussche/resources/ConceptTerms.owl<br /> This ontology describes example coming from Eurovoc(http://europa.eu/eurovoc/) where a concept has a preferred term &quot;social sciences&quot; in english and a simple non preferred term (i.e. synonyms) &quot;humanities&quot; in the same language whereas the same concept has a preferred term &quot;sciences sociales&quot; in french and a simple non preferred term &quot;sciences humaines&quot; in this language. We consider a second preferred term in english &quot;award&quot; which names a concept. In this particular information retrieval context, we define a coumpound non preferred term &quot;social sciences awards&quot; which is related to preferred terms &quot;social sciences&quot; and &quot;award&quot;.<br /> |Image=ConceptTermsEurovocExample.jpg<br /> |OWLFile=http://sites.google.com/site/pierreyvesvandenbussche/resources/ConceptTermsEurovocExample.owl<br /> |ScenarioOf=Submissions:ConceptTerms<br /> }}</div>

Pierre-YvesVandenbussche http://ontologydesignpatterns.org/index.php?title=Submissions:ConceptTerms/Scenario_1&diff=5827 2009-09-17T15:51:30Z

<p>Pierre-YvesVandenbussche: creation</p> <hr /> <div>{{Scenario Template<br /> |Description=This ontology contains an example ABox for the ConceptTerms CP available at http://sites.google.com/site/pierreyvesvandenbussche/resources/ConceptTerms.owl<br /> This ontology describes example providing from Eurovoc(http://europa.eu/eurovoc/) where a concept has a preferred term &quot;social sciences&quot; in english and a simple non preferred term (i.e. synonyms) &quot;humanities&quot; in the same language whereas the same concept has a preferred term &quot;sciences sociales&quot; in french and a simple non preferred term &quot;sciences humaines&quot; in this language. We consider a second preferred term in english &quot;award&quot; which names a concept. In this particular information retrieval context, we define a coumpound non preferred term &quot;social sciences awards&quot; which is related to preferred terms &quot;social sciences&quot; and &quot;award&quot;.<br /> |Image=ConceptTermsEurovocExample.jpg<br /> |OWLFile=http://sites.google.com/site/pierreyvesvandenbussche/resources/ConceptTermsEurovocExample.owl<br /> |ScenarioOf=Submissions:ConceptTerms<br /> }}</div>

Pierre-YvesVandenbussche http://ontologydesignpatterns.org/index.php?title=File:ConceptTermsEurovocExample.jpg&diff=5826 2009-09-17T15:49:59Z

<p>Pierre-YvesVandenbussche: </p> <hr /> <div></div>

Pierre-YvesVandenbussche http://ontologydesignpatterns.org/index.php?title=Submissions:ConceptTerms&diff=5825 2009-09-17T15:12:10Z

<p>Pierre-YvesVandenbussche: Reviews corrections</p> <hr /> <div>{{Content_OP_Proposal_toolbar}}<br /> {{Include Image<br /> |ImageName=ConceptTermsPattern.jpg<br /> }}<br /> {{Content OP Proposal Template<br /> |SubmittedBy=Pierre-YvesVandenbussche, JeanCharlet<br /> |Name=ConceptTerms<br /> |Intent=This CP allows designers to represent both conceptual and linguistic part of a vocabulary. <br /> The pattern purpose is not to encompass all linguistic complexity as Linginfo(http://olp.dfki.de/LingInfo/index.php) or LMF(http://www.lexicalmarkupframework.org/) does, but to describe linguistic information in more details than simple labels on a concept as SKOS does. This pattern suits for various vocabularies (thesaurus, terminology, taxonomy…) and has been applied to GEMET, Eurovoc, CIM10 among other.<br /> Modeling takes into account:<br /> -the possibility to extend the current pattern in order to add some more precise linguistic information (for instance represent translation relation between two terms since term is a class)<br /> -minimal linguistic artifacts necessary for vocabulary resource access by providing a preferred Term to name a concept and some synonyms which are Simple non preferred terms.<br /> |Domain=Linguistic, Vocabulary,<br /> |CompetencyQuestion=How to distinguish a preferred term or label from synonyms in order to name a concept?, How to enable cross language searching?, How to allow adding properties on term?<br /> |ContentODPDescription=A concept is named in a particular language by a preferred term and a set of simple non preferred terms. Those terms artifacts specialize the term entity which owns common properties for terms such as: language, source information (when creating vocabulary from corpora). This list of properties may be extended depending on vocabulary specific needs.<br /> |ReusableOWLBuildingBlock=http://sites.google.com/site/pierreyvesvandenbussche/resources/ConceptTerms.owl<br /> |Consequences=Compare to labels on a concept class, this solution has a higher data load.<br /> |Scenario=Used for vocabulary representation. For example in Eurovoc(http://europa.eu/eurovoc/), a concept has a preferred term &quot;social sciences&quot; in english and a simple non preferred term (i.e. synonyms) &quot;humanities&quot; in the same language whereas the same concept has a preferred term &quot;sciences sociales&quot; in french and a simple non preferred term &quot;sciences humaines&quot; in this language. If we wanted to add a translation relation between terms we could state that &quot;social sciences&quot; english term is a translation of &quot;sciences sociales&quot; french term. If we consider a second preferred term in english &quot;award&quot; which names a concept, in a particular information retrieval context, we could define a coumpound non preferred term &quot;social sciences awards&quot; which is related to preferred terms &quot;social sciences&quot; and &quot;award&quot;.<br /> |ReengineeredFrom=BS8723-5 model: http://schemas.bs8723.org/Examples.aspx In BS8723 model, triangular-shaped relations are defined between a thesaurus concept, a preferred term and some simple non preferred terms. We are convinced that maintaining this model can be optimized by reifying those relations in a single relation class. That is why we defines the Concept-Terms relation which reusing N-ary pattern in order to represent terms on a concept. Between all terms, we distinguish a preferred term and some synonyms (simple non preferred terms).<br /> }}<br /> {{Element list header}}<br /> {{Takes in account review<br /> |TakesInAccountReview=WimPeters about ConceptTerms<br /> }}<br /> {{Takes in account review<br /> |TakesInAccountReview=VojtechSvatek about ConceptTerms<br /> }}<br /> {{Takes in account review<br /> |TakesInAccountReview=MariCarmenSuarezFigueroa about ConceptTerms<br /> }}<br /> <br /> {{Scenarios about me}}<br /> {{Reviews about me}}<br /> {{Submission to event<br /> |Event=WOP2009<br /> }}</div>

Pierre-YvesVandenbussche http://ontologydesignpatterns.org/index.php?title=Submissions_talk:CollectionEntity/Scenario_1&diff=5820 2009-09-15T15:43:43Z

<p>Pierre-YvesVandenbussche: New page: There is a mistake in OWL example file: http://www.ontologydesignpatterns.org/cp/owl/collectiveentity.owl is not a valid owl:imports URL should be: http://ontologydesignpatterns.org/cp/ow...</p> <hr /> <div>There is a mistake in OWL example file:<br /> http://www.ontologydesignpatterns.org/cp/owl/collectiveentity.owl is not a valid owl:imports URL <br /> should be:<br /> http://ontologydesignpatterns.org/cp/owl/collectionentity.owl</div>

Pierre-YvesVandenbussche http://ontologydesignpatterns.org/index.php?title=Submissions:ConceptGroup&diff=5518 2009-08-16T10:21:09Z

<p>Pierre-YvesVandenbussche: </p> <hr /> <div>{{Content_OP_Proposal_toolbar}}<br /> {{Include Image<br /> |ImageName=ConceptGroupPattern.jpg<br /> }}<br /> {{Content OP Proposal Template<br /> |SubmittedBy=Pierre-YvesVandenbussche<br /> |Name=ConceptGroup<br /> |Intent=This CP allows designers to represent concept group defined by intention (all concepts satisfying group membership condition) or by extension (all concepts referring a group).<br /> |Domain=Parts and Collections, Vocabulary,<br /> |ContentODPDescription=How a group entity stands alone?, How to represent either a vocabulary subset, a cross vocabulary subset or a whole vocabulary?, How to represent group concept members?<br /> |ReusableOWLBuildingBlock=http://sites.google.com/site/pierreyvesvandenbussche/resources/ConceptGroup.owl<br /> |Scenario=Used to describe whole vocabulary entity or vocabulary concepts subset. Compliant with RefSets in SNOMED-CT or themes in GEMET.<br /> |ReengineeredFrom=SNOMED-CT Reference Sets specification: http://www.ihtsdo.org/fileadmin/user_upload/Docs_01/Technical_Docs/reference_sets.pdf<br /> }}<br /> {{Element list header}}<br /> <br /> {{Scenarios about me}}<br /> {{Reviews about me}}<br /> {{Submission to event<br /> |Event=WOP2009:Main<br /> }}</div>

Pierre-YvesVandenbussche http://ontologydesignpatterns.org/index.php?title=Submissions:ConceptGroup&diff=5517 2009-08-16T10:20:05Z

<p>Pierre-YvesVandenbussche: </p> <hr /> <div>{{Content_OP_Proposal_toolbar}}<br /> {{Include Image<br /> |ImageName=ConceptGroupPattern<br /> }}<br /> {{Content OP Proposal Template<br /> |SubmittedBy=Pierre-YvesVandenbussche<br /> |Name=ConceptGroup<br /> |Intent=This CP allows designers to represent concept group defined by intention (all concepts satisfying group membership condition) or by extension (all concepts referring a group).<br /> |Domain=Parts and Collections, Vocabulary, <br /> |ContentODPDescription=How a group entity stands alone?, How to represent either a vocabulary subset, a cross vocabulary subset or a whole vocabulary?, How to represent group concept members?<br /> |ReusableOWLBuildingBlock=http://sites.google.com/site/pierreyvesvandenbussche/resources/ConceptGroup.owl<br /> |Scenario=Used to describe whole vocabulary entity or vocabulary concepts subset. Compliant with RefSets in SNOMED-CT or themes in GEMET.<br /> |ReengineeredFrom=SNOMED-CT Reference Sets specification: http://www.ihtsdo.org/fileadmin/user_upload/Docs_01/Technical_Docs/reference_sets.pdf<br /> }}<br /> {{Element list header}}<br /> <br /> {{Scenarios about me}}<br /> {{Reviews about me}}</div>

Pierre-YvesVandenbussche http://ontologydesignpatterns.org/index.php?title=Submissions:ConceptGroup&diff=5516 2009-08-16T10:18:21Z

<p>Pierre-YvesVandenbussche: Imported from OWL file.</p> <hr /> <div>{{Content_OP_Proposal_toolbar}}<br /> {{Include Image<br /> |ImageName=<br /> }}<br /> {{Content OP Proposal Template<br /> |SubmittedBy=Pierre-YvesVandenbussche<br /> |ReusableOWLBuildingBlock=http://sites.google.com/site/pierreyvesvandenbussche/resources/ConceptGroup.owl<br /> |Name=ConceptGroup<br /> }}<br /> {{Element list header}}<br /> <br /> {{Scenarios about me}}<br /> {{Reviews about me}}</div>

Pierre-YvesVandenbussche http://ontologydesignpatterns.org/index.php?title=Submissions:ConceptTerms&diff=5515 2009-08-16T09:11:11Z

<p>Pierre-YvesVandenbussche: </p> <hr /> <div>{{Content_OP_Proposal_toolbar}}<br /> {{Include Image<br /> |ImageName=ConceptTermsPattern.jpg<br /> }}<br /> {{Content OP Proposal Template<br /> |SubmittedBy=Pierre-YvesVandenbussche<br /> |Name=ConceptTerms<br /> |Intent=This CP allows designers to represent language complexity for concept description (preferred term, synonyms, translation relation,etc.).<br /> |Domain=Linguistic, Vocabulary,<br /> |CompetencyQuestion=How to distinguish a preferred term or label from synonyms in order to name a concept?, How to enable cross language searching?, How to allow adding properties on term?<br /> |ContentODPDescription=A concept is named in a particular language by a preferred term and a set of simple non preferred terms. Those terms artifacts specialize the term entity which owns common properties for terms such as: language, source information (when creating vocabulary from corpora). This list of properties may be extended depending on vocabulary specific needs.<br /> |ReusableOWLBuildingBlock=http://sites.google.com/site/pierreyvesvandenbussche/resources/ConceptTerms.owl<br /> |Consequences=Compare to labels on a concept class, this solution has a higher data load.<br /> |Scenario=Used for terminology representation. For example, a preferred term &quot;car&quot; in english could be translated in &quot;voiture&quot; in french and linked to the same concept. Here translation relation is possible thanks to the term entity.<br /> |ReengineeredFrom=BS8723-5 model: http://schemas.bs8723.org/<br /> }}<br /> {{Element list header}}<br /> <br /> {{Scenarios about me}}<br /> {{Reviews about me}}<br /> {{Submission to event<br /> |Event=WOP2009<br /> }}</div>

Pierre-YvesVandenbussche http://ontologydesignpatterns.org/index.php?title=Submissions:ConceptTerms&diff=5514 2009-08-16T09:09:10Z

<p>Pierre-YvesVandenbussche: </p> <hr /> <div>{{Content_OP_Proposal_toolbar}}<br /> {{Include Image<br /> |ImageName=ConceptTermsPattern.jpg<br /> }}<br /> {{Content OP Proposal Template<br /> |SubmittedBy=Pierre-YvesVandenbussche<br /> |Name=ConceptTerms<br /> |Intent=This CP allows designers to represent language complexity for concept description (preferred term, synonyms...). For instance, synonyms (simple non preferred terms) give various possibilities to access a resource; translation relation between terms enables multilingual vocabularies searches and therefore broaden results.<br /> |Domain=Linguistic, Vocabulary, <br /> |CompetencyQuestion=How to distinguish a preferred term or label from synonyms in order to name a concept?, How to enable cross language searching?, How to allow adding properties on term?<br /> |ContentODPDescription=A concept is named in a particular language by a preferred term and a set of simple non preferred terms. Those terms artifacts specialize the term entity which owns common properties for terms such as: language, source information (when creating vocabulary from corpora). This list of properties may be extended depending on vocabulary specific needs.<br /> |ReusableOWLBuildingBlock=http://sites.google.com/site/pierreyvesvandenbussche/resources/ConceptTerms.owl<br /> |Consequences=Compare to labels on a concept class, this solution has a higher data load.<br /> |Scenario=Used for terminology representation. For example, a preferred term &quot;car&quot; in english could be translated in &quot;voiture&quot; in french and linked to the same concept. Here translation relation is possible thanks to the term entity.<br /> |ReengineeredFrom=BS8723-5 model: http://schemas.bs8723.org/<br /> }}<br /> {{Element list header}}<br /> <br /> {{Scenarios about me}}<br /> {{Reviews about me}}<br /> {{Submission to event<br /> |Event=WOP2009<br /> }}</div>

Pierre-YvesVandenbussche http://ontologydesignpatterns.org/index.php?title=Submissions:ConceptTerms&diff=5513 2009-08-16T09:07:30Z

<p>Pierre-YvesVandenbussche: </p> <hr /> <div>{{Content_OP_Proposal_toolbar}}<br /> {{Include Image<br /> |ImageName=ConceptTermsPattern.jpg<br /> }}<br /> {{Content OP Proposal Template<br /> |SubmittedBy=Pierre-YvesVandenbussche<br /> |Name=ConceptTerms<br /> |Intent=This CP allows designers to represent language complexity for concept description (preferred term, synonyms...). For instance, synonyms (simple non preferred terms) give various possibilities to access a resource; translation relation between terms enables multilingual vocabularies searches and therefore broaden results.<br /> |CompetencyQuestion=How to distinguish a preferred term or label from synonyms in order to name a concept?, How to enable cross language searching?, How to allow adding properties on term?<br /> |ContentODPDescription=A concept is named in a particular language by a preferred term and a set of simple non preferred terms. Those terms artifacts specialize the term entity which owns common properties for terms such as: language, source information (when creating vocabulary from corpora). This list of properties may be extended depending on vocabulary specific needs.<br /> |ReusableOWLBuildingBlock=http://sites.google.com/site/pierreyvesvandenbussche/resources/ConceptTerms.owl<br /> |Consequences=Compare to labels on a concept class, this solution has a higher data load.<br /> |Scenario=Used for terminology representation. For example, a preferred term &quot;car&quot; in english could be translated in &quot;voiture&quot; in french and linked to the same concept. Here translation relation is possible thanks to the term entity.<br /> |ReengineeredFrom=BS8723-5 model: http://schemas.bs8723.org/<br /> }}<br /> {{Element list header}}<br /> <br /> {{Scenarios about me}}<br /> {{Reviews about me}}<br /> {{Submission to event<br /> |Event=WOP2009<br /> }}</div>

Pierre-YvesVandenbussche http://ontologydesignpatterns.org/index.php?title=Submissions:ConceptTerms&diff=5512 2009-08-16T09:06:43Z

<p>Pierre-YvesVandenbussche: </p> <hr /> <div>{{Content_OP_Proposal_toolbar}}<br /> {{Include Image<br /> |ImageName=ConceptTermsPattern.jpg<br /> }}<br /> {{Content OP Proposal Template<br /> |SubmittedBy=Pierre-YvesVandenbussche<br /> |Name=ConceptTerms<br /> |Intent=This CP allows designers to represent language complexity for concept description (preferred term, synonyms...). For instance, synonyms (simple non preferred terms) give various possibilities to access a resource; translation relation between terms enables multilingual vocabularies searches and therefore broaden results.<br /> |CompetencyQuestion=How to distinguish a preferred term or label from synonyms in order to name a concept?, How to enable cross language searching?, How to allow adding properties on term?<br /> |ContentODPDescription=A concept is named in a particular language by a preferred term and a set of simple non preferred terms. Those terms artifacts specialize the term entity which owns common properties for terms such as: language, source information (when creating vocabulary from corpora). This list of properties may be extended depending on vocabulary specific needs.<br /> |ReusableOWLBuildingBlock=http://sites.google.com/site/pierreyvesvandenbussche/resources/ConceptTerms.owl?attredirects=0<br /> |Consequences=Compare to labels on a concept class, this solution has a higher data load.<br /> |Scenario=Used for terminology representation. For example, a preferred term &quot;car&quot; in english could be translated in &quot;voiture&quot; in french and linked to the same concept. Here translation relation is possible thanks to the term entity.<br /> |ReengineeredFrom=BS8723-5 model: http://schemas.bs8723.org/<br /> }}<br /> {{Element list header}}<br /> <br /> {{Scenarios about me}}<br /> {{Reviews about me}}<br /> {{Submission to event<br /> |Event=WOP2009<br /> }}</div>

Pierre-YvesVandenbussche http://ontologydesignpatterns.org/index.php?title=Submissions:ConceptTerms&diff=5511 2009-08-16T09:06:04Z

<p>Pierre-YvesVandenbussche: </p> <hr /> <div>{{Content_OP_Proposal_toolbar}}<br /> {{Include Image<br /> |ImageName=ConceptTermsPattern.jpg<br /> }}<br /> {{Content OP Proposal Template<br /> |SubmittedBy=Pierre-YvesVandenbussche<br /> |Name=ConceptTerms<br /> |Intent=This CP allows designers to represent language complexity for concept description (preferred term, synonyms...). For instance, synonyms (simple non preferred terms) give various possibilities to access a resource; translation relation between terms enables multilingual vocabularies searches and therefore broaden results.<br /> |CompetencyQuestion=How to distinguish a preferred term or label from synonyms in order to name a concept?, How to enable cross language searching?, How to allow adding properties on term?<br /> |ContentODPDescription=A concept is named in a particular language by a preferred term and a set of simple non preferred terms. Those terms artifacts specialize the term entity which owns common properties for terms such as: language, source information (when creating vocabulary from corpora). This list of properties may be extended depending on vocabulary specific needs.<br /> |ReusableOWLBuildingBlock=http://sites.google.com/site/pierreyvesvandenbussche/resources/ConceptTerms.owl?attredirects=0<br /> |Consequences=Compare to labels on a concept class, this solution has a higher data load.<br /> |CPInstantiationExample=Used for terminology representation. For example, a preferred term &quot;car&quot; in english could be translated in &quot;voiture&quot; in french and linked to the same concept. Here translation relation is possible thanks to the term entity.<br /> |ReengineeredFrom=BS8723-5 model: http://schemas.bs8723.org/<br /> }}<br /> {{Element list header}}<br /> <br /> {{Scenarios about me}}<br /> {{Reviews about me}}<br /> {{Submission to event<br /> |Event=WOP2009<br /> }}</div>

Pierre-YvesVandenbussche http://ontologydesignpatterns.org/index.php?title=File:ConceptTermsPattern.jpg&diff=5510 2009-08-16T09:04:05Z

<p>Pierre-YvesVandenbussche: </p> <hr /> <div></div>

Pierre-YvesVandenbussche http://ontologydesignpatterns.org/index.php?title=Submissions:ConceptTerms&diff=5509 2009-08-16T08:58:16Z

<p>Pierre-YvesVandenbussche: Imported from OWL file.</p> <hr /> <div>{{Content_OP_Proposal_toolbar}}<br /> {{Include Image<br /> |ImageName=<br /> }}<br /> {{Content OP Proposal Template<br /> |SubmittedBy=Pierre-YvesVandenbussche<br /> |ReusableOWLBuildingBlock=http://sites.google.com/site/pierreyvesvandenbussche/resources/ConceptTerms.owl?attredirects=0<br /> |Name=ConceptTerms<br /> }}<br /> {{Element list header}}<br /> <br /> {{Scenarios about me}}<br /> {{Reviews about me}}</div>

Pierre-YvesVandenbussche http://ontologydesignpatterns.org/index.php?title=Community:Linguistic&diff=5506 2009-08-16T07:27:39Z

<p>Pierre-YvesVandenbussche: New page: {{Domain Template |Name=Linguistic |Description=The lingistic representation: language complexity, synonyms, translation relations... }} {{List of CPs of this domain}} {{List of Modeling i...</p> <hr /> <div>{{Domain Template<br /> |Name=Linguistic<br /> |Description=The lingistic representation: language complexity, synonyms, translation relations...<br /> }}<br /> {{List of CPs of this domain}}<br /> {{List of Modeling issues related to this domain}}</div>

Pierre-YvesVandenbussche http://ontologydesignpatterns.org/index.php?title=Community:Vocabulary&diff=5505 2009-08-16T07:23:41Z

<p>Pierre-YvesVandenbussche: New page: {{Domain Template |Name=Vocabulary |Description=There is a wide range of knowledge representation structures such as controlled list, classification, thesauri, terminology, etc. ‘vocabul...</p> <hr /> <div>{{Domain Template<br /> |Name=Vocabulary<br /> |Description=There is a wide range of knowledge representation structures such as controlled list, classification, thesauri, terminology, etc. ‘vocabulary’ is the general term used to refer to those knowledge representations.<br /> }}<br /> {{List of CPs of this domain}}<br /> {{List of Modeling issues related to this domain}}</div>

Pierre-YvesVandenbussche http://ontologydesignpatterns.org/index.php?title=File:ConceptGroupPattern.jpg&diff=5471 2009-08-14T14:12:09Z

<p>Pierre-YvesVandenbussche: Picture describing concept group pattern.</p> <hr /> <div>Picture describing concept group pattern.</div>

Pierre-YvesVandenbussche