<?xml version="1.0" encoding="UTF-8"?>
<TEI xml:space="preserve" xmlns="http://www.tei-c.org/ns/1.0" 
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" 
xsi:schemaLocation="http://www.tei-c.org/ns/1.0 https://raw.githubusercontent.com/kermitt2/grobid/master/grobid-home/schemas/xsd/Grobid.xsd"
 xmlns:xlink="http://www.w3.org/1999/xlink">
	<teiHeader xml:lang="en">
		<fileDesc>
			<titleStmt>
				<title level="a" type="main">A Portal for the State of the Art on Content Negotiation</title>
			</titleStmt>
			<publicationStmt>
				<publisher/>
				<availability status="unknown"><licence/></availability>
			</publicationStmt>
			<sourceDesc>
				<biblStruct>
					<analytic>
						<author>
							<persName><forename type="first">Yousouf</forename><surname>Taghzouti</surname></persName>
							<affiliation key="aff0">
								<orgName type="department">Mines Saint-Etienne</orgName>
								<orgName type="laboratory">UMR 6158 LIMOS</orgName>
								<orgName type="institution" key="instit1">Univ Clermont Auvergne</orgName>
								<orgName type="institution" key="instit2">INP Clermont Auvergne</orgName>
								<orgName type="institution" key="instit3">CNRS</orgName>
								<address>
									<postCode>F -42023</postCode>
									<settlement>Saint-Etienne</settlement>
									<country key="FR">France</country>
								</address>
							</affiliation>
						</author>
						<author>
							<persName><forename type="first">Antoine</forename><surname>Zimmermann</surname></persName>
							<affiliation key="aff0">
								<orgName type="department">Mines Saint-Etienne</orgName>
								<orgName type="laboratory">UMR 6158 LIMOS</orgName>
								<orgName type="institution" key="instit1">Univ Clermont Auvergne</orgName>
								<orgName type="institution" key="instit2">INP Clermont Auvergne</orgName>
								<orgName type="institution" key="instit3">CNRS</orgName>
								<address>
									<postCode>F -42023</postCode>
									<settlement>Saint-Etienne</settlement>
									<country key="FR">France</country>
								</address>
							</affiliation>
						</author>
						<author>
							<persName><forename type="first">Maxime</forename><surname>Lefrançois</surname></persName>
							<affiliation key="aff0">
								<orgName type="department">Mines Saint-Etienne</orgName>
								<orgName type="laboratory">UMR 6158 LIMOS</orgName>
								<orgName type="institution" key="instit1">Univ Clermont Auvergne</orgName>
								<orgName type="institution" key="instit2">INP Clermont Auvergne</orgName>
								<orgName type="institution" key="instit3">CNRS</orgName>
								<address>
									<postCode>F -42023</postCode>
									<settlement>Saint-Etienne</settlement>
									<country key="FR">France</country>
								</address>
							</affiliation>
						</author>
						<title level="a" type="main">A Portal for the State of the Art on Content Negotiation</title>
					</analytic>
					<monogr>
						<idno type="ISSN">1613-0073</idno>
					</monogr>
					<idno type="MD5">EE6291F83475C8AF0A6CA498DBB49354</idno>
					<idno type="DOI">10.5281/zenodo.6504504</idno>
				</biblStruct>
			</sourceDesc>
		</fileDesc>
		<encodingDesc>
			<appInfo>
				<application version="0.7.2" ident="GROBID" when="2023-03-25T03:14+0000">
					<desc>GROBID - A machine learning software for extracting information from scholarly documents</desc>
					<ref target="https://github.com/kermitt2/grobid"/>
				</application>
			</appInfo>
		</encodingDesc>
		<profileDesc>
			<textClass>
				<keywords>
					<term>Content negotiation</term>
					<term>Style of negotiation</term>
					<term>Dimension of negotiation</term>
					<term>Constraint</term>
					<term>Ontology</term>
				</keywords>
			</textClass>
			<abstract>
<div xmlns="http://www.tei-c.org/ns/1.0"><p>Resources on the Web are identified by Uniform Resource Identifiers (URIs), and can be accessed using web protocols such as HTTP. A resource can have several representations varying along a set of dimensions, forming a set of variants. Content negotiation (CN) is the mechanism for selecting the appropriate variant that conforms to a set of preferences (constraints). Over the years, various dimensions of CN, styles of CN, as well as ways to convey constraints have emerged to satisfy new requirements and solve new use cases. This demo presents a new resource called Content Negotiation Theoretical Framework (CNTF): a website that collects knowledge about CN use cases, styles, dimensions, etc., and organises it according to an ontology. CNTF aims to highlight existing solutions, if available, or suggest plausible ways to satisfy common requirements. It is intended to be used to disseminate our future proposals for advancing CN, making it a sustainable and up-to-date digital survey of CN.</p></div>
			</abstract>
		</profileDesc>
	</teiHeader>
	<text xml:lang="en">
		<body>
