------=_NextPart_000_0003_01BDF918.4EDE6150
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
From: owner-xml-dev@ic.ac.uk [mailto:owner-xml-dev@ic.ac.uk]On Behalf Of
Thierry Thelliez
We are attempting to implement XML for one of our projects.
There is a need for our users to cross reference documents/data.
We were looking for a way to generate/format a universal ID.
FPI seems to solve this issue but:
1- Why having yet another syntax ? I mean
-//myOrg//myDocType myDocName//en
could be:
<Registered>No</Registered>
<Org>myOrg</Org>
<DocType>myDocType</DocType>
<DocName>myDocName</DocName>
<Lang>en</ Lang>
It could be, but then you couldnt use it inside attributes (unless you
put in a processor to parse tags) or thePUBLIC identifier field of an entity
declaration (unless ditto).
The question is the same as "why aren't URLs marked up using element
syntax?" Various previous DTDs have tried to do this, and they have not been
as successful. I think the reason can be explained by the software
engineering concept of "cohesion and coupling": some kinds of data so
naturally cohere to each other (i.e. in the minds of users) that it is wise
to couple them (i.e. in their syntax) strongly. In particular, some strings
have certain qualities where our minds accept them as names: I think URLs,
FPIs and MIME types are such.
In my book on document patterns I discuss this. I would also mention
that these kind of compound names correspond to the "natural document"
pattern, in that they have ( metadata, data, annotations ). When there is
one natural document embedded in a different type of document (i.e. code
inside text, FPI inside attribute) it seems that humans appreciate this
being flagged: especially if no formatting is available, a change of
notation will be used.
Why does CSS not use instance notation (apart from not upsetting dumb
HTML browsers)? I think it is exactly this reason that an embedded document
of a completely different document type (as far as its function is
concerned) is best marked up by clearly flagging it by using a differnet
notation.
In other words
<a href="http://www.w3.org/TR/">
is not the same as
<a href:method="http" href:node="www.w3.org" href:directory="TR/" >
but
<a href:method="http" href:node="www.w3.org" href:directory="TR/"
href:combine-notation="URL Syntax">
I think XMLers should not go too far in saying that instance syntax is
always preferable to little languages (embedded notations), in particular
when the function of the embedded language is not structural markup but for
naming or locating or stylesheets.
2- Where can I find more info about FPIs ? I spend a long time with
a web search engine but got only few interesting documents. Where can I
find ISO 9070 related documents ? The ISO web site is not very user
friendly
for a first timer.
Several (most?) SGML books have information on FPI syntax. Online try
Robin Cover's SGML site first.
3- Assuming that we keep this syntax, would it be valid to have
something
like:
-//anOrg::anAuthor//aDocType aDocName::aVersionNumber//en
or even worse:
-//aCountry::anOrg::aDepartment::anAuthor//aDocType::aDocTypeVersionNumb
er aDocName::aDocVersionNumber//en
After the "-//" you can use any convention you want for the "owner of
FPI" and "name" field. the syntax is
-//owner of FPI//type name//lang
where the "type" is defined in the SGML standard: e.g. DTD, ENTITIES,
NOTATION, TEXT, NONSGML (capitals) and the "lang" (capitals) is the language
code of the FPI (and therefore probably of the resource). Why "even worse"?
If that is what is required to specify it exactly enough, that is great.
ISBN and IDN (Internet Domain Name) "owners" may use the form
+//ISBN number//type name//lang
+//IDN addess//type name//lang
Rick Jelliffe
------=_NextPart_000_0003_01BDF918.4EDE6150
Content-Type: text/html;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD W3 HTML//EN">
1- Why having yet another syntax ? I mean It=20
could be, but then you couldnt use it inside attributes (unless you =
put in a=20
processor to parse tags) or thePUBLIC identifier field of an entity=20
declaration (unless ditto). The question is the same as "why aren't =
URLs marked=20
up using element syntax?" Various previous DTDs have tried to =
do this,=20
and they have not been as successful. I think the reason can =
be=20
explained by the software engineering concept of "cohesion and=20
coupling": some kinds of data so naturally cohere to each =
other=20
(i.e. in the minds of users) that it is wise to couple them (i.e. in =
their=20
syntax) strongly. In particular, some strings have certain =
qualities=20
where our minds accept them as names: I think URLs, FPIs and MIME =
types are=20
such. In=20
my book on document patterns I discuss this. I would also mention =
that these=20
kind of compound names correspond to the "natural =
document"=20
pattern, in that they have ( metadata, data, annotations ). When =
there is=20
one natural document embedded in a different type of document (i.e. =
code=20
inside text, FPI inside attribute) it seems that humans appreciate =
this=20
being flagged: especially if no formatting is available, a change of =
notation will be used. Why=20
does CSS not use instance notation (apart from not upsetting dumb =
HTML=20
browsers)? I think it is exactly this reason that an embedded =
document of a=20
completely different document type (as far as its function is=20
concerned) is best marked up by clearly flagging it by using a =
differnet notation. In other words <a=20
href=3D"http://www.w3.org/TR/"> is not the same as <a href:met I=20
think XMLers should not go too far in saying that instance syntax is =
always=20
preferable to little languages (embedded notations), in particular =
when the=20
function of the embedded language is not structural markup but for =
naming or=20
locating or stylesheets. 2- Where can I find more info about FPIs ? I spend a long time =
with Several (most?) SGML books have information on FPI =
syntax. =20
Online try Robin Cover's SGML site first.
3- Assuming that we keep this syntax, =
would it be=20
valid to have something or even worse:=20
=
-//aCountry::anOrg::aDepartment::anAuthor//aDocType::aDocTypeVersionNu=
mber=20
aDocName::aDocVersionNumber//en After the "-//" you can use any convention you =
want for the=20
"owner of FPI" and "name" field. the syntax=20
is -//owner of FPI//type =20
name//lang where the "type" is defined in the SGML standard: =
e.g. DTD,=20
ENTITIES, NOTATION, TEXT, NONSGML (capitals) and the =
"lang"=20
(capitals) is the language code of the FPI (and therefore probably =
of the=20
resource). Why "even worse"? If that is what =
is=20
required to specify it exactly enough, that is great. =
ISBN=20
and IDN (Internet Domain Name) "owners" may use the=20
form +//ISBN =
number//type =20
name//lang +//IDN =
addess//type =20
name//lang Rick=20
Jelliffe
-//myOrg//myDocType =
myDocName//en
could be: =
<Registered>No</Registered>=20
<Org>myOrg</Org>=20
<DocType>myDocType</DocType>=20
<DocName>myDocName</DocName> =
<Lang>en</
a=20
web search engine but got only few interesting documents. Where can =
I=20
find ISO 9070 related documents ? The ISO web site is not very =
user=20
friendly
for a first timer.=20
like:
-//anOrg::anAuthor//aDocType=20
aDocName::aVersionNumber//en