Nabble - w3.org - www-xml-infoset-comments

Possible erratum in XML Information Set (Second Edition)

2009-03-26T20:13:57Z

In Section 2.3, Point 8, I think the sentence should end “… or in its [namespace attributes] property”.

Best regards,

Larry Golding

Re: space

2008-04-19T04:34:21Z

Over the past few decades, recycling has become a central component of many business operations in the United States. Recycling is valued for the cost-savings associated with some programs as well as its general environment-friendly aspects. Recycling programs are comprised of three elements in a continuum represented by the well-known "chasing arrows" symbol that adorns recyclable products: 1) collection of recyclable materials from the waste stream; 2) processing of those materials into new products; and 3) purchasing of products containing recycled materials

Food and Fitness: golf

Golf Clubs is a competitive sport, and a very popular recreational activity played by people of a wide range of age and ability. Unlike many other activities, golf retains its players throughout their lifetime. Golfers in their eighties claim that the game helps them to keep physically and mentally fit. Golf strengthens the back and shoulders, and helps to maintain spine rotation, necessary for a healthy back.

There are two contrasting parts to the game. On the tee, power is used to hit the ball as close to the hole as possible. The tee shot requires considerable strength in the upper body, and flexibility in the back and legs. When on the green, great muscle control and accuracy are needed to putt the ball delicately into the hole. Golfers use Heathrow taxis to get to the airport

Phone sex

Phone sex is a type of virtual sex that refers to sexually explicit conversation between two or more persons via telephone, especially when at least one of the participants phonesex numbers masturbate or engages in sexual fantasy. Phone sex conversation may take many forms, including (but not limited to): guided, narrated, and enacted suggestions; sexual anecdotes and confessions; candid expression of sexual feelings or love a UK phone sex blog discussion of very personal and sensitive sexual topics; or just two people listening to each other masturbate.

Wikipedia: sex worker

A sex worker in UK Porn

A sex worker is a person who earns money by providing sexual services. The term is sometimes used as a synonym or euphemism for prostitution, but most scholars define it to include all individuals who perform sexual or sexually oriented activities in the phone porn sex industry, such as swingers strippers, erotic massage therapists, pornography actors and actresses, live sex shows, webcam shows, and phone sex operators.

Casino

The history of the word mobile phone casino reveals a transformation from a cottage to a gambling palace. The source of our word, Italian casino, is a diminutive of casa, “house.” Central to the transformation is the development of the senses of casino in Italian. The word was first applied to a country house and then came to be used for a social gathering place, a room or building where one could dance, listen to music, and gamble. This last pastime seems to have gained precedence over the others, at least as far as the development of the word is concerned, and casino took on the meaning “gambling establishment.” These senses of the Italian word have all been borrowed into English, the sense “social gathering place” mobile phone bingo being recorded first in the 18th century, the sense “gambling establishment” first in 1851.

elements without namespace names

2008-02-26T09:08:17Z

Section 2.2 of http://www.w3.org/TR/2004/REC-xml-infoset-20040204/
reads in part:

[namespace name] The namespace name, if any, of the element type.
If the element does not belong to a namespace,
this property has no value.

I think the notion of "belonging to a namespace" is used once or
twice informally in the Namespaces rec, but it is not defined. I
think the Infoset spec would do better to recast the second sentence
above to say "If the element has no namespace name ..." As it is,
I think the sentence makes a false assumption about the Namespaces
recommendation which renders the condition meaningless; at the very
least the sentence deviates unnecessarily from what the Namespaces
rec says.

[Rationale, for those who find it useful. If a name has an
explicit namespace name, we know that the local name belongs to
that namespace. We do not know that that local name does not
belong to any other namespace, nor that that local name has
different semantics in any other namespace that defines a meaning
for it. No (namespace, local name) pair provides any information
about the relation of that local name to any other namespace.

It follows that specifying a QName whose expanded name has no
namespace name provides no information about the relation of
that particular local name to any namespace. It does not tell
us that the local name is in any such namespace; it also does not
tell us that that local name is not in any namespace. That's
a common way of speaking, but misleading and false.

At the practical level, if a processor is designed to understand
and process a particular set of names in a particular namespace,
it can also be defined to process those names when they are
provided by expanded names without namespaces, without failing to
conform to the Namespaces rec. (I.e. I can write a stylesheet
that processes both tei:x, tei:y, and tei:z, on the one hand,
and x, y, z [with no default namespace] on the other.) This was
an important consideration for some of those involved in the
initial development of the namespaces rec, and it helps understand
why the empty string is explicitly excluded from use as a namespace
name.

At the theoretical level, the ns/localname bindings of expanded
names provide positive information only, no negation, and ditto
for expanded names which have no namespace name.]

--C. M. Sperberg-McQueen

document property should be defaulted to 'no'

2008-02-26T08:39:59Z

The version of the infoset spec at

http://www.w3.org/TR/2004/REC-xml-infoset-20040204/

says, of the document information item's [standalone] property

This property ... has no value if there is no standalone
document declaration.

But the XML specification says

If there are no external markup declarations, the standalone
document declaration has no meaning. If there are external
markup declarations but there is no standalone document
declaration, the value "no" is assumed.

This seems to me to indicate that the correct thing for the
infoset spec to do is to specify that the property defaults to
the value 'no'. (This gives a value to the property in cases
where the XML spec does not specify a value, but those cases
are also those for which the XML spec says it does not matter,
since in those cases the value has no meaning.)

I think the infoset spec should specify a default value of 'no'
for this property.

Am I wrong?

--C. M. Sperberg-McQueen