UCI - Revision history

imported>Martins at 14:07, 20 September 2012

2012-09-20T14:07:12Z

← Older revision		Revision as of 14:07, 20 September 2012
Line 39:		Line 39:
	UCL and UCN are both UCI's (i.e., uniform concept identifiers). They are both used to identify UW's. The difference is that UCL is an address to the position of the UW in the [[UNL Knowledge Base]], whereas the UCN is only the name of the UW. The same address (i.e., UCL) may be associated to different UCN's, but a single UCN may not have more than one UCL. A UCL always describe an available UW, i.e., a UW that has been already defined in the UNL KB, whereas a UCN is not necessarily linked to an address. In that sense, UCL's are more "official" than UCN's, which are normally used in order to preserve the readability of the UNL code.		UCL and UCN are both UCI's (i.e., uniform concept identifiers). They are both used to identify UW's. The difference is that UCL is an address to the position of the UW in the [[UNL Knowledge Base]], whereas the UCN is only the name of the UW. The same address (i.e., UCL) may be associated to different UCN's, but a single UCN may not have more than one UCL. A UCL always describe an available UW, i.e., a UW that has been already defined in the UNL KB, whereas a UCN is not necessarily linked to an address. In that sense, UCL's are more "official" than UCN's, which are normally used in order to preserve the readability of the UNL code.

			== Simplified Notation ==
	In the [[UNL document\|UNL Document Structure]], UCI's are always abbreviated to the last part, because the scheme, the authority and the namespace may be inferred from the document header. For instance:		In the [[UNL document\|UNL Document Structure]], UCI's are always abbreviated to the last part, because the scheme, the authority and the namespace may be inferred from the document header. For instance:
	*104379964 instead of ucl://unlkb.unlweb.net.br/104379964		*104379964 instead of ucl://unlkb.unlweb.net.br/104379964

imported>Martins at 14:06, 20 September 2012

2012-09-20T14:06:41Z

← Older revision		Revision as of 14:06, 20 September 2012
Line 37:		Line 37:

	== UCL or UCN? ==		== UCL or UCN? ==
	UCL and UCN are both UCI's (i.e., uniform concept identifiers). They are both used to identify UW's. The difference is that UCL is an address to the position of the UW in the [[UNL Knowledge Base]], whereas the UCN is only the name of the UW. The same address (i.e., UCL) may be associated to different UCN's, but a single UCN may not have more than one UCL. A UCL always describe an available UW, i.e., a UW that has been already defined in the UNL KB, ~~where~~ a UCN ~~does~~ not ~~have~~ necessarily an address.		UCL and UCN are both UCI's (i.e., uniform concept identifiers). They are both used to identify UW's. The difference is that UCL is an address to the position of the UW in the [[UNL Knowledge Base]], whereas the UCN is only the name of the UW. The same address (i.e., UCL) may be associated to different UCN's, but a single UCN may not have more than one UCL. A UCL always describe an available UW, i.e., a UW that has been already defined in the UNL KB, whereas a UCN is not necessarily linked to an address. In that sense, UCL's are more "official" than UCN's, which are normally used in order to preserve the readability of the UNL code.

	In the [[UNL document\|UNL Document Structure]], UCI's are always abbreviated to the last part, because the scheme, the authority and the namespace may be inferred from the document header. For instance:		In the [[UNL document\|UNL Document Structure]], UCI's are always abbreviated to the last part, because the scheme, the authority and the namespace may be inferred from the document header. For instance:

imported>Martins at 20:31, 19 September 2012

2012-09-19T20:31:32Z

← Older revision		Revision as of 20:31, 19 September 2012
Line 53:		Line 53:
	<nowiki><NSS> ::= <root>[<suffix>]</nowiki>		<nowiki><NSS> ::= <root>[<suffix>]</nowiki>
	<nowiki><root> ::= <UTF-8 character>+</nowiki>		<nowiki><root> ::= <UTF-8 character>+</nowiki>
	<nowiki><suffix> ::= “(~~“ <suffix> [ “,” <suffix> ]… “)” \|~~ <relation> { “>” , “<” } <root></nowiki>		<nowiki><suffix> ::= "("<relation>{">","<"}<root>")"</nowiki>
	<nowiki><relation> ::= {~~“agt”~~, "and", "aoj", ...}</nowiki>		<nowiki><relation> ::= {"agt","and","aoj",...}</nowiki>
	where:<br>		where:<br>
	+ to be repeated 1 or more times<br >		+ to be repeated 1 or more times<br >