<div xmlns="http://www.tei-c.org/ns/1.0"><p>One resource may have different representations. To request a specific representation, a client would use Content Negotiation (CN), the mechanism for serving the most appropriate representation of a web resource. CN is described in the Architecture of the World Wide Web W3C Recommendation as one of the essential components of Web design [1, section 3.2]. The client may accompany its request with a set of constraints that the origin server (or some proxy server) uses to serve an adequate response. The sequence and type of exchanged messages vary according to the CN style, CN dimension, constraint conveyance technique, and the web protocol employed.</p><p>Over the years, various dimensions of CN, styles of CN, as well as ways to convey constraints have emerged to satisfy new requirements and solve new use cases. However, there is no general and comprehensive state of the art on this topic. This demo presents a new resource ISWC'22: international semantic web conference, October 23-27, 2022, Virtual conference * Corresponding author. Envelope yousouf.taghzouti@emse.fr (Y. Taghzouti); antoine.zimmermann@emse.fr (A. Zimmermann); maxime.lefrancois@emse.fr (M. Lefrançois) GLOBE https://youctagh.github.io/ (Y. Taghzouti); https://www.emse.fr/~zimmermann/ (A. Zimmermann); https://www.maxime-lefrancois.info/ (M. Lefrançois) Orcid 0000-0003-4509-9537 (Y. Taghzouti); 0000-0003-1502-6986 (A. Zimmermann); 0000-0001-9814-8991 (M. Lefrançois) called Content Negotiation Theoretical Framework (CNTF ): a website that collects knowledge about CN use cases, styles, dimensions, etc., and organises it according to an ontology. To the best of our knowledge, CNTF provides the first digital state of the art survey about existing CN approaches and features. We identify the used CN feature in each contribution, and categorise them in order to classify existing contributions on CN. CNTF aims to highlight existing solutions, if available, or suggest plausible ways to satisfy common requirements. To summarise, the contributions of CNTF are the following: 1) A digital state of the art about CN in the form of a website; 2) A reference point for CN categories and concept groups to enable classification; 3) An ontology for CN knowledge; 4) A graphic visualisation and navigation. CNTF is open-source https://github.com/youctagh/cntf with permanent URL https: //w3id.org/cntf/ and DOI https://doi.org/10.5281/zenodo.6504504 a video demonstration is available at https://youtu.be/Cm8tuabbXCM. Some efforts were done to encapsulate the available techniques and characteristics of CN, but to the best of our knowledge, this only took the form of a related work section in specifications using CN such as [2, Section 5] or web page documentation such as in Mozilla Developer Network Web Docs<ref type="foot" target="#foot_0">1</ref> . The idea of a digital state of the art is not new; others have already proposed similar resources, either in the form of web pages, or in the form of a website dedicated to a topic like the one for the complexity of reasoning in Description Logics [3].</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="2.">A Portal for the State of the Art on Content Negotiation</head><p>CNTF is a website designed to help the web community: either newcomers to the field of CN who want to explore it, or experts who want to keep up with the latest techniques. CNTF should meet these requirements: The system has been designed as a website, so no installation process is required. In addition, it allows users to always have the latest version without having to perform an update at each release. CNTF is built with the Angular Framework. Next, we discuss how CNTF could be utilised:</p><formula xml:id="formula_0">R</formula><p>CNTF as a State of the Art Literature Review of CN CNTF collects the styles of CN and provides: 1) A description of the style; 2) An example of CN using that style; 3) The use cases from the bank of use cases in CNTF using that style; 4) Pointing the advantages and disadvantages of this style. CNTF groups the preferences of the client/server in a category named CN dimension and for each of these dimensions we deliver: 1) A description of the dimension; 2) Some references to the pertinent use cases; 3) Some examples of the CN process; 4) Some relevant references on the state of the art. Each domain comes with a set of terms, for a newcomer to find and grasp the definitions of all these terms is a tedious task, that's why CNTF has a terminology section that lists and keeps track of the meaning of the terms related to CN, and since different communities might differ on the meaning of a term, we present them with their respective communities references. Since another type of user of this resource is developers, CNTF has an "Additional Info" section that lists implementations of CN using some of the available technologies.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head>CNTF as a Bank of CN Use Cases</head><p>A difficulty faced by someone conducting research in a new subject area is to contextualise the usefulness of the material learned. CNTF attempts to solve this problem for the CN domain by collecting use cases from other documents and websites. Being an open-source project, the community may contribute with other use cases. In each of the use cases, one finds: 1) A description of the use case; 2) Potentially some references to the primary source the use case was inspired from; 3) The requirements extracted from the use case; 4) Potentially a solution section with relevant references or preliminary solutions. Each of these use cases must satisfy a set of requirements that could be found in the "CN requirement" section.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head>CNTF as a Categorisation and Classification</head><p>Medium CNTF is organised in categories, which favours categorisation and classification. A user may check all the concepts of CN: styles, dimensions, etc., and select those that best fit their use case. A table can be found in the "Classification" section in CNTF, where each row of the table is accompanied by a summary to aid understanding.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head>CNTF as a CN Knowledge Graph</head><p>Most of the content of CNTF is available in a knowledge graph (KG) <ref type="bibr" target="#b1">2</ref> , describing among other: use cases, references, dimensions, requirements. CNTF knowledge graph is modelled according to the "CNTF ontology" https://w3id.org/cntf/ontology.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head>CNTF as a Medium for Visualisation and Navigation of CN Concepts CNTF users can</head><p>navigate with the traditional hyperlinks to move from one page to another in order to explore different concepts. Alternatively, the user can get a general view of the relationships between concepts through CNTF ontology "visualisation" section <ref type="bibr" target="#b2">3</ref> . WebVOWL is used to render the visualisation.</p><p>CNTF as a Template for State of the Art Resources CNTF is a website that represents a digital form of the survey on the CN domain but some components that represent generic parts could be reused to fit other domains such as: Use Cases, Requirements, Classifications (change the table columns with the used metrics), Terminologies, Abbreviations, References, etc., making it a candidate to be a model for digital surveys. Moreover, the same parts could be reused from the ontology.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="3.">Conclusion and Future work</head><p>Content negotiation is a cornerstone of the Web architecture, and a powerful mechanism for selecting the best representation from multiple available alternatives. CNTF aims to collect everything one needs to know about it in one place. CNTF reviews the available literature and compiles it into a single resource so that users interested in CN can easily find relevant materials. It addresses the problem of CN and attempts to identify new ways to better solve the available use cases. The resource covers the basics of CN: use cases, dimensions, styles, and existing ways of conveying constraints. CNTF gives a coherent view of the problem that will be the basis for addressing the semantic CN problem. CNTF recommends solutions that leverage semantic web technologies, e.g., leveraging SHACL as a way to express the threshold of CN constraints. <ref type="bibr">4</ref> The future work on CNTF involves a number of initiatives, one of which is the ongoing collection of use cases for CN, dimensions, etc., in particular the new CN by profile. We plan to have an implementation of this approach to facilitate its adoption by having an experimental space, this space would give users the opportunity to test different CN styles, dimensions and solutions to some of the use cases without having to implement them themselves.</p></div><figure xmlns="http://www.tei-c.org/ns/1.0" type="table" xml:id="tab_0"><head></head><label></label><figDesc>Categorisable CNTF should provide the means to categorise the different CN use cases and techniques to allow for comparative evaluation. It should also have a well thought out grouping and modelling of the different CN concepts to facilitate understanding. R 4 Maintainable CNTF should promote maintainability by adjusting the model used, e.g., community-recommended vocabularies, and by taking into account feedback provided by resource users to clarify and rectify content.</figDesc><table /><note>1 Navigable design CNTF should have a navigable design that includes interlinking through hyperlinks to help users categorise their use cases, and a graph following the resource model, with clickable nodes to navigate from one concept to another. R 2 Extensible One of the main contrasts between a traditional survey paper and the CNTF resource is that it should support extensibility by allowing the addition of new CN concepts, e.g., a new dimension, and to be up to date with different terminology and definitions.R 3</note></figure>
			<note xmlns="http://www.tei-c.org/ns/1.0" place="foot" n="1" xml:id="foot_0">https://developer.mozilla.org/en-US/docs/Web/HTTP/Content_negotiation</note>
			<note xmlns="http://www.tei-c.org/ns/1.0" place="foot" n="2" xml:id="foot_1">https://w3id.org/cntf/kg</note>
			<note xmlns="http://www.tei-c.org/ns/1.0" place="foot" n="3" xml:id="foot_2">https://w3id.org/cntf/visualisation</note>
			<note xmlns="http://www.tei-c.org/ns/1.0" place="foot" n="4" xml:id="foot_3">See the use case: Negotiation of RDF shapes in CNTF.</note>
		</body>
		<back>
			<div type="references">

				<listBibl>

<biblStruct xml:id="b0">
	<monogr>
		<author>
			<persName><forename type="first">I</forename><surname>Jacobs</surname></persName>
		</author>
		<author>
			<persName><forename type="first">N</forename><surname>Walsh</surname></persName>
		</author>
		<title level="m">Architecture of the World Wide Web, W3C Recommendation</title>
				<meeting><address><addrLine>W3C</addrLine></address></meeting>
		<imprint>
			<date type="published" when="2004">2004</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b1">
	<monogr>
		<author>
			<persName><forename type="first">L</forename><forename type="middle">G</forename><surname>Svensson</surname></persName>
		</author>
		<author>
			<persName><forename type="first">R</forename><surname>Atkinson</surname></persName>
		</author>
		<author>
			<persName><forename type="first">N</forename><forename type="middle">J</forename><surname>Car</surname></persName>
		</author>
		<title level="m">Content Negotiation by Profile, W3C Working Draft</title>
				<meeting><address><addrLine>W3C</addrLine></address></meeting>
		<imprint>
			<date type="published" when="2019">2019</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b2">
	<monogr>
		<title level="m" type="main">Complexity of reasoning in description logics</title>
		<author>
			<persName><forename type="first">E</forename><surname>Zolin</surname></persName>
		</author>
		<ptr target="http://www.cs.man.ac.uk/~ezolin/dl/" />
		<imprint>
			<date type="published" when="2013">2013</date>
		</imprint>
	</monogr>
</biblStruct>

				</listBibl>
			</div>
		</back>
	</text>
</TEI>
