OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help

sarif message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]

Subject: "namespaced" vs. "hierarchical"

I suggest that we use the term “hierarchical” rather than “namespaced” to refer to those string values in the spec1 of the form “component [ / component ]…”. My reasoning is:


  1. There is no such English word as “namespaced.” Even reference sources like Wikipedia and MSDN, when describing namespaces, don’t use this form. Google search doesn’t find it anywhere.
  2. Even granting the coinage, IMO “hierarchical” better conveys the semantics.
  3. We already use “namespace” in the spec to mean something else (it’s an example of a logical location kind, and it shows up in lots of examples).




This isn’t blocking me. I can write the change draft for #162 with “namespaced” and a search-and-replace will do the trick if necessary.




1 properties.tags, run.stableId, and after #162, run.automationId.

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]