Changes between Version 44 and Version 45 of FCS-Specification-ScrapBook

Timestamp:

02/13/14 20:20:03 (10 years ago)

Author:

oschonef

Comment:

--

FCS-Specification-ScrapBook

@@ -144 +144 @@
 === Typographic and XML Namespace conventions ===
 The following typographic conventions for XML fragments will be used throughout this specification:
- * `<prefix:Element>`: An XML element with the Generic Identifier ''Element'' that is bound an XML namespace denoted by the prefix ''prefix''.
- * `@attr`: An XML attribute with the name ''attr''
+ * `<prefix:Element>` \\ An XML element with the Generic Identifier ''Element'' that is bound an XML namespace denoted by the prefix ''prefix''.
+ * `@attr` \\ An XML attribute with the name ''attr''
 {{{#!comment
- * `@prefix:attr`: An XML attribute with the name ''attr'' that is bound to an XML namespaces denoted by the prefix ''prefix''.
-}}}
- * `string`: the literal ''string'' must be used either as element content or attribute value
+ * `@prefix:attr` \\ An XML attribute with the name ''attr'' that is bound to an XML namespaces denoted by the prefix ''prefix''.
+}}}
+ * `string` \\ The literal ''string'' must be used either as element content or attribute value.
 Endpoints and Clients `MUST` adhere the [#REF_XML_Namespaces XML-Namespaces] specification. The CLARIN-FCS interface specification generally does not dictate whether XML elements should be serialized in their prefixed or non-prefixed syntax, but Endpoints `MUST` ensure that the correct XML namespace is used for elements and that XML namespaces are declared correctly. Clients `MUST` be agnostic to which syntax for serializing the XML elements, i.e. if the prefixed or un-prefixed variant was used, and `SHOULD` operate solely on ''expanded names'', i.e. pairs of ''namespace name'' and ''local name''.