imported>Martins at 20:29, 19 September 2012

2012-09-19T20:29:26Z

← Older revision		Revision as of 20:29, 19 September 2012
Line 46:		Line 46:

	<nowiki><UCI> ::= <UCL>\|<UCN></nowiki>		<nowiki><UCI> ::= <UCL>\|<UCN></nowiki>

	<nowiki><UCL> ::= "ucl://"<AUTHORITY>"/"<PATH></nowiki>		<nowiki><UCL> ::= "ucl://"<AUTHORITY>"/"<PATH></nowiki>
	<nowiki><AUTHORITY> ::= <UTF-8 character>+</nowiki>		<nowiki><AUTHORITY> ::= <UTF-8 character>+</nowiki>
	<nowiki><ID> ::= [0123456789]+</nowiki>		<nowiki><ID> ::= [0123456789]+</nowiki>

	<nowiki><UCN> ::= "ucn://"<LID>":"<NSS></nowiki>		<nowiki><UCN> ::= "ucn://"<LID>":"<NSS></nowiki>
	<nowiki><LID> ::= [a-z]{3}</nowiki>		<nowiki><LID> ::= [a-z]{3}</nowiki>

imported>Martins at 20:28, 19 September 2012

2012-09-19T20:28:49Z

← Older revision		Revision as of 20:28, 19 September 2012
Line 9:		Line 9:
	**ucn, which is used for uniform concept names		**ucn, which is used for uniform concept names
	*<hierarchical part> holds the identification information.		*<hierarchical part> holds the identification information.



	== UCL (Uniform Concept Locator) ==		== UCL (Uniform Concept Locator) ==
Line 37:		Line 35:
	ucn:rus:стол(icl>мебель)		ucn:rus:стол(icl>мебель)
	UCN's must be unique and the namespace-specific string is normally split into two different parts: a root and a suffix, as exemplified above. The root can be a word or a multi-word expression. The suffix, which is always introduced by a UNL relation, is used to disambiguate the root.		UCN's must be unique and the namespace-specific string is normally split into two different parts: a root and a suffix, as exemplified above. The root can be a word or a multi-word expression. The suffix, which is always introduced by a UNL relation, is used to disambiguate the root.

			== UCL or UCN? ==
			UCL and UCN are both UCI's (i.e., uniform concept identifiers). They are both used to identify UW's. The difference is that UCL is an address to the position of the UW in the [[UNL Knowledge Base]], whereas the UCN is only the name of the UW. The same address (i.e., UCL) may be associated to different UCN's, but a single UCN may not have more than one UCL. A UCL always describe an available UW, i.e., a UW that has been already defined in the UNL KB, where a UCN does not have necessarily an address.

			In the [[UNL document\|UNL Document Structure]], UCI's are always abbreviated to the last part, because the scheme, the authority and the namespace may be inferred from the document header. For instance:
			*104379964 instead of ucl://unlkb.unlweb.net.br/104379964
			*table(icl>furniture) instead of ucn:eng:table(icl>furniture)

	== Formal Syntax ==		== Formal Syntax ==

	<nowiki><UCI> ::= <UCL>\|<UCN>		<nowiki><UCI> ::= <UCL>\|<UCN></nowiki>

	<nowiki><UCL> ::= "ucl://"<AUTHORITY>"/"<PATH>		<nowiki><UCL> ::= "ucl://"<AUTHORITY>"/"<PATH></nowiki>
	<nowiki><AUTHORITY> ::= <UTF-8 character>+</nowiki>		<nowiki><AUTHORITY> ::= <UTF-8 character>+</nowiki>
	<nowiki><ID> ::= [0123456789]+</nowiki>		<nowiki><ID> ::= [0123456789]+</nowiki>
Line 61:		Line 66:
	{ } alternative element<br >		{ } alternative element<br >
	... to be repeated more than 0 times<br >		... to be repeated more than 0 times<br >

	~~== UCL or UCN? ==~~
	UCL and UCN are both UCI's (i.e., uniform concept identifiers). They are both used to identify UW's. The difference is that UCL is an address to the position of the UW in the [[UNL Knowledge Base]], whereas the UCN is only the name of the UW. The same address (i.e., UCL) may be associated to different UCN's, but a single UCN may not have more than one UCL. A UCL always describe an available UW, i.e., a UW that has been already defined in the UNL KB, where a UCN does not have necessarily an address.

	In the [[UNL document\|UNL Document Structure]], UCI's are always abbreviated to the last part, because the scheme, the authority and the namespace may be inferred from the document header. For instance:
	*104379964 instead of ucl://unlkb.unlweb.net.br/104379964
	*table(icl>furniture) instead of ucn:eng:table(icl>furniture)

imported>Martins at 20:27, 19 September 2012

2012-09-19T20:27:54Z

← Older revision		Revision as of 20:27, 19 September 2012
Line 1:		Line 1:
	An '''Uniform Concept Identifier''' (UCI) is used to identify a concept. It is a URI (Uniform Resource Identifier) for [[UW]]'s. In the UNL framework, UCI's are represented either as UCL (Uniform Concept Locator) or UCN (Uniform Concept Name).		An '''Uniform Concept Identifier''' (UCI) is used to identify a concept. It is a URI (Uniform Resource Identifier) for [[UW]]'s. In the UNL framework, UCI's are represented either as UCL (Uniform Concept Locator) or UCN (Uniform Concept Name).

	== ~~Syntax~~ ==		== Structure ==
	The UCI follows the generic syntax defined for URI's:		The UCI follows the generic syntax defined for URI's:
	<scheme name> : <hierarchical part>		<scheme name> : <hierarchical part>
Line 9:		Line 9:
	**ucn, which is used for uniform concept names		**ucn, which is used for uniform concept names
	*<hierarchical part> holds the identification information.		*<hierarchical part> holds the identification information.



	== UCL (Uniform Concept Locator) ==		== UCL (Uniform Concept Locator) ==
	Uniform Concept Locators (UCL), as URL's, provide a method for finding the concept in the [[UNL Knowledge Base]]. They are represented as:		Uniform Concept Locators (UCL), as URL's, provide a method for finding the concept in the [[UNL Knowledge Base]]. They are represented as:
	ucl://<AUTHORITY>/<~~PATH~~>		ucl://<AUTHORITY>/<ID>
	Where:		Where:
	*ucl is the scheme name for uniform concept locators		*ucl is the scheme name for uniform concept locators
	*<AUTHORITY> is the authority (knowledge base) responsible for the concept (unlkb.unlweb.net, by default)		*<AUTHORITY> is the authority (knowledge base) responsible for the concept (unlkb.unlweb.net, by default)
	*<~~PATH~~> is the ~~address~~ of the concept in the knowledge base ~~(an integer indicating the unique position of the concept in the knowledge base)~~		*<ID> is the index of the concept in the knowledge base
	For instance, the concept "a piece of furniture having a smooth flat top that is usually supported by one or more vertical legs", which is lexicalized in English through the noun "table", may be located through:		For instance, the concept "a piece of furniture having a smooth flat top that is usually supported by one or more vertical legs", which is lexicalized in English through the noun "table", may be located through:
	ucl://unlkb.unlweb.net.br/104379964		ucl://unlkb.unlweb.net.br/104379964
Line 35:		Line 37:
	ucn:rus:стол(icl>мебель)		ucn:rus:стол(icl>мебель)
	UCN's must be unique and the namespace-specific string is normally split into two different parts: a root and a suffix, as exemplified above. The root can be a word or a multi-word expression. The suffix, which is always introduced by a UNL relation, is used to disambiguate the root.		UCN's must be unique and the namespace-specific string is normally split into two different parts: a root and a suffix, as exemplified above. The root can be a word or a multi-word expression. The suffix, which is always introduced by a UNL relation, is used to disambiguate the root.

			== Formal Syntax ==

			<nowiki><UCI> ::= <UCL>\|<UCN>

			<nowiki><UCL> ::= "ucl://"<AUTHORITY>"/"<PATH>
			<nowiki><AUTHORITY> ::= <UTF-8 character>+</nowiki>
			<nowiki><ID> ::= [0123456789]+</nowiki>

			<nowiki><UCN> ::= "ucn://"<LID>":"<NSS></nowiki>
			<nowiki><LID> ::= [a-z]{3}</nowiki>
			<nowiki><NSS> ::= <root>[<suffix>]</nowiki>
			<nowiki><root> ::= <UTF-8 character>+</nowiki>
			<nowiki><suffix> ::= “(“ <suffix> [ “,” <suffix> ]… “)” \| <relation> { “>” , “<” } <root></nowiki>
			<nowiki><relation> ::= {“agt”, "and", "aoj", ...}</nowiki>
			where:<br>
			+ to be repeated 1 or more times<br >
			< > variable<br >
			" " terminal symbol<br >
			<nowiki>::=</nowiki> ... is defined as ...<br >
			\| or<br >
			[ ] optional element<br >
			{ } alternative element<br >
			... to be repeated more than 0 times<br >

	== UCL or UCN? ==		== UCL or UCN? ==

imported>Martins at 19:56, 19 September 2012

2012-09-19T19:56:56Z

← Older revision		Revision as of 19:56, 19 September 2012
Line 34:		Line 34:
	ucn:deu:Tisch(icl>Möbel)		ucn:deu:Tisch(icl>Möbel)
	ucn:rus:стол(icl>мебель)		ucn:rus:стол(icl>мебель)
	UCN's must be unique and the namespace-specific string is normally split into two different parts: a root and a suffix. The root can be a word or a multi-word expression. The suffix, which is always introduced by a UNL relation, is used to disambiguate the root.		UCN's must be unique and the namespace-specific string is normally split into two different parts: a root and a suffix, as exemplified above. The root can be a word or a multi-word expression. The suffix, which is always introduced by a UNL relation, is used to disambiguate the root.

	== UCL or UCN? ==		== UCL or UCN? ==

imported>Martins at 19:56, 19 September 2012

2012-09-19T19:56:14Z

← Older revision		Revision as of 19:56, 19 September 2012
Line 34:		Line 34:
	ucn:deu:Tisch(icl>Möbel)		ucn:deu:Tisch(icl>Möbel)
	ucn:rus:стол(icl>мебель)		ucn:rus:стол(icl>мебель)
			UCN's must be unique and the namespace-specific string is normally split into two different parts: a root and a suffix. The root can be a word or a multi-word expression. The suffix, which is always introduced by a UNL relation, is used to disambiguate the root.

	== UCL or UCN? ==		== UCL or UCN? ==

imported>Martins at 19:51, 19 September 2012

2012-09-19T19:51:38Z

← Older revision		Revision as of 19:51, 19 September 2012
Line 19:		Line 19:
	For instance, the concept "a piece of furniture having a smooth flat top that is usually supported by one or more vertical legs", which is lexicalized in English through the noun "table", may be located through:		For instance, the concept "a piece of furniture having a smooth flat top that is usually supported by one or more vertical legs", which is lexicalized in English through the noun "table", may be located through:
	ucl://unlkb.unlweb.net.br/104379964		ucl://unlkb.unlweb.net.br/104379964
	This address is expected to bring all the information concerning the concept, i.e., it's definition in UNL, which ~~is expected to~~ be used by the languages where this concept is not lexicalized.		This address is expected to bring all the information concerning the concept, i.e., it's definition in UNL, which may be used by the languages where this concept is not lexicalized.

	== UCN (Uniform Concept Name) ==		== UCN (Uniform Concept Name) ==

imported>Martins at 17:36, 19 September 2012

2012-09-19T17:36:07Z

← Older revision		Revision as of 17:36, 19 September 2012
Line 38:		Line 38:
	UCL and UCN are both UCI's (i.e., uniform concept identifiers). They are both used to identify UW's. The difference is that UCL is an address to the position of the UW in the [[UNL Knowledge Base]], whereas the UCN is only the name of the UW. The same address (i.e., UCL) may be associated to different UCN's, but a single UCN may not have more than one UCL. A UCL always describe an available UW, i.e., a UW that has been already defined in the UNL KB, where a UCN does not have necessarily an address.		UCL and UCN are both UCI's (i.e., uniform concept identifiers). They are both used to identify UW's. The difference is that UCL is an address to the position of the UW in the [[UNL Knowledge Base]], whereas the UCN is only the name of the UW. The same address (i.e., UCL) may be associated to different UCN's, but a single UCN may not have more than one UCL. A UCL always describe an available UW, i.e., a UW that has been already defined in the UNL KB, where a UCN does not have necessarily an address.

	In the [[UNL document\|UNL Document Structure]], UCI's are always abbreviated to the last part, because the scheme and the ~~other information~~ may be inferred from the document header. For instance:		In the [[UNL document\|UNL Document Structure]], UCI's are always abbreviated to the last part, because the scheme, the authority and the namespace may be inferred from the document header. For instance:
	*104379964 instead of ucl://unlkb.unlweb.net.br/104379964		*104379964 instead of ucl://unlkb.unlweb.net.br/104379964
	*table(icl>furniture) instead of ucn:eng:table(icl>furniture)		*table(icl>furniture) instead of ucn:eng:table(icl>furniture)