GxPlex

Activity

Official signals, newest first by the day the source itself dated them. A signal is one record of one item a source’s own publication feed listed: the address the source listed it at, the day the source dated it, the class the source stated, and a digest of the listing entry’s own text.

A signal is not an observation and the two stores do not read each other. The observation series records what this site has fetched and hashed; a signal records what a source’s listing listed. Signals reports what the whole store holds and the Observatory reports whether each source has been read; this page is the subset of that store the scope below admits.

What this stream admits, and what it refuses

The stream carries official signals only. That is read off the distance scale rather than decided here: a record’s distance from source is derived from which surface it came from, the scale’s first three values are the primary document and two official surfaces, and its fourth value is third-party. Distances 0 to 2 are admitted and 3 is refused. A commercial news page is a third-party surface, so the order’s “never commercial news” is the same fence stated by example.

The distance scale, and what each value does in this stream
Value Scale label In this stream
0 primary admitted
1 official notice admitted
2 official related record admitted
3 third-party refused

Value 0 is admitted by the rule and no record can carry it: every record in this store is an entry in a listing, no adapter fetches the item behind one, and a 0 would say this record holds bytes it never requested. The row is kept rather than dropped, because a scale printed with a value missing is a scale a reader cannot check the rule against.

The three verdicts, and the population each is drawn from

The admission rule has been applied to no record, because the store holds none this reader could read. The three verdicts below therefore have no population, and no count is stated for them: an unmeasured result is not a negative one. No read has been attempted against any declared source, so every zero on this page is an unasked question rather than a source that listed nothing.

What a zero in the refused column would mean

A record can only be refused if an adapter declared that the listing it came from is not an official surface. Read from the adapter sources at build time: 8 adapter(s) declare a surface class, 8 declare an official one, 0 declare a third-party one, and 0 declare a value this census could not resolve. So a refused count of zero here says that nothing in this repository reads a third-party surface — not that a third-party signal was offered and turned away. Those are different facts and this page does not let one stand for the other.

Newest first, and where there is no date

The day is the day the source dated the entry, kept in the source’s own offset and never converted. The day this record read the entry is not consulted for ordering anywhere on this page: ordering by it would publish this record’s own collection schedule as though it were publisher activity. Within one day the order is by the record’s own identifier, ascending — a tiebreak has to be something, and this one says nothing about which entry a source published first, which is why it was chosen over any ordering that would. A record carrying no identifier sorts after those that do.

No record is in this section. This page states which zero that is above, and it is not one fact.

Admitted records with no day this stream can order by

These are not the bottom of the list above and they are not dropped. Each carries the state that says why it has no day, and the three states below are opposite facts: a source that stated no date, a source that stated one this reader could not read, and a record that has not been asked.

No admitted record is in this section, out of 0 admitted record(s).

By class

All 12 classes, in the order they were filed, including those nothing holds. Ordering by count would rank the classes against one another, and a class with no member keeps its place and its address. The two count columns are different populations and are printed side by side for that reason: this stream is the admitted subset, and the class page under Signals counts the whole store.

The signal classes, with what this stream holds and what the whole store holds
Class In this stream In the whole store Page
document 0 0 /signals/class/document
revision 0 0 /signals/class/revision
consultation 0 0 /signals/class/consultation
agenda 0 0 /signals/class/agenda
work item 0 0 /signals/class/work-item
notice 0 0 /signals/class/notice
press release 0 0 /signals/class/press-release
implementation 0 0 /signals/class/implementation
effective date 0 0 /signals/class/effective-date
standard progression 0 0 /signals/class/standard-progression
committee 0 0 /signals/class/committee
technical 0 0 /signals/class/technical

The stream column is drawn from 0 admitted record(s); the store column from 0 record(s) this reader could read. No cell above was counted over a record, because the population is none; the named state that says which none it is stands at the head of this page, and it is not one fact.

By authority

The host each listing was served from, alphabetically. Ordering by count would rank the sources against one another, which is a claim this record does not make. No author, editor, contributor or creator element is read into any field: a syndication format defines two of those as the email addresses of people, this record names no natural person, and a host cannot be one.

No admitted record carries an authority, because the stream holds no record at all. This page states which zero that is above.

By topic

A topic here is a source’s own stated category token, verbatim, and it is filed by the store for a signal whose declared addresses name no tracked entry. Nothing is inferred from a title, an address, or the section a listing sits in. A signal that does name a tracked entry carries no topic at all in this store, and that is the other state rather than an absence: the tracked entries carry a second vocabulary — the controlled identifiers published on Conventions — and reaching through a signal’s attachment to borrow one of those would make this record the author of that signal’s topic. The two vocabularies stay apart, and the counts below say how many records each covers.

No topic reading has been taken, because the stream holds no admitted record. This is an empty list rather than a set of zeros, so that it cannot be read as records having been examined and found to carry no topic.

By lens

A lens is one saved query with one grammar across every surface that honours it. A row here is a signal, not a tracked entry. A signal may NAME one, by an address the publisher declared inside its own listing, and a lens term is then a fact about the entry named — as this record holds it today, not about the signal and not about the entry as it stood on the signal’s own date.

This surface files rows under verification · status · jurisdiction · subject.

No lens is applied on this page. One lens grammar serves every surface and one parser reads it. That parser requires a surface declaration, and the module that owns the six declarations does not name this surface. A second parser or a borrowed declaration would each be worse than the gap: the first is a second spelling of the grammar, the second counts a population it is not looking at. The lens terms each row carries are published beside it instead, in the same grammar, so the same lens can be applied to these bytes by whatever received them. A full stream here is therefore never evidence that a lens matched everything.

Feeds

/activity.xml carries this stream — the same admitted population, under the same admission rule, built by the same module. It publishes at most 100 item(s), those carrying a day the source stated first, and states its own counts either side of that cut in its own description: a feed has no page on which to put a denominator, so the denominator goes where a subscriber reads it.

It holds nothing from this record’s own log. A revision detected in a tracked document, a correction, and an entry joining or leaving the tracker are the subject of /changes.xml, which carries no signal in return. One feed per subject, and neither fires on the other’s events: a subscriber can tell which of the two arrived.

Each item links to its own row above, by the identifier the store gave the record. A record the address rule will build nothing from carries no link rather than a shared one, because an item’s link is also its identity, and two items under one identity are one item to a subscriber.

No feed is published per class, per authority or per topic. Each would mint a permanent address whose membership can empty, and an address this site publishes has to keep answering after the last member leaves it.

What this page counts, and what it does not

Last updated